[Desktop-packages] [Bug 193325] Re: "unknown media type" during update
Also I'm pretty sure the bug lies in the package shared-mime-info. It certainly isn't limited to Nautilus alone since I use Kubuntu and the bug shows up there: Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/193325 Title: "unknown media type" during update Status in Nautilus: Confirmed Status in shared MIME database: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/193325/+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 1453703] Re: Gnome Shell
Hi Christopher, it doesn't look like I have that option. -- 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/1453703 Title: Gnome Shell Status in xorg package in Ubuntu: Incomplete Bug description: Windows in Gnome shell turn invisible. e.g. when opening Terminator and maximizing it, it turns invisible. It shows up when going to Activities. I have to use a shortcut to restore it to see it again. When maximizing SublimeText, there's tearing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 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: GNOME Date: Mon May 11 09:53:28 2015 DistUpgraded: 2014-06-17 09:13:14,256 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.11.0-18-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox, 4.3.10, 3.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2002] InstallationDate: Installed on 2014-02-18 (446 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-06-17 (328 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-211 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-211:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon May 11 08:19:04 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22653 vendor GSM xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453703/+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 193325] Re: "unknown media type" during update
Why is this bug still unfixed? It's appeared in every version of Ubuntu I've used since at least 8.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/193325 Title: "unknown media type" during update Status in Nautilus: Confirmed Status in shared MIME database: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/193325/+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 1291574] Re: nouveau DRM GPU lockup, PFIFO unhandled status 0x00800000
I can trigger the bug with docky anytime I want. Just move quickly through Docky icons with the mouse cursor (https://bugs.launchpad.net/ubuntu/+source/docky/+bug/1451379). I a few seconds the screen will freeze. Most of the times I have to wait for about 30 seconds. I can switch to text (Alt + Ctrl + F1) in the meantime and see that gnome-shell occupies the computer 100%. Nouveau driver writes lots of lines into syslog at the same time. But sometimes everything freezes and only hard reset helps. It starts like that: May 21 08:35:37 computer gnome-session[8979]: nouveau: kernel rejected pushbuf: Invalid argument May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: krec 0 pushes 1 bufs 19 relocs 0 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0005 0004 0004 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0001 01b9 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0002 0007 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0003 000a 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0004 000b 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0005 0008 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0006 0006 0004 0004 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0007 019e 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0008 0013 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0009 000d 0004 0004 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 000a 0104 0004 0004 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 000b 0124 0002 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 000c 0026 0004 0004 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 000d 0090 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 000e 01b1 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 000f 01ac 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0010 01ad 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0011 0030 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: buf 0012 01ba 0002 0002 May 21 08:35:37 computer gnome-session[8979]: nouveau: ch0: psh 05e7d4 06045c May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0004721c May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0fac6881 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00086ff4 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x12c0 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x04b0 May 21 08:35:37 computer kernel: [263094.549645] nouveau E[gnome-shell[9087]] multiple instances of buffer 442 on validation list May 21 08:35:37 computer kernel: [263094.549650] nouveau E[gnome-shell[9087]] validate_init May 21 08:35:37 computer kernel: [263094.549652] nouveau E[gnome-shell[9087]] validate: -22 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00146200 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x511f May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00e6 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0040 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00087240 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x12c0 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x04b0 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00047224 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0001 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00146fe0 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x42dd May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0016 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0040 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x00047538 May 21 08:35:37 computer gnome-session[8979]: nouveau: #0110x0001 And then hundreds of these lines with "nouveau: #..." -- You received this bug notification becau
[Desktop-packages] [Bug 1457750] Re: Locked input while recording a shortcut
This is a very confusing situation (not only for ubuntu beginners). To resolve it I would either recommend that a) It should not be possible to select the "Typing" tab during key stroke recording or b) Selecting the "Typing" tab during key stroke recording should abort that recording -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1457750 Title: Locked input while recording a shortcut Status in unity-control-center package in Ubuntu: New Bug description: - open unity-control-center - select "Keyboard" - select "Shortcuts" tab - select "Screenshots" from the left list - select "Take a screenshot" from the right list Now the unity control-center expects some keystrokes to be pressed for that shortcut "New accelerator" - DON'T press any keys but - select "Typing" tab The "Typing" tab will be shown. - select "Shortcuts" tab Nothing happens. In fact clicking on anything on the screen has no effect. The screen seems to be locked. - press "d" key Out of the blue you get the "The shortcut "D" cannot be used ..." Dialog. - click "Cancel" Input seems to be unlocked again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 22 08:03:28 2015 SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1457750/+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 1457750] [NEW] Locked input while recording a shortcut
Public bug reported: - open unity-control-center - select "Keyboard" - select "Shortcuts" tab - select "Screenshots" from the left list - select "Take a screenshot" from the right list Now the unity control-center expects some keystrokes to be pressed for that shortcut "New accelerator" - DON'T press any keys but - select "Typing" tab The "Typing" tab will be shown. - select "Shortcuts" tab Nothing happens. In fact clicking on anything on the screen has no effect. The screen seems to be locked. - press "d" key Out of the blue you get the "The shortcut "D" cannot be used ..." Dialog. - click "Cancel" Input seems to be unlocked again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 22 08:03:28 2015 SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1457750 Title: Locked input while recording a shortcut Status in unity-control-center package in Ubuntu: New Bug description: - open unity-control-center - select "Keyboard" - select "Shortcuts" tab - select "Screenshots" from the left list - select "Take a screenshot" from the right list Now the unity control-center expects some keystrokes to be pressed for that shortcut "New accelerator" - DON'T press any keys but - select "Typing" tab The "Typing" tab will be shown. - select "Shortcuts" tab Nothing happens. In fact clicking on anything on the screen has no effect. The screen seems to be locked. - press "d" key Out of the blue you get the "The shortcut "D" cannot be used ..." Dialog. - click "Cancel" Input seems to be unlocked again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 22 08:03:28 2015 SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1457750/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
the bug is solved installing nvidia-modprobe -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for "LUG" in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 1361207] Re: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
the bug is solved installing nvidia-modprobe! -- 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/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Confirmed Bug description: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf -> 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+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 1457738] Re: package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1457738 Title: package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 Status in brltty package in Ubuntu: New Bug description: maybe panasoniclpd problem ProblemType: Package DistroRelease: Ubuntu 15.04 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 22 07:28:10 2015 DuplicateSignature: package:brltty:(not installed):il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 ErrorMessage: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 InstallationDate: Installed on 2015-05-02 (19 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: brltty Title: package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1457738/+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 1457738] [NEW] package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1
Public bug reported: maybe panasoniclpd problem ProblemType: Package DistroRelease: Ubuntu 15.04 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 22 07:28:10 2015 DuplicateSignature: package:brltty:(not installed):il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 ErrorMessage: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 InstallationDate: Installed on 2015-05-02 (19 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: brltty Title: package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: brltty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1457738 Title: package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 Status in brltty package in Ubuntu: New Bug description: maybe panasoniclpd problem ProblemType: Package DistroRelease: Ubuntu 15.04 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 22 07:28:10 2015 DuplicateSignature: package:brltty:(not installed):il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 ErrorMessage: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 InstallationDate: Installed on 2015-05-02 (19 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: brltty Title: package brltty (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1457738/+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 1434986] Re: Not working network connection after boot
I`ve tested Wily and the problem persist, my motherboard is http://www.gigabyte.com/products/product-page.aspx?pid=5189#sp lspci: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Please help me, this problem maybe affect a lot of people, is very annoying :´O( I’m just a poor latinoamerican boy. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1399129] Re: A system icon of iBus is not displayed in Kubuntu Plasma 5
** Attachment added: "kubuntu1504japanese.png" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1399129/+attachment/4402184/+files/kubuntu1504japanese.png -- 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/1399129 Title: A system icon of iBus is not displayed in Kubuntu Plasma 5 Status in IBus: Unknown Status in ibus package in Ubuntu: Triaged Bug description: In Kubuntu 14.10 Plasma 5, a system icon of iBus is not displayed. I installed Kubuntu 14.10 Plasma 5 in Japanese (日本語). Because iBus-Anthy is installed then, I change it to Anthy in Super+Space and can perform Japanese input again. but systray does not have an icon, and a big problem occurs in operability. This problem is one of the side effects of systray of Plasma 5 having changed the specifications: https://community.kde.org/Plasma/5.0_Errata http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/ As for this problem, bug report is performed in iBus: https://code.google.com/p/ibus/issues/detail?id=1749 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1399129/+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 1399129] Re: A system icon of iBus is not displayed in Kubuntu Plasma 5
As for this problem, solution was carried out on the iBus side: https://code.google.com/p/ibus/issues/detail?id=1749 but the problem that a system icon is not displayed is continued while iBus is installed when I installed Kubuntu 15.04 in Japanese. Therefore I report this comment and maintain current status. The live boot of Kubuntu 15.04 displays a status icon of iBus. Therefore a problem unlike Kubuntu 14.10 Plasma 5 may occur. -- 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/1399129 Title: A system icon of iBus is not displayed in Kubuntu Plasma 5 Status in IBus: Unknown Status in ibus package in Ubuntu: Triaged Bug description: In Kubuntu 14.10 Plasma 5, a system icon of iBus is not displayed. I installed Kubuntu 14.10 Plasma 5 in Japanese (日本語). Because iBus-Anthy is installed then, I change it to Anthy in Super+Space and can perform Japanese input again. but systray does not have an icon, and a big problem occurs in operability. This problem is one of the side effects of systray of Plasma 5 having changed the specifications: https://community.kde.org/Plasma/5.0_Errata http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/ As for this problem, bug report is performed in iBus: https://code.google.com/p/ibus/issues/detail?id=1749 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1399129/+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 1448636] Re: Suspend/resume failure misspells "occurred"
This bug was fixed in the package apport - 2.17.3-0ubuntu1 --- apport (2.17.3-0ubuntu1) wily; urgency=medium * New upstream release: - SECURITY UPDATE: When /proc/sys/fs/suid_dumpable is enabled, crashing a program that is suid root or not readable for the user would create root-owned core files in the current directory of that program. Creating specially crafted core files in /etc/logrotate.d or similar could then lead to arbitrary code execution with root privileges. Now core files do not get written for these kinds of programs, in accordance with the intention of core(5). Thanks to Sander Bos for discovering this issue! (CVE-2015-1324, LP: #1452239) - SECURITY UPDATE: When writing a core dump file for a crashed packaged program, don't close and reopen the .crash report file but just rewind and re-read it. This prevents the user from modifying the .crash report file while "apport" is running to inject data and creating crafted core dump files. In conjunction with the above vulnerability of writing core dump files to arbitrary directories this could be exploited to gain root privileges. Thanks to Philip Pettersson for discovering this issue! (CVE-2015-1325, LP: #1453900) - apportcheckresume: Fix "occured" typo, thanks Matthew Paul Thomas. (LP: #1448636) - signal_crashes test: Fix test_crash_setuid_* to look at whether suid_dumpable was enabled. - test/run: Run UI tests under dbus-launch, newer GTK versions require this now. -- Martin Pitt Wed, 20 May 2015 16:58:35 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1324 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1325 -- 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/1448636 Title: Suspend/resume failure misspells "occurred" Status in apport package in Ubuntu: Fix Released Bug description: apport 2.14.1-0ubuntu3.8, Ubuntu 14.04 1. Trigger a KernelOops (for example, by following the steps for bug 1298792 if it isn't fixed yet). 2. Choose "Show Details". 3. Expand the "Annotation" section. What you see: "This occured..." What you should see: "This occurred..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1448636/+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 1452239] Re: root escalation with fs.suid_dumpable=2
This bug was fixed in the package apport - 2.17.3-0ubuntu1 --- apport (2.17.3-0ubuntu1) wily; urgency=medium * New upstream release: - SECURITY UPDATE: When /proc/sys/fs/suid_dumpable is enabled, crashing a program that is suid root or not readable for the user would create root-owned core files in the current directory of that program. Creating specially crafted core files in /etc/logrotate.d or similar could then lead to arbitrary code execution with root privileges. Now core files do not get written for these kinds of programs, in accordance with the intention of core(5). Thanks to Sander Bos for discovering this issue! (CVE-2015-1324, LP: #1452239) - SECURITY UPDATE: When writing a core dump file for a crashed packaged program, don't close and reopen the .crash report file but just rewind and re-read it. This prevents the user from modifying the .crash report file while "apport" is running to inject data and creating crafted core dump files. In conjunction with the above vulnerability of writing core dump files to arbitrary directories this could be exploited to gain root privileges. Thanks to Philip Pettersson for discovering this issue! (CVE-2015-1325, LP: #1453900) - apportcheckresume: Fix "occured" typo, thanks Matthew Paul Thomas. (LP: #1448636) - signal_crashes test: Fix test_crash_setuid_* to look at whether suid_dumpable was enabled. - test/run: Run UI tests under dbus-launch, newer GTK versions require this now. -- Martin Pitt Wed, 20 May 2015 16:58:35 +0200 ** Changed in: apport (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1452239 Title: root escalation with fs.suid_dumpable=2 Status in Apport crash detection/reporting: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Precise: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Utopic: Fix Released Status in apport source package in Vivid: Fix Released Status in apport source package in Wily: Fix Released Bug description: Sander Bos discovered that Apport enabled a user to perform a root escalation since it now configures fs.suid_dumpable=2. Here's a brief description of the issue: 1- A regular user can trigger a coredump with /proc/$PID/stat as root:root simply by doing chmod u-r 2- The root-owned coredump will them be written in the CWD, which in the PoC is /etc/logrotate.d 3- logrotate will gladly skip parts of the coredump it doesn't understand and will successfully run the parts it does I've set a CRD of 2015-05-21 (original proposal: 2015-05-12) for the publication of this issue. I have assigned CVE-2015-1324 to this issue. We can either: 1- Disable fs.suid_dumpable=2 2- Stop creating core dump files when they are to be created as root 3- Create root-owned core dump files in a well-known location To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1452239/+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 1457093] Re: New upstream microreleases 9.1.16, 9.3.7, 9.4.2
All packages are in http://people.canonical.com/~pitti/tmp/psql-1457093/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1457093 Title: New upstream microreleases 9.1.16, 9.3.7, 9.4.2 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.4 package in Ubuntu: In Progress Status in postgresql-9.1 source package in Precise: In Progress Status in postgresql-9.1 source package in Trusty: In Progress Status in postgresql-9.3 source package in Trusty: In Progress Status in postgresql-9.4 source package in Utopic: In Progress Status in postgresql-9.4 source package in Vivid: In Progress Status in postgresql-9.4 source package in Wily: In Progress Bug description: PostgreSQL will push out new microreleases on Friday, 2015-05-22. The tarballs for the updates are not public yet, but the fixes are visible in the upstream git, so there's no need to treat this as embargoed, but there should still be a coordinated release. These fix a couple of security issues, as well as the usual set of bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1457093/+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 1457017] Re: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
The attachment "fglrx_15.2_preinst.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1457017 Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in fglrx-installer package in Ubuntu: Confirmed Bug description: Happened while I was updating via software updater. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:14.501-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 20 08:08:31 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:fglrx:2:14.501-0ubuntu1:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:047e] InstallationDate: Installed on 2015-02-25 (83 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=5423b7df-3038-4d4f-a0ce-8dcc2d8f3adb ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 15 09:44:22 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] 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] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1457017/+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 1027410] Re: Crash when opening a WMV file
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1027410 Title: Crash when opening a WMV file Status in libav package in Ubuntu: Expired Status in vlc package in Ubuntu: Invalid Bug description: There is a WMV file I am trying to play but VLC crashes when I open it : VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547) [0x9cbd908] main libvlc: Lancement de vlc avec l'interface par défaut. Utilisez « cvlc » pour démarrer VLC sans interface. [vc1 @ 0xb5304200] Bits overconsumption: 102040 > 102032 [vc1 @ 0xb5304200] concealing 837 DC, 837 AC, 837 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 22776 > 22768 [vc1 @ 0xb5304200] concealing 980 DC, 980 AC, 980 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 74392 > 74384 [vc1 @ 0xb5304200] concealing 366 DC, 366 AC, 366 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 39104 > 39096 at 38x19 [vc1 @ 0xb5304200] concealing 369 DC, 369 AC, 369 MV errors [0xb5100618] main input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 300 ms) [0xb5100618] main input error: ES_OUT_RESET_PCR called [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] block_len_bits 6 out of range [vc1 @ 0xb5304200] Bits overconsumption: 94824 > 94816 [vc1 @ 0xb5304200] concealing 1004 DC, 1004 AC, 1004 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 69064 > 69056 [vc1 @ 0xb5304200] concealing 630 DC, 630 AC, 630 MV errors [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] frame_len overflow [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] overflow in spectral RLE, ignoring [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] block_len_bits 5 out of range [wmav2 @ 0xb5322a20] block_len_bits 6 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] block_len_bits 4 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 4 out of range [vc1 @ 0xb5304200] Bits overconsumption: 80344 > 80336 [vc1 @ 0xb5304200] concealing 411 DC, 411 AC, 411 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 61368 > 61360 [vc1 @ 0xb5304200] concealing 753 DC, 753 AC, 753 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 53624 > 53616 at 0x22 [vc1 @ 0xb5304200] concealing 229 DC, 229 AC, 229 MV errors Erreur de segmentation (core dumped) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vlc 2.0.1-4 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 Date: Sat Jul 21 16:00:32 2012 ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to precise on 2012-04-27 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1027410/+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 1433382] Re: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling sounds using module-loopback
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1433382 Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling sounds using module-loopback Status in alsa-driver package in Ubuntu: Expired Bug description: I recently hooked up a SB X-Fi Surrount 5.1 Pro external sound card to my computer. It has a Line-In port which I wanted to use for playing audio from another computer. I enabled the loopback module like so: pactl load-module module-loopback And although I could then hear sound from Line-In, it was distorted by static, crackling sounds. I took the advice I found here: https://wiki.ubuntu.com/Audio/PositionReporting Making this change to /etc/pulse/default.pa: load-module module-udev-detect tsched=0 After rebooting and again loading the loopback module, the playback was static-free. As instructed by the above webpage, I'm filing this bug to track the issue and suggested solution. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66 Uname: Linux 3.2.0-77-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa62 irq 95' Mixer name : 'Realtek ALC898' Components : 'HDA:10ec0899,104384d8,0013' Controls : 47 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'Pro'/'Creative Technology Ltd SB X-Fi Surround 5.1 Pro at usb-:00:1d.0-1.3, high ' Mixer name : 'USB Mixer' Components : 'USB041e:3237' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 36' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Tue Mar 17 21:02:47 2015 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro successful Symptom_Card: GF114 HDMI Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 PRO 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.:bvr1104:bd04/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1433382/+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 1074137] Re: commands in menu of Libre Office Calc does not work after some time
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1074137 Title: commands in menu of Libre Office Calc does not work after some time Status in libreoffice package in Ubuntu: Expired Bug description: after a few commands, comands activated frommenu list do not work anymore. Menu is listed but command is not executed when clicked. Only commands via icons or keyboard shorcuts can be executed ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-core 1:3.6.2~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Thu Nov 1 21:45:11 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2012-10-20 (12 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1074137/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Assignee: (unassigned) => Matheus Salatiel (matheussnb) -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for "LUG" in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background
I'm encountering this regularly as well on Ubuntu 14.04.02 with Rhythmbox 3.0.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/978604 Title: Banshee/Rhythmbox regularly stop playing audio when left on in the background Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Precise: Confirmed Bug description: If Banshee or Rhythmbox is left playing in the background they will randomly stop playing in the latest builds of Ubuntu 12.04. Starting a new piece of music usually fixes the problem. If left to its own devices, the music will start playing again at some random time, at some random position. This problem exists on both my desktop machine (custom built Intel machine) and my laptop (Macbook 5,1). It has been happening for several months now. I became frustrated enough to load up pulseaudio in debugging mode. The log shows that when the music player just finishes playing one piece, and tries to start the next piece, you see something like this: --- ( 335.399| 34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to corking ( 335.400| 0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: before: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: after: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.400| 0.000) D: [alsa-sink] sink.c: latency = 1643 ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on render memblockq. ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on implementor. ( 335.400| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.400| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 dB 1: -28.11 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -28.00 dB 1: -28.00 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 0: 100% 1: 100% (accurate-enough=yes) ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -0.11 dB 1: -0.11 dB ( 335.402| 0.000) D: [alsa-sink] sink.c: Volume not changing ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes. ( 335.402| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: before: 3825 ( 335.402| 0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: after: 3825 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes. ( 335.402| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.402| 0.000) D: [alsa-sink] sink.c: latency = 1402 ( 335.402| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.402| 0.000) I: [pulseaudio] sink-input.c: Freeing input 3 "'zero-project - 05 - Forest of the unicorns' by 'zero-project'" ( 335.402| 0.000) D: [pulseaudio] module-stream-restore.c: Not restoring device for stream sink-input-by-media-role:music, because already set to 'alsa_output.pci-_00_1b.0.analog-stereo'. ( 335.403| 0.000) D: [pulseaudio] module-intended-roles.c: Not setting device for stream Playback Stream, because already set. ( 335.403| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume for sink input sink-input-by-media-role:music. ( 335.403| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute state for sink input sink-input-by-media-role:music. ( 335.403| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes busy. ( 335.403| 0.000) I: [pulseaudio] resampler.c: Forcing resampler 'copy', because of fixed, identical sample rates. ( 335.403| 0.000) I: [pulseaudio] resampler.c: Using resampler 'copy' ( 335.403| 0.000) I: [pulseaudio] resampler.c: Using float32le as working format. ( 335.403| 0.000) D: [pulseaudio] memblockq.c: memblockq requested: maxlength=33554432, tlength=0, base=4, prebuf=0, minreq=1 maxr
[Desktop-packages] [Bug 1088780] Re: XOrg configuration for Apple Magic Trackpad needs more vertical sensitivity
** No longer affects: elementaryos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1088780 Title: XOrg configuration for Apple Magic Trackpad needs more vertical sensitivity Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: By default, the Apple Magic Trackpad has way more horizontal sensitivity than vertical sensitivity, leading to weird results on wide screens and multiple monitor setups. This means that while you can span 1920 pixels with one horizontal swipe, you can't pan 1/3 of the 1080 pixels with one vertical swipe. The attached patch sets the horizontal and vertical resolution to be the same so that when you draw a circle on the track pad, you see a similar shape drawn by the mouse. Patch should either go into /usr/share/X11/xorg.conf.d/ or into /etc/X11/xorg.conf.d/. You must restart X in order to see changes with the touchpad. I'm preparing a similar patch for the Apple MacBook Pro built-in touch pad. ProblemType: Bug DistroRelease: elementary OS 0.2 Package: elementary-desktop 1.287-0~361~precise1 [origin: LP-PPA-elementary-os-daily] ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu15+elementary3~precise1 Architecture: amd64 CrashDB: elementary_meta Date: Mon Dec 10 21:52:30 2012 InstallationMedia: elementary OS 0.2 "Luna" - Beta 1 amd64 (20121114) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: elementary-meta SuspiciousXErrors: ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1088780/+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 1295247] Re: Cheese says "There was an error playing video from webcam"
Any word on this guys? I'm getting the same error as everybody else. I have a Dell XPS 12 - model name : Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz I'm running Kubuntu 14.04 - 32 Bit I've run different kernels from the Ubuntu repository with the same result: (Uname) Linux zubin-dell-xps-12 3.13.0-43-generic #51~14.04.1-Ubuntu SMP i686 i686 i686 GNU/Linux Linux zubin-dell-xps-12 3.16.0-37-generic #51~14.04.1-Ubuntu SMP i686 i686 i686 GNU/Linux $ lsusb Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 8087:09fa Intel Corp. Bus 002 Device 003: ID 0bda:5716 Realtek Semiconductor Corp. Bus 002 Device 002: ID 8087:07dc Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The Video Works perfect in VLC, therefor I don't think this is a V4L2 Problem However, It doesn't work with Cheese, Skype, guvcview $ cheese libv4l2: error got 4 consecutive frame decode errors, last error: v4l-convert: libjpeg error: End Of Image (cheese:13269): cheese-WARNING **: Internal data flow error.: gstbasesrc.c(2865): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin17/GstV4l2Src:video_source: streaming task paused, reason error (-5) GStreamer packages installed: $ dpkg -l | grep gstreamer ii gstreamer0.10-alsa:i3860.10.36-1.1ubuntu2 i386 GStreamer plugin for ALSA ii gstreamer0.10-nice:i3860.1.4-1 i386 ICE library (GStreamer 0.10 plugin) ii gstreamer0.10-plugins-bad:i386 0.10.23-7.2ubuntu1.1 i386 GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-bad-multiverse 0.10.21-1ubuntu3 i386 GStreamer plugins from the "bad" set (Multiverse Variant) ii gstreamer0.10-plugins-base:i3860.10.36-1.1ubuntu2 i386 GStreamer plugins from the "base" set ii gstreamer0.10-plugins-good:i3860.10.31-3+nmu1ubuntu5 i386 GStreamer plugins from the "good" set ii gstreamer0.10-plugins-ugly:i3860.10.19-2ubuntu5 i386 GStreamer plugins from the "ugly" set ii gstreamer0.10-pulseaudio:i386 0.10.31-3+nmu1ubuntu5 i386 GStreamer plugin for PulseAudio ii gstreamer0.10-qapt 2.1.70-0ubuntu4.2 i386 GStreamer plugin to install codecs using QApt ii gstreamer0.10-x:i386 0.10.36-1.1ubuntu2 i386 GStreamer plugins for X11 and Pango ii gstreamer1.0-alsa:i386 1.2.4-1~ubuntu1 i386 GStreamer plugin for ALSA ii gstreamer1.0-clutter 2.0.8-1build1 i386 Clutter PLugin for GStreamer 1.0 ii gstreamer1.0-libav:i3861.2.4-1~ubuntu1 i386 libav plugin for GStreamer ii gstreamer1.0-plugins-bad-faad:i386 1.2.4-1~ubuntu1 i386 GStreamer faad plugin from the "bad" set ii gstreamer1.0-plugins-bad-videoparsers:i386 1.2.4-1~ubuntu1 i386 GStreamer videoparsers plugin from the "bad" set ii gstreamer1.0-plugins-base:i386 1.2.4-1~ubuntu1 i386 GStreamer plugins from the "base" set ii gstreamer1.0-plugins-good:i386 1.2.4-1~ubuntu1 i386 GStreamer plugins from the "good" set ii gstreamer1.0-pulseaudio:i386 1.2.4-1~ubuntu1 i386 GStreamer plugin for PulseAudio ii gstreamer1.0-x:i3861.2.4-1~ubuntu1 i386 GStreamer plugins for X11 and Pango ii libgstreamer-plugins-bad0.10-0:i3860.10.23-7.2ubuntu1.1 i386 GStreamer shared libraries from the "bad" set ii libgstreamer-plugins-bad1.0-0:i386 1.2.4-1~ubuntu1 i386 GStreamer development files for libraries from the "bad" set ii libgstreamer-plugins-base0.10-0:i386 0.10.36-1.1ubuntu2 i386 GStreamer libraries from the "base" set ii libgstreamer-plugins-base1.0-0:i3861.2.4-1~ubuntu1 i386 GStreamer libraries from the "base" set ii libgstreamer-plugins-good1.0-0:i3861.2
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Tags removed: hang verification-needed ** Tags added: verification-done-precise verification-needed-utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+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 1456667] Re: package fglrx 2:14.501-0ubuntu1 [modified: usr/bin/aticonfig usr/bin/atiode usr/bin/fgl_glxgears usr/bin/fglrxinfo usr/lib/fglrx/libGL.so.1.2 usr/sbin/atieventsd]
*** This bug is a duplicate of bug 1457017 *** https://bugs.launchpad.net/bugs/1457017 ** This bug has been marked a duplicate of bug 1457017 package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1456667 Title: package fglrx 2:14.501-0ubuntu1 [modified: usr/bin/aticonfig usr/bin/atiode usr/bin/fgl_glxgears usr/bin/fglrxinfo usr/lib/fglrx/libGL.so.1.2 usr/sbin/atieventsd] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in fglrx-installer package in Ubuntu: Confirmed Bug description: the last update of fglrx does not install on ubuntu 14.04 64 bits. I have a AMD 7600 HD and I intalled manually the Omega driver a few months ago. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:14.501-0ubuntu1 [modified: usr/bin/aticonfig usr/bin/atiode usr/bin/fgl_glxgears usr/bin/fglrxinfo usr/lib/fglrx/libGL.so.1.2 usr/sbin/atieventsd] ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 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: Tue May 19 09:17:21 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.16.0-37-generic, x86_64: installed vboxhost, 4.3.28, 3.16.0-37-generic, x86_64: installed DuplicateSignature: package:fglrx:2:14.501-0ubuntu1 [modified: usr/bin/aticonfig usr/bin/atiode usr/bin/fgl_glxgears usr/bin/fglrxinfo usr/lib/fglrx/libGL.so.1.2 usr/sbin/atieventsd]:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1659] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6490M [103c:1659] InstallationDate: Installed on 2015-02-28 (80 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Casablanca H510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=8f55ec4e-4ab9-470f-ba78-f7df51f66c91 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: package fglrx 2:14.501-0ubuntu1 [modified: usr/bin/aticonfig usr/bin/atiode usr/bin/fgl_glxgears usr/bin/fglrxinfo usr/lib/fglrx/libGL.so.1.2 usr/sbin/atieventsd] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1659 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPCasablancaH510:pvr059C1020210011034:rvnHewlett-Packard:rn1659:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Casablanca H510 dmi.product.version: 059C1020210011034 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 19 08:14:06 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object f
[Desktop-packages] [Bug 1457017] Re: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Looks like is in preinst script. It backups /etc/ati folder with user settings and then tries to delete the original dir with "rm -f /etc/ati 2>/dev/null" but this fail because it is a dir. The solution is to add recursive flag, after repacking with modified preinst dpkg succesfully installed the package. ** Patch added: "fglrx_15.2_preinst.diff" https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1457017/+attachment/4402138/+files/fglrx_15.2_preinst.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1457017 Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in fglrx-installer package in Ubuntu: Confirmed Bug description: Happened while I was updating via software updater. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:14.501-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 20 08:08:31 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:fglrx:2:14.501-0ubuntu1:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:047e] InstallationDate: Installed on 2015-02-25 (83 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=5423b7df-3038-4d4f-a0ce-8dcc2d8f3adb ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 15 09:44:22 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] 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] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1457017/+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.
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Changed in: gvfs Status: Unknown => Fix Released ** Changed in: gvfs Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+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 1445520] Re: Orca crach at startup
I am not an expert on Orca internals. As I said earlier, something is broken on your system, I don't know what it is. Try re-installing the packages I suggested you try re-installing in an earlier post, and report back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1445520 Title: Orca crach at startup Status in gnome-orca package in Ubuntu: New Bug description: Hello, Orca description : Package: gnome-orca Priority: optional Section: gnome Installed-Size: 5932 Maintainer: Ubuntu Developers Original-Maintainer: Debian Accessibility Team Architecture: all Version: 3.10.3-0ubuntu1 Replaces: gnome-orca-common (<< 2.20.1-2) Depends: python3:any (>= 3.3.2-2~), python3, python3-speechd (>= 0.6.2), python3-gi (>= 3.4.2), python3-pyatspi (>= 2.6), python3-brlapi, python3-louis (>= 1.6.2), gir1.2-glib-2.0, gir1.2-pango-1.0, gir1.2-gtk-3.0 (>= 3.6.2), gir1.2-wnck-3.0 Conflicts: gnome-orca-common (<< 2.20.1-2) Filename: pool/main/g/gnome-orca/gnome-orca_3.10.3-0ubuntu1_all.deb Size: 751948 MD5sum: a08528efb758b14b06c6ac1f9735bc64 SHA1: fb59e3b98ed163f633490e99393fcd347490c877 SHA256: 88274fd630f476598ddaa3cb86b7a0a741aa9a521512bd4ba79291dc79a2d944 Description-fr: Lecteur d'écran programmable Orca est une technologie d'assistance flexible, extensible et puissante qui fournit un accès pour les utilisateurs finaux aux applications et boîte à outils qui supporte le AT-SPI (comme par exemple le bureau GNOME). Avec un retour rapide et un engagement continu envers ses utilisateurs, Orca a été conçu et implémenté par le programme d'accessibilité de Sun Microsystems, Inc. . Orca définit un ensemble de comportements par défaut (réactions aux évènements des applications) et aux raccourcis clavier. Ces comportements par défaut et raccourcis clavier peuvent être modifiés pour chaque application. Orca crée un objet script pour chaque application fonctionnant sur le système et fusionne les comportements par défaut avec les raccourcis clavier et les paramètres spécifiques dédiés à cette application. Orca fournit l'infrastructure pour activer et désactiver les scripts mais aussi un hôte des services accessible depuis les scripts. Description-md5: f65a62b4ea6bad4bd1544c0d34a697ce Homepage: http://live.gnome.org/Orca Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 5y Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb, ubuntustudio-desktop, ubuntu-gnome-desktop oython 3 description Package: python3 Priority: important Section: python Installed-Size: 100 Maintainer: Ubuntu Developers Original-Maintainer: Matthias Klose Architecture: amd64 Source: python3-defaults Version: 3.4.0-0ubuntu2 Replaces: python3-minimal (<< 3.1.2-2) Provides: python3-profiler Depends: python3.4 (>= 3.4.0-0~), python3-minimal (= 3.4.0-0ubuntu2), libpython3-stdlib (= 3.4.0-0ubuntu2), dh-python Suggests: python3-doc (>= 3.4.0-0ubuntu2), python3-tk (>= 3.4.0-0ubuntu2) Filename: pool/main/p/python3-defaults/python3_3.4.0-0ubuntu2_amd64.deb Size: 8666 MD5sum: bfb7da0b87a977d7c8810d41aa151ba0 SHA1: 63e38e68c45e194311ee68d9d81cb900283f4c5b SHA256: e1856a097784129b4a52c31c348fadd4eb82097762bcd652179946ebfab4592b Description-fr: Langage interactif de haut niveau orienté objet (version python3 par défaut) Python, le langage de haut niveau, orienté objet, interactif, comprend une bibliothèque de classes étendue et pleine de bonnes choses pour la programmation réseau, l'administration système, le son et le graphisme. . This package is a dependency package, which depends on Debian's default Python 3 version (currently v3.4). Description-md5: d2d5b9ee5047a791224f1b8f4bc73d3b Multi-Arch: allowed Homepage: http://www.python.org/ Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 5y Task: minimal My configuration : ubuntu 14.04 Packagge affect Orca gnome Python 3 I have installed orca package on ubuntu 14.04 LTS 64 bit. However, it seems crash at startup. See the python 3 log at attachment file for more details. Could you help me please ? Thanks by advance Best regards Battant PS srr log orca at : http://www.parcheto.ch/owncloud/index.php/s/FHmTaUsJOu3fEtT --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-29 (82 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) Package: gnome-orca 3.10.3-0ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Tags: trusty Uname: Linux 3.13.0-49-generic x86_64 UpgradeStatus: Upgraded to trusty on 2015-03-
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.2 --- accountsservice (0.6.35-0ubuntu7.2) trusty-proposed; urgency=medium * debian/patches/0010-set-language.patch: Use static variables inside user_get_fallback_value() to prevent execution of expensive code at each invocation (LP: #1443178). -- Gunnar Hjalmarsson Tue, 12 May 2015 18:30:00 +0200 ** Changed in: accountsservice (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443178 Title: Accounts Service always relies on language fallback if never set by the user Status in the base for Ubuntu mobile products: New Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: Fix Released Status in accountsservice source package in Vivid: Fix Released Bug description: trusty and vivid SRU requests = [Impact] Until a user has set the language or regional formats explicitly, accountsservice makes the system default values available. The code for 'calculating' the system defaults is expensive, and it's triggered frequently. The case in the original description of this bug report is one example of bad performance for this reason. Another example is a system with many users (see e.g. bug #1350393). This upload adds a couple of static variables inside the function in question, to avoid that the expensive code is executed at each invocation. Under certain conditions this improves the performance significantly. [Test Case] Hmm.. There is no easy use case to reproduce the bug. The original description below gives a hint. [Regression Potential] On a multi-user system, if the system defaults in /etc/default/locale are changed, accountsservice will keep providing the old system default values until the system is rebooted. (Previously it took effect instantly.) I think the advantages with the proposed change outweigh this subtle change in behavior (which hardly anyone will notice anyway). Can't think of anything besides that. [Original description] current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 This causes a bad side effect when changing volume via indicator- sound, as that will cause a sync to accountsservice in order to sync the volume. Once that sync happens, it will request the user properties, and in case the user doesn't have a valid language at /var/lib/AccountsService/users/, it will always rely on the fallback, which would be fine if calculating the fallback wasn't 't so cpu or i/o intensive (and that happens multiple times). As a test, just flash latest vivid image on mako, don't set any language when the wizard shows up, run top and then change the volume by pressing volume up/down. This is what I see with mako: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8 5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19 language-option 1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25 unity-system-co 1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66 accounts-daemon And the reason why: src/user.c ... static void user_get_property (GObject*object, guint param_id, GValue *value, GParamSpec *pspec) { User *user = USER (object); ... case PROP_LANGUAGE: if (user->language) g_value_set_string (value, user->language); else g_value_set_string (value, user_get_fallback_value (user, "Language")); break; case PROP_FORMATS_LOCALE: if (user->formats_locale) g_value_set_string (value, user->formats_locale); else g_value_set_string (value, user_get_fallback_value (user, "FormatsLocale")); break; user_set_property never gets called unless the user changes the system language from system-settings or wizard. Once you change the language, it will set a valid language at /var/lib/AccountsService/users/, causing this behavior to stop. Another bad side effect of this issue is that it takes quite a while for accountsservice to reply back to indicator-sound when the sync happens, possibly causing sync aborts (as indicator-sound only waits 1 second before triggering another sync).
[Desktop-packages] [Bug 1455212] Re: IPP-over-USB support broken
This bug was fixed in the package system-config-printer - 1.5.6+20150318-0ubuntu2.1 --- system-config-printer (1.5.6+20150318-0ubuntu2.1) vivid-proposed; urgency=medium * debian/patches/33_ipp-over-usb-support.patch: Fixes on IPP-over-USB support, to make auto-setup of print queues work correctly again, for both devices supporting and not supporting IPP-over-USB (LP: #1455212). -- Till Kamppeter Thu, 14 May 2015 17:02:47 -0300 ** Changed in: system-config-printer (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1455212 Title: IPP-over-USB support broken Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Vivid: Fix Released Bug description: The support for IPP-over-USB printers in udev-configure-printer is broken, leading to the following two problems: 1. If the printer connected to USB supports IPP-over-USB, the automatic generation of a print queue can hang for three minutes 2. If the printer connected to USB does not support IPP-over-USB udev- configure-printer calls ippusbxd anyway and errors out, not creating a print queue. This occurs in Vivid and Wily. [Impact] All Vivid users with a USB printer will not get automatic setup of print queues (printer does not do IPP-over-USB) or a print queue setup delayed by around 3 minutes (IPP-over-USB printers). [Test Case] Connect a USB printer for which there is not yet set up a local print queue. Usually within some seconds a print queue is set up automatically for it. No queue gets set up, for IPP-over-USB printers it takes around three minutes to get a print queue. The proposed package fixes this problem. [Regression Potential] Very low. The patch is trivial and it affects only the automatic setup of USB printers. Network printer setup and manual setup of USB printers or printing on already existing queues is not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1455212/+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 1455868] Re: improve visibility of currently active tab
Please: 1. Add an screen-shot of this bug. 2. Set this bug status back to "confirmed". Thank you. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Incomplete -- 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/1455868 Title: improve visibility of currently active tab Status in gnome-terminal package in Ubuntu: Incomplete Bug description: improve visibility of currently active tab ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 Uname: Linux 4.0.1-040001-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 10:04:46 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (44 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1455868/+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 1455212] Update Released
The verification of the Stable Release Update for system-config-printer has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1455212 Title: IPP-over-USB support broken Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Vivid: Fix Released Bug description: The support for IPP-over-USB printers in udev-configure-printer is broken, leading to the following two problems: 1. If the printer connected to USB supports IPP-over-USB, the automatic generation of a print queue can hang for three minutes 2. If the printer connected to USB does not support IPP-over-USB udev- configure-printer calls ippusbxd anyway and errors out, not creating a print queue. This occurs in Vivid and Wily. [Impact] All Vivid users with a USB printer will not get automatic setup of print queues (printer does not do IPP-over-USB) or a print queue setup delayed by around 3 minutes (IPP-over-USB printers). [Test Case] Connect a USB printer for which there is not yet set up a local print queue. Usually within some seconds a print queue is set up automatically for it. No queue gets set up, for IPP-over-USB printers it takes around three minutes to get a print queue. The proposed package fixes this problem. [Regression Potential] Very low. The patch is trivial and it affects only the automatic setup of USB printers. Network printer setup and manual setup of USB printers or printing on already existing queues is not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1455212/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
This bug was fixed in the package accountsservice - 0.6.37-1ubuntu10.1 --- accountsservice (0.6.37-1ubuntu10.1) vivid-proposed; urgency=medium * debian/patches/0010-set-language.patch: Use static variables inside user_get_fallback_value() to prevent execution of expensive code at each invocation (LP: #1443178). -- Gunnar Hjalmarsson Tue, 12 May 2015 17:44:00 +0200 ** Changed in: accountsservice (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443178 Title: Accounts Service always relies on language fallback if never set by the user Status in the base for Ubuntu mobile products: New Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: Fix Committed Status in accountsservice source package in Vivid: Fix Released Bug description: trusty and vivid SRU requests = [Impact] Until a user has set the language or regional formats explicitly, accountsservice makes the system default values available. The code for 'calculating' the system defaults is expensive, and it's triggered frequently. The case in the original description of this bug report is one example of bad performance for this reason. Another example is a system with many users (see e.g. bug #1350393). This upload adds a couple of static variables inside the function in question, to avoid that the expensive code is executed at each invocation. Under certain conditions this improves the performance significantly. [Test Case] Hmm.. There is no easy use case to reproduce the bug. The original description below gives a hint. [Regression Potential] On a multi-user system, if the system defaults in /etc/default/locale are changed, accountsservice will keep providing the old system default values until the system is rebooted. (Previously it took effect instantly.) I think the advantages with the proposed change outweigh this subtle change in behavior (which hardly anyone will notice anyway). Can't think of anything besides that. [Original description] current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 This causes a bad side effect when changing volume via indicator- sound, as that will cause a sync to accountsservice in order to sync the volume. Once that sync happens, it will request the user properties, and in case the user doesn't have a valid language at /var/lib/AccountsService/users/, it will always rely on the fallback, which would be fine if calculating the fallback wasn't 't so cpu or i/o intensive (and that happens multiple times). As a test, just flash latest vivid image on mako, don't set any language when the wizard shows up, run top and then change the volume by pressing volume up/down. This is what I see with mako: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8 5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19 language-option 1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25 unity-system-co 1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66 accounts-daemon And the reason why: src/user.c ... static void user_get_property (GObject*object, guint param_id, GValue *value, GParamSpec *pspec) { User *user = USER (object); ... case PROP_LANGUAGE: if (user->language) g_value_set_string (value, user->language); else g_value_set_string (value, user_get_fallback_value (user, "Language")); break; case PROP_FORMATS_LOCALE: if (user->formats_locale) g_value_set_string (value, user->formats_locale); else g_value_set_string (value, user_get_fallback_value (user, "FormatsLocale")); break; user_set_property never gets called unless the user changes the system language from system-settings or wizard. Once you change the language, it will set a valid language at /var/lib/AccountsService/users/, causing this behavior to stop. Another bad side effect of this issue is that it takes quite a while for accountsservice to reply back to indicator-sound when the sync happens, possibly causing sync aborts (as indicator-sound only waits 1 second before triggering another sync).
[Desktop-packages] [Bug 1452318] Re: Faulty behavior when resuming from suspend
** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1452318 Title: Faulty behavior when resuming from suspend Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Waking from suspend, everything seems normal, except the graphical elements and text on my desktop are not drawn properly. Sometimes, moving the mouse over icons can cause them to be redrawn, sometimes not. It appears not to matter how I initiate the suspend (e.g. by closing laptop lid, or by calling pm-suspend explicitly) and it appears not to matter whether I am using an external display or the laptop's own screen. All other hardware appears to be working, and I can restart the laptop by clicking where the icons ought to be. The only symptom seems to be that the drawing does not happen correctly. I'm not sure what additional information I should provide to help diagnose the problem, so please advise me. Also, if this is more likely to be a xfce issue, then please change the package on the bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 6 17:17:51 2015 InstallationDate: Installed on 2015-05-04 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318/+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 1439220] Re: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignorin
** Changed in: ubuntu-gnome-default-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1439220 Title: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu- settings.gschema.override'; ignoring override for this key. Status in ubuntu-gnome-default-settings package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: Get that error now when installing a package (synaptic install dialog box) Unpacking nautilus (1:3.14.2-0ubuntu8) over (1:3.14.2-0ubuntu6) ... Processing triggers for libglib2.0-0:i386 (2.44.0-1) ... No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. note: i have installed the 3.16 version of gsettings-desktop-schemas (gnome3-staging ppa), so maybe it is related to. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libglib2.0-0 2.44.0-1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Apr 1 16:06:11 2015 SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1439220/+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 1445039] Re: Device '/dev/video0' is busy
** Changed in: cheese (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1445039 Title: Device '/dev/video0' is busy Status in cheese package in Ubuntu: Confirmed Bug description: First time I run cheese during the day, an attempt to take a picture typically results in an error being displayed on a black background in the preview pane "There was an error playing video from the webcam" (odd for two reasons, one I'm taking a picture, not video, and two... it's an error message that indicated something indeed went wrong) (cheese:2506): cheese-WARNING **: Device '/dev/video0' is busy: gstv4l2object.c(2838): gst_v4l2_object_set_format (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:video_source: Call to S_FMT failed for YU12 @ 1280x720: Device or resource busy webcam: description: Video product: HD WebCam vendor: NC.21411.01N415006E5LM0002 physical id: 1 bus info: usb@3:1.1 version: 0.02 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s linux: Linux Hedy 3.19.0-13-generic #13-Ubuntu SMP Thu Apr 9 22:56:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ubuntu : 15.04 cheese: Installed: 3.14.1-2ubuntu4 Candidate: 3.14.1-2ubuntu4 The timer goes off, flash goes off, but no photo is saved in my ~/Webcam directory. Attempts to take video, or attempts to take a few pictures using root seem to clear this problem up and after I have done so, cheese seems to be initialized correctly, and it works fine for awhile. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: cheese 3.14.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 16 10:20:25 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (280 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1445039/+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 1440032] Re: nm-applet is missing the Sierra EM7345 4G LTE
** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1440032 Title: nm-applet is missing the Sierra EM7345 4G LTE Status in network-manager-applet package in Ubuntu: Confirmed Bug description: The current system Ubuntu 15.04 Beta2 (up2date) is missing the nm- applet after restarting the system. It might be a problem with the Sierra EM7345 module?! After the new install of Ubuntu 15.04 Beta2 i saw the Sierra for one or two times inside the nm-applet and i could create a mobile-data connection over HSDPA/UMTS/LTE. But just for this time. Now, after some regular updates, the Sierra Card is not accessable inside the nm-applet menu for creating a new mobile data connection, the old connection profil is missing too. The Sierra EM7345 was also named as cdc-wdm not by name. [ 2.277029] usb 1-4: New USB device found, idVendor=1199, idProduct=a001 [ 2.277031] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.277033] usb 1-4: Product: Sierra Wireless EM7345 4G LTE [ 2.277034] usb 1-4: Manufacturer: Sierra Wireless Inc. [ 2.277035] usb 1-4: SerialNumber: 013937003691337 # lsusb Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 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 006: ID 04f2:b449 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. Bus 001 Device 002: ID 1199:a001 Sierra Wireless, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager-gnome 0.9.10.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 3 13:24:21 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-04-02 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 1024 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.193 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 5ghz.offlinehoster.de e1d2c80e-d6c2-4029-80bd-ed4e93fac4d5 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 15.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-04-03 (18 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) IpRoute: default via 10.100.1.1 dev eth0 proto static metric 1024 10.100.1.0/24 dev eth0 proto kernel scope link src 10.100.1.99 169.254.0.0/16 dev eth0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false WimaxEnabled=true Package: network-manager-applet (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID
[Desktop-packages] [Bug 1449959] Re: Running ./unity --replace ... terminates the session and starts a new one on vivid
This bug was fixed in the package gnome-session - 3.14.0-2ubuntu5 --- gnome-session (3.14.0-2ubuntu5) vivid; urgency=medium * In 3.14.0-2ubuntu1, RequiredComponents of ubuntu (unity)'s session file incorrectly gained compiz. This caused compiz to be started by gnome-session and not to be managed by upstart in user sessions meaning, for example, that it won't be restarted correctly in the event of a crash. (LP: #1449959) -- Iain Lane Wed, 29 Apr 2015 12:01:55 +0100 ** Changed in: gnome-session (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1449959 Title: Running ./unity --replace ... terminates the session and starts a new one on vivid Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Vivid: Fix Released Bug description: [ Description ] Due to an error when merging with Debian, ubuntu's gnome-session file is inadvertantly starting compiz when it should instead be managed by upstart. This means that we don't, for example, have unity restarted by upstart if it crashes and (as the reporter of this bug notes) unity --replace breaks due to gnome-session tearing the session down if one of its required components goes away and comes back. [ Fix ] Remove "compiz;" from ubuntu.session so that the unity7.conf shipped by unity is used. [ QA ] Verify that you see the following before upgrading laney@raleigh> status unity7 unity7 stop/waiting laney@raleigh> pstree -s -p $(pidof compiz) systemd(1)───lightdm(1625)───lightdm(10651)───upstart(10864)───gnome-session(11094)───compiz(11374)─┬─{dconf worker}(11382) ├─{gdbus}(11383) └─{gmain}(11376) i.e. compiz is a child of gnome-session, and the unity7 job isn't running. and this after laney@raleigh> status unity7 unity7 start/running, process 8945 laney@raleigh> pstree -s -p $(pidof compiz) systemd(1)───lightdm(1625)───lightdm(8487)───upstart(8715)───compiz(8945)─┬─{dconf worker}(8972) ├─{gdbus}(8976) └─{gmain}(8950) compiz is a direct child of upstart and the unity7 job is running. Additionally, verify that unity --replace kicks you back to the display manager before and unity is replaced in-session after. [ Regression potential ] unity's job is now used instead of upstart being started by gnome-session. This was the case since we started having upstart in the session, but make sure that login and logout still work properly. [ Original description ] Running ./unity --replace on vivid (systemd) exits the session and the login screen of lightdm appears. After log in, a new session starts. Steps: 1- build unity 2- run ./unity --replace with the env. variables and parameters you used on utopic 3- see the lightdm login screen and login ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-session 3.14.0-2ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 29 13:15:16 2015 InstallationDate: Installed on 2014-07-04 (299 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1449959/+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 1449959] Update Released
The verification of the Stable Release Update for gnome-session has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1449959 Title: Running ./unity --replace ... terminates the session and starts a new one on vivid Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Vivid: Fix Released Bug description: [ Description ] Due to an error when merging with Debian, ubuntu's gnome-session file is inadvertantly starting compiz when it should instead be managed by upstart. This means that we don't, for example, have unity restarted by upstart if it crashes and (as the reporter of this bug notes) unity --replace breaks due to gnome-session tearing the session down if one of its required components goes away and comes back. [ Fix ] Remove "compiz;" from ubuntu.session so that the unity7.conf shipped by unity is used. [ QA ] Verify that you see the following before upgrading laney@raleigh> status unity7 unity7 stop/waiting laney@raleigh> pstree -s -p $(pidof compiz) systemd(1)───lightdm(1625)───lightdm(10651)───upstart(10864)───gnome-session(11094)───compiz(11374)─┬─{dconf worker}(11382) ├─{gdbus}(11383) └─{gmain}(11376) i.e. compiz is a child of gnome-session, and the unity7 job isn't running. and this after laney@raleigh> status unity7 unity7 start/running, process 8945 laney@raleigh> pstree -s -p $(pidof compiz) systemd(1)───lightdm(1625)───lightdm(8487)───upstart(8715)───compiz(8945)─┬─{dconf worker}(8972) ├─{gdbus}(8976) └─{gmain}(8950) compiz is a direct child of upstart and the unity7 job is running. Additionally, verify that unity --replace kicks you back to the display manager before and unity is replaced in-session after. [ Regression potential ] unity's job is now used instead of upstart being started by gnome-session. This was the case since we started having upstart in the session, but make sure that login and logout still work properly. [ Original description ] Running ./unity --replace on vivid (systemd) exits the session and the login screen of lightdm appears. After log in, a new session starts. Steps: 1- build unity 2- run ./unity --replace with the env. variables and parameters you used on utopic 3- see the lightdm login screen and login ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-session 3.14.0-2ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 29 13:15:16 2015 InstallationDate: Installed on 2014-07-04 (299 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1449959/+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 1445134] Re: Network manager never scanning for new access points
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- 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/1445134 Title: Network manager never scanning for new access points Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+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 1450724] Re: Epiphany browser doesn't show most visited page
** Changed in: epiphany-browser (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1450724 Title: Epiphany browser doesn't show most visited page Status in epiphany-browser package in Ubuntu: Confirmed Bug description: Epiphany browser doesn't show the most visited page, only some cryptic symbols are displayed. It worked without problems in Ubuntu 14.10. before I updated to 15.04. An update of webkit2gtk from WebKit Team stable ppa didn't help. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: epiphany-browser 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri May 1 09:38:38 2015 InstallationDate: Installed on 2015-01-09 (112 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - i386 (20141023) SourcePackage: epiphany-browser UpgradeStatus: Upgraded to vivid on 2015-04-23 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1450724/+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 1415188] Re: DuckDuckGo search plugin is outdated
** Changed in: firefox (Ubuntu) Importance: Undecided => Medium ** Changed in: firefox (Ubuntu) Importance: Medium => Low ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1415188 Title: DuckDuckGo search plugin is outdated Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: It seems that Ubuntu overrides Firefox's DuckDuckGo search plugin with a version that doesn't support search suggestions. e.g. I receive this file: http://bazaar.launchpad.net/~mozillateam/firefox/firefox.utopic/view/head:/debian/searchplugins/en-US/duckduckgo.xml While Mozilla already includes their own DuckDuckGo search plugin which supports search suggestions: https://hg.mozilla.org/mozilla-central/file/bf58b2c55797/browser/locales/en-US/searchplugins/ddg.xml To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1415188/+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 1455097] Re: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
** Changed in: pm-utils (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid Status in pm-utils package in Ubuntu: Confirmed Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1455097/+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 1445520] Re: Orca crach at startup
Hello, I see this python exception Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 242, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'labelAndName' is not definedTraceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 242, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'labelAndName' is not defined Could you help me to fix it ? Best regards Battant -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1445520 Title: Orca crach at startup Status in gnome-orca package in Ubuntu: New Bug description: Hello, Orca description : Package: gnome-orca Priority: optional Section: gnome Installed-Size: 5932 Maintainer: Ubuntu Developers Original-Maintainer: Debian Accessibility Team Architecture: all Version: 3.10.3-0ubuntu1 Replaces: gnome-orca-common (<< 2.20.1-2) Depends: python3:any (>= 3.3.2-2~), python3, python3-speechd (>= 0.6.2), python3-gi (>= 3.4.2), python3-pyatspi (>= 2.6), python3-brlapi, python3-louis (>= 1.6.2), gir1.2-glib-2.0, gir1.2-pango-1.0, gir1.2-gtk-3.0 (>= 3.6.2), gir1.2-wnck-3.0 Conflicts: gnome-orca-common (<< 2.20.1-2) Filename: pool/main/g/gnome-orca/gnome-orca_3.10.3-0ubuntu1_all.deb Size: 751948 MD5sum: a08528efb758b14b06c6ac1f9735bc64 SHA1: fb59e3b98ed163f633490e99393fcd347490c877 SHA256: 88274fd630f476598ddaa3cb86b7a0a741aa9a521512bd4ba79291dc79a2d944 Description-fr: Lecteur d'écran programmable Orca est une technologie d'assistance flexible, extensible et puissante qui fournit un accès pour les utilisateurs finaux aux applications et boîte à outils qui supporte le AT-SPI (comme par exemple le bureau GNOME). Avec un retour rapide et un engagement continu envers ses utilisateurs, Orca a été conçu et implémenté par le programme d'accessibilité de Sun Microsystems, Inc. . Orca définit un ensemble de comportements par défaut (réactions aux évènements des applications) et aux raccourcis clavier. Ces comportements par défaut et raccourcis clavier peuvent être modifiés pour chaque application. Orca crée un objet script pour chaque application fonctionnant sur le système et fusionne les comportements par défaut avec les raccourcis clavier et les paramètres spécifiques dédiés à cette application. Orca fournit l'infrastructure pour activer et désactiver les scripts mais aussi un hôte des services accessible depuis les scripts. Description-md5: f65a62b4ea6bad4bd1544c0d34a697ce Homepage: http://live.gnome.org/Orca Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 5y Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb, ubuntustudio-desktop, ubuntu-gnome-desktop oython 3 description Package: python3 Priority: important Section: python Installed-Size: 100 Maintainer: Ubuntu Developers Original-Maintainer: Matthias Klose Architecture: amd64 Source: python3-defaults Version: 3.4.0-0ubuntu2 Replaces: python3-minimal (<< 3.1.2-2) Provides: python3-profiler Depends: python3.4 (>= 3.4.0-0~), python3-minimal (= 3.4.0-0ubuntu2), libpython3-stdlib (= 3.4.0-0ubuntu2), dh-python Suggests: python3-doc (>= 3.4.0-0ubuntu2), python3-tk (>= 3.4.0-0ubuntu2) Filename: pool/main/p/python3-defaults/python3_3.4.0-0ubuntu2_amd64.deb Size: 8666 MD5sum: bfb7da0b87a977d7c8810d41aa151ba0 SHA1: 63e38e68c45e194311ee68d9d81cb900283f4c5b SHA256: e1856a097784129b4a52c31c348fadd4eb82097762bcd652179946ebfab4592b Description-fr: Langage interactif de haut niveau orienté objet (version python3 par défaut) Python, le langage de haut niveau, orienté objet, interactif, comprend une bibliothèque de classes étendue et pleine de bonnes choses pour la programmation réseau, l'administration système, le son et le graphisme. . This package is a dependency package, which depends on Debian's default Python 3 version (currently v3.4). Description-md5: d2d5b9ee5047a791224f1b8f4bc73d3b Multi-Arch: allowed Homepage: http://www.python.org/ Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 5y Task: minimal My configuration : ubuntu 14.04 Packagge affect Orca gnome Python 3 I have installed orca package on ubuntu 14.04 LTS 64 bit. However, it seems crash at startup. See the python 3 log at attachment file for more details. Could you help me please ? Thanks by advance Best regards Battant PS srr log orca at : http://www.parcheto.ch/owncloud/index.php/s/FHmTaUsJOu3fEtT --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-29 (82 days ag
[Desktop-packages] [Bug 1455711] Re: pidgin icon does not appear in the System Tray on kde 5
** Changed in: pidgin (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1455711 Title: pidgin icon does not appear in the System Tray on kde 5 Status in pidgin package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 15.04 pidgin does not appear in the System Tray area. As additional information I can say that is not the only, but applications such as skype or dropbox neither do. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 16 00:19:41 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-16 (0 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1455711/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
Package nvidia-graphics-drivers-331 (Ubuntu) is still no fixed. After update i have still this same error -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for "LUG" in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 1165104] Re: oneconf is only showing the pc you are on in raring and isn't sharing to other machines
** Description changed: + [Impact] + + The package synchronization in the Ubuntu Software Center doesn't work, + and only the current machine is displayed. + + + [Test Case] + + At least two computers (or virtual machines) are needed. + + First, enable software sync in both computers, by opening the Ubuntu + Software Center, then clicking "File > Sync Between Computers" in the + menu in each computer. Enter your Ubuntu One credentials if asked. + + Then either use both computers normally for some time (one or two days?) so the package sync occurs naturally, or force the sync to happen in both of them (faster) by running: + $ oneconf-query --stop + $ oneconf-service --debug + (The --debug flag is not necessary, but useful for debugging) + Do this for both computers, one at a time. + + Then open the Software Center and click on the Installed Software tab, or "File > Sync Between Computers". + If all computer are listed, and if clicking on one of them (except the current one) bring up a package comparison, the bug is fixed. + If not, you may try to force a sync on both computers one last time and check again, just to be sure. + + + [Regression Potential] + + Oneconf wasn't working as intended, so there's probably not regression + potential. But it suppose it could impact the stability of Oneconf or + the Software Center. + + + [Original Report] + In Raring I see only the machince I'm on. In the precise box beside it I see a couple of boxes but not this one. Please see the screenshots attached. I have a feeling that some how the sync has broken but I'm not sure what technology it is use on the backend. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: oneconf 0.3.3 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Fri Apr 5 18:18:24 2013 InstallationDate: Installed on 2013-04-02 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402) MarkForUpload: True PackageArchitecture: all SourcePackage: oneconf 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 oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1165104 Title: oneconf is only showing the pc you are on in raring and isn't sharing to other machines Status in One Hundred Papercuts: Fix Committed Status in oneconf package in Ubuntu: Fix Committed Bug description: [Impact] The package synchronization in the Ubuntu Software Center doesn't work, and only the current machine is displayed. [Test Case] At least two computers (or virtual machines) are needed. First, enable software sync in both computers, by opening the Ubuntu Software Center, then clicking "File > Sync Between Computers" in the menu in each computer. Enter your Ubuntu One credentials if asked. Then either use both computers normally for some time (one or two days?) so the package sync occurs naturally, or force the sync to happen in both of them (faster) by running: $ oneconf-query --stop $ oneconf-service --debug (The --debug flag is not necessary, but useful for debugging) Do this for both computers, one at a time. Then open the Software Center and click on the Installed Software tab, or "File > Sync Between Computers". If all computer are listed, and if clicking on one of them (except the current one) bring up a package comparison, the bug is fixed. If not, you may try to force a sync on both computers one last time and check again, just to be sure. [Regression Potential] Oneconf wasn't working as intended, so there's probably not regression potential. But it suppose it could impact the stability of Oneconf or the Software Center. [Original Report] In Raring I see only the machince I'm on. In the precise box beside it I see a couple of boxes but not this one. Please see the screenshots attached. I have a feeling that some how the sync has broken but I'm not sure what technology it is use on the backend. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: oneconf 0.3.3 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Fri Apr 5 18:18:24 2013 InstallationDate: Installed on 2013-04-02 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402) MarkForUpload: True PackageArchitecture: all SourcePackage: oneconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1165104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop
[Desktop-packages] [Bug 1457660] [NEW] Sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main)
Public bug reported: Please sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Change appdata-tools b-dep to appstream-util Droppped upstream Changelog entries since current wily version 1:3.14.1-1ubuntu1: gucharmap (1:3.16.2-1) unstable; urgency=medium * New upstream release. * Drop appdata-tools build-dependency, no longer needed. -- Andreas Henriksson Tue, 19 May 2015 15:02:43 +0200 ** Affects: gucharmap (Ubuntu) Importance: Wishlist Status: New ** Changed in: gucharmap (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1457660 Title: Sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main) Status in gucharmap package in Ubuntu: New Bug description: Please sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Change appdata-tools b-dep to appstream-util Droppped upstream Changelog entries since current wily version 1:3.14.1-1ubuntu1: gucharmap (1:3.16.2-1) unstable; urgency=medium * New upstream release. * Drop appdata-tools build-dependency, no longer needed. -- Andreas Henriksson Tue, 19 May 2015 15:02:43 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1457660/+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 1376602] Re: Sync gucharmap 1:3.14.0-1 (main) from Debian unstable (main)
** Changed in: gucharmap (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1376602 Title: Sync gucharmap 1:3.14.0-1 (main) from Debian unstable (main) Status in gucharmap package in Ubuntu: Fix Released Bug description: Please sync gucharmap 1:3.14.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Upload from unreleased Debian SVN to fix FTBFS, should be a sync in future. * Use dh_autoreconf to update libtool.m4 for new ports, and build with --as-needed to obsolete debian/patches/99_ltmain_as-needed.patch. Thanks to Colin Watson in Ubuntu. Fixed in debian + new upstream translation release Changelog entries since current utopic version 1:3.13.90-1ubuntu1: gucharmap (1:3.14.0-1) unstable; urgency=medium [ Iain Lane ] * Use dh_autoreconf to update libtool.m4 for new ports, and build with --as-needed to obsolete debian/patches/99_ltmain_as-needed.patch. Thanks to Colin Watson in Ubuntu. [ Andreas Henriksson ] * New upstream release. -- Andreas Henriksson Tue, 23 Sep 2014 01:08:39 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1376602/+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 1457650] Re: package fglrx-updates-core (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g32631
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1457650 Title: package fglrx-updates-core (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 Status in fglrx-installer-updates package in Ubuntu: New Bug description: Ubuntu 14.04.2 fglrx-updates-core failed to install when fglrx was being updated from 13 to 15 to fix bug 1424491 because it was trying to overwrite /bin/clinfo, also present in the clinfo package. had to use sudo dpkg -r clinfo to get fglrx-updates-core installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-updates-core (not installed) ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 21 10:45:04 2015 DistUpgraded: 2014-05-12 02:09:10,784 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.16.0-36-generic, x86_64: installed virtualbox, 4.3.10, 3.16.0-37-generic, x86_64: installed DuplicateSignature: package:fglrx-updates-core:(not installed):trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 ErrorMessage: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] [1002:9640] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84c8] InstallationDate: Installed on 2013-02-13 (827 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-37-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer-updates Title: package fglrx-updates-core (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 UpgradeStatus: Upgraded to trusty on 2014-05-12 (374 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0211 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F1A75-M-PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0211:bd07/02/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-M-PROR2.0:rvrRevX.0x: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.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 12 16:59:52 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Unifying Device. Wireless PID:101f MOUSE, id 8 inputLogitech Unifying Device. Wireless PID:4003 KEYBOARD, id 9 inputEee PC WMI hotkeys KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] 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] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/d
[Desktop-packages] [Bug 1457650] [NEW] package fglrx-updates-core (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g326
Public bug reported: Ubuntu 14.04.2 fglrx-updates-core failed to install when fglrx was being updated from 13 to 15 to fix bug 1424491 because it was trying to overwrite /bin/clinfo, also present in the clinfo package. had to use sudo dpkg -r clinfo to get fglrx-updates-core installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-updates-core (not installed) ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 21 10:45:04 2015 DistUpgraded: 2014-05-12 02:09:10,784 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.16.0-36-generic, x86_64: installed virtualbox, 4.3.10, 3.16.0-37-generic, x86_64: installed DuplicateSignature: package:fglrx-updates-core:(not installed):trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 ErrorMessage: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] [1002:9640] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84c8] InstallationDate: Installed on 2013-02-13 (827 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-37-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer-updates Title: package fglrx-updates-core (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/clinfo', which is also in package clinfo 0.0.git20141116-g3263181-1~ubuntu14.04.1 UpgradeStatus: Upgraded to trusty on 2014-05-12 (374 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0211 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F1A75-M-PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0211:bd07/02/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-M-PROR2.0:rvrRevX.0x: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.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 12 16:59:52 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Unifying Device. Wireless PID:101f MOUSE, id 8 inputLogitech Unifying Device. Wireless PID:4003 KEYBOARD, id 9 inputEee PC WMI hotkeys KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] 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] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1457650 Title: package fglrx-updates-core (not installed) failed to install/upgrade: trying to overwrite '/
[Desktop-packages] [Bug 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
>From IRC: 16:20 < nessita> jsalisbury, just wanted to sync about the bisect we're doing for LP: #1201528, since I'm now in 3.8.13.1 and audio died with the underrun error. So I re-read all the comments and noticed that in commnet #39 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/comments/39) I reproduced the issue with kernel 3.8.0-27-generic 16:21 < nessita> I'm now installing latest 3.7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ which is 3.7.10 and see if audio breaks, will report in the bug So, in summary: Kernel 3.8.13.1 -> AUDIO BREAKS Kernel 3.7.10 -> audio does not break Will try other versions of 3.8. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board As
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Autopkgtest seems still mark release for trusty as cause of regression :( http://people.canonical.com/~ubuntu-archive/pending-sru.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+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 1457605] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: i've installed the lts-vivid kernel and i found this error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 DKMSKernelVersion: 3.19.0-18-generic Date: Thu May 21 13:49:05 2015 DuplicateSignature: dkms:nvidia-331-updates-uvm:331.113-0ubuntu0.0.4:/var/lib/dkms/nvidia-331-updates/331.113/build/nv.c:2027:29: error: ‘struct file’ has no member named ‘f_dentry’ InstallationDate: Installed on 2015-05-05 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: 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 third-party-packages trusty -- 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/1457605 Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: i've installed the lts-vivid kernel and i found this error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 DKMSKernelVersion: 3.19.0-18-generic Date: Thu May 21 13:49:05 2015 DuplicateSignature: dkms:nvidia-331-updates-uvm:331.113-0ubuntu0.0.4:/var/lib/dkms/nvidia-331-updates/331.113/build/nv.c:2027:29: error: ‘struct file’ has no member named ‘f_dentry’ InstallationDate: Installed on 2015-05-05 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: 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/1457605/+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 1457605] Re: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build
** Tags removed: need-duplicate-check -- 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/1457605 Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: i've installed the lts-vivid kernel and i found this error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 DKMSKernelVersion: 3.19.0-18-generic Date: Thu May 21 13:49:05 2015 DuplicateSignature: dkms:nvidia-331-updates-uvm:331.113-0ubuntu0.0.4:/var/lib/dkms/nvidia-331-updates/331.113/build/nv.c:2027:29: error: ‘struct file’ has no member named ‘f_dentry’ InstallationDate: Installed on 2015-05-05 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: 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/1457605/+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 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
Can confirm gvfs-ls trash:/// works fine producing the output of all the files in the trash:// location. I have another account on the system with plenty of files in that trash:// works perfectly fine for. Guest mode trash:// also works perfectly fine. The program still crashes with SIGSEGV (__GI__IO_default_xsputn (f=0x7f7ff600, data=, n=38) at genops.c:463) with python-nautilus uninstalled and pruged out (I did not restart the system, but I ensured that nautilus was completely killed before I re- attempted the test) I'm guessing there's probably something in my trash:// that's triggering this right? Any particular file types I should look for? Interestingly opening `nautilus ~/.local/share/Trash/files` causes a sefault too! -- 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/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// Status in nautilus package in Ubuntu: New Bug description: Package version 1:3.14.2-0ubuntu9 from http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages Ubuntu 15.04 amd64 on an i5-4670K CPU Hi, I'm currently getting a consistent SIGSEGV from Nautilus when attempting to open the rubbish bin. This happens whether I click the bookmark on the left or instantaneously if I run `nautilus trash://`. The crash occurs before the icons have fully loaded, but a second after the rubbish bin is selected. I installed the debug symbols for nautilus and ran with gdb and got the following output: (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". (nautilus:21736): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:21736): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:21736): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [Thread 0x77f8ba00 (LWP 21736) exited] [Inferior 1 (process 21736) exited normally] (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". nautilus-wipe-Message: Initializing [New Thread 0x7fffe9017700 (LWP 22649)] [Thread 0x7fffe9017700 (LWP 22649) exited] [New Thread 0x7fffc1347700 (LWP 22680)] [New Thread 0x7fffe35f1700 (LWP 22651)] [New Thread 0x7fffe3fff700 (LWP 22650)] [New Thread 0x7fffe9818700 (LWP 22648)] Program received signal SIGSEGV, Segmentation fault. 0x7372332e in __GI__IO_default_xsputn (f=0x7f7ff5f0, data=0x50e080, n=6) at genops.c:447 447 genops.c: No such file or directory. I can provide more info if needed as I can easily reproduce the bug. I know a little about using gdb as well, but may need a bit of guidance as I'm no hardened C programmer. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+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 1457592] [NEW] cell contents and formulas are missing from calc spreadsheets, suddenly
Public bug reported: Upon opening ods files with formulas on 20 May, Calc does not display most of the cell contents. In some cells the value is simply a text string, which appears in the formula box but does not appear in the cell. In one cell I enter the time, and what I entered shows up in the formula box but does not show up in the cell. This time is used in a formula for another cell. In another cell I enter the date, and Calc correctly formats the date and displays it in the cell. This date is used in a formula for another cell. The formula is not shown in the formula box. If I click on a cell, the RESULT of the formula shows in the formula box, but not in the cell. In one case, the formula box does display the formula (=C3+B3). This occurs in a template ods file with no values (in C3 or B3). Some of the lines on the spreadsheet are suddenly in red, and it takes several tries to get them to disappear. The formats (colors of cells) are all displayed correctly. The font of each cell is still displayed in the font box, but most of the cell contents are not displaying at all. Calc still works normally on other spreadsheets with no formulas. Calc was working normally on 6 May 2014. Using Ubuntu 14.04. libreoffice-calc 1:4.2.8-0ubuntu2 I don't think I have any extensions installed. I use the normal ubuntu update process. I ran the sudo apt-get -y intall libreoffice and the result is the same. AMD64 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 21 10:15:42 2015 InstallationDate: Installed on 2015-03-18 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1457592 Title: cell contents and formulas are missing from calc spreadsheets, suddenly Status in libreoffice package in Ubuntu: New Bug description: Upon opening ods files with formulas on 20 May, Calc does not display most of the cell contents. In some cells the value is simply a text string, which appears in the formula box but does not appear in the cell. In one cell I enter the time, and what I entered shows up in the formula box but does not show up in the cell. This time is used in a formula for another cell. In another cell I enter the date, and Calc correctly formats the date and displays it in the cell. This date is used in a formula for another cell. The formula is not shown in the formula box. If I click on a cell, the RESULT of the formula shows in the formula box, but not in the cell. In one case, the formula box does display the formula (=C3+B3). This occurs in a template ods file with no values (in C3 or B3). Some of the lines on the spreadsheet are suddenly in red, and it takes several tries to get them to disappear. The formats (colors of cells) are all displayed correctly. The font of each cell is still displayed in the font box, but most of the cell contents are not displaying at all. Calc still works normally on other spreadsheets with no formulas. Calc was working normally on 6 May 2014. Using Ubuntu 14.04. libreoffice-calc 1:4.2.8-0ubuntu2 I don't think I have any extensions installed. I use the normal ubuntu update process. I ran the sudo apt-get -y intall libreoffice and the result is the same. AMD64 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 21 10:15:42 2015 InstallationDate: Installed on 2015-03-18 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1457592/+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 1457593] Re: Xorg crashed after 'service gdm restart'
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1457593/+attachment/4401877/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1457593/+attachment/4401880/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1457593/+attachment/4401892/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1457593/+attachment/4401894/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1457593/+attachment/4401895/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1457593/+attachment/4401896/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1457593/+attachment/4401897/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 Xorg crashed with SIGABRT in OsAbort() ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1457593 Title: Xorg crashed after 'service gdm restart' Status in xorg-server package in Ubuntu: New Bug description: I noticed my keyboard was not working properly as typing for example shift + , would give me the character _ instead of the expected quotation mark ? I opened a terminal and typed 'sudo service gdm restart' After that I was in the lobby but my user wasn't available for quick login so I had to go through the 'not listed?' option typing my username and password. After that bug splat informed that this crashed had happened. I am running Ubuntu 14.04.2 LTS ~$ apt-cache policy xorg xorg: Installed: 1:7.7+1ubuntu8.1 Candidate: 1:7.7+1ubuntu8.1 Version table: *** 1:7.7+1ubuntu8.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+1ubuntu8 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 21 19:36:15 2015 DistUpgraded: 2014-08-24 19:29:45,281 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2013-10-25 (572 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540 ProcCmdline: /usr/bin/X :1 -background none -verbose -auth /var/run/gdm/auth-for-gdm-sqGn5O/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=en_US.UTF-8 TERM=linux LANGUAGE=en_US:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=d63b3b56-49e7-42d0-88b7-fedf4767a791 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () FatalError () ?? () xf86CloseConsole () ddxGiveUp () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to trusty on 2014-08-24 (270 days ago) UserGroups: dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08JV.M029.20100621.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730/R540 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable 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:bvnPhoenixTechnologiesLtd.:bvr08JV.M029.20100621.hkk:bd06/21/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730/R540:pv
[Desktop-packages] [Bug 1457593] [NEW] Xorg crashed after 'service gdm restart'
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 Public bug reported: I noticed my keyboard was not working properly as typing for example shift + , would give me the character _ instead of the expected quotation mark ? I opened a terminal and typed 'sudo service gdm restart' After that I was in the lobby but my user wasn't available for quick login so I had to go through the 'not listed?' option typing my username and password. After that bug splat informed that this crashed had happened. I am running Ubuntu 14.04.2 LTS ~$ apt-cache policy xorg xorg: Installed: 1:7.7+1ubuntu8.1 Candidate: 1:7.7+1ubuntu8.1 Version table: *** 1:7.7+1ubuntu8.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+1ubuntu8 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 21 19:36:15 2015 DistUpgraded: 2014-08-24 19:29:45,281 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2013-10-25 (572 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730/R540 ProcCmdline: /usr/bin/X :1 -background none -verbose -auth /var/run/gdm/auth-for-gdm-sqGn5O/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=en_US.UTF-8 TERM=linux LANGUAGE=en_US:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=d63b3b56-49e7-42d0-88b7-fedf4767a791 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () FatalError () ?? () xf86CloseConsole () ddxGiveUp () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to trusty on 2014-08-24 (270 days ago) UserGroups: dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08JV.M029.20100621.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730/R540 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable 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:bvnPhoenixTechnologiesLtd.:bvr08JV.M029.20100621.hkk:bd06/21/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730/R540:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730/R540:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730/R540 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 21 21:23:32 2015 xserver.configfile: default xserver.errors: Server terminated successfully (0). Closing log file. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5522 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash trusty ubuntu ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1457593 Title: Xorg crashed after 'service gdm restart' Status in xorg-server package in Ubuntu: New Bug description: I noticed my keyboard was not working properly as typing for example shift + , would give me the character _ instead of the expected quotation mark ? I opened a terminal and typed 'sudo service
[Desktop-packages] [Bug 1373070] Re: full fix for disconnected path (paths)
To add one more data point, my Trusty server using the Utopic HWE kernel also exhibits the problem: May 21 12:27:28 xeon kernel: [95104.918686] audit: type=1400 audit(1432225648.230:57): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=3444 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 $ apt-cache policy apparmor linux-image-3.16.0-38-generic rsyslog apparmor: Installed: 2.8.95~2430-0ubuntu5.2 Candidate: 2.8.95~2430-0ubuntu5.2 Version table: *** 2.8.95~2430-0ubuntu5.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.8.95~2430-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages linux-image-3.16.0-38-generic: Installed: 3.16.0-38.52~14.04.1 Candidate: 3.16.0-38.52~14.04.1 Version table: *** 3.16.0-38.52~14.04.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status rsyslog: Installed: 7.4.4-1ubuntu2.6 Candidate: 7.4.4-1ubuntu2.6 Version table: *** 7.4.4-1ubuntu2.6 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.3 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.4.4-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1373070 Title: full fix for disconnected path (paths) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+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 1183738] Re: removed
** Summary changed: - libxml2 can not coexist with libxml2-i386 on 64-bit systems + removed ** Description changed: - In Ubuntu 13.04 (64-bit), libxml2-i386 can not be installed in the same - time with libxml2(-amd64), though some packages (for example, skype, - wine) depend on libxml2-i386. As much software depends on libxml2-amd64 - (such as KDE), it is impossible to install wine, skype, etc. in 64-bit - system using KDE. + removed ** Package changed: libxml2 (Ubuntu) => ubuntu ** Information type changed from Public to Private -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1183738 Title: removed Status in Ubuntu: Invalid Bug description: removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1183738/+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 1457490] Re: Chrome using only one core after S3/resume
edit: sorry, i looked at System monitor, so chrome is using CPU0, just the widget showed it as 4th core. im also using TurionPowerControl, but not as service, just a script sets the voltages. -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: Incomplete Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1457490/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Assignee: (unassigned) => Roberto (swaggerone) -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for "LUG" in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 1453052] Re: X fails to automatically detect ATI radeon RV600 card
Ok. Tried with latest kernel. Nope. The whole system boots fine, but X is still failing to detect properly the graphic card. -- 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/1453052 Title: X fails to automatically detect ATI radeon RV600 card Status in xorg package in Ubuntu: Incomplete Bug description: Good day. I'm testing pure EFI boot capability on my iMac 7.1 (graphic card ATI radeon HD2600 pro). So far, with Ubuntu 14.10, i've been able to boot directly into a perfectly working system using the EFI kernel stub. No GRUB, no ELILO, no rEFIND, no boot manager whatsoever! And the result was amazing! Boot up time reduced to a fraction of the time needed by GRUB, for example, Compiz compositing much more quick, smooth and and efficient. I could notice even some graphical detail (e.g. Text shadows in the GDM log-in screen) that were not present if booting via GRUB. The way to accomplished this is simple: 1) Create a small (40MB or less) HFS+ partition. E.g. #> sudo mkfs.hfsplus /dev/sdaX -v "Ubuntu (EFI-Stub)" 2) Copy to the new partition the files vmlinuz-3.XX.YY-ZZ-generic.efi.signed and initrd.img-3.XX.YY-ZZ-generig. Also rename them to "vmlinuz.efi" and "initrd.img" for sake of simplicity in further command line work. Furthermore, Apple's EFI won't boot anything that doesn't end with the ".efi" extension. 3) Create a boot entry in the NVRAM using efibootmgr like this: #> sudo efibootmgr -d /dev/sdX -p Y -c -L "Ubuntu 14.04 LTS" -l /vmlinuz.efi -u "root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash initrd=\initrd.img" 4) reboot (and enjoy!) As i've said, in Ubuntu 14 all this is working fine, but after the upgrade to Ubuntu 15, "X" doesn't start anymore. The system starts up correctly but X fails (with error: (EE) No devices detected. (EE) Fatal server error: (EE) no screens found) dropping me to a tty console login. I'm not shure if it is a X problem or a kernel KMS bug, but i'm more inclined to think of a problem with X because i've tried to boot Ubuntu 15.0 with the old kernel (3.13/16) and the problem is still there. I've also tried to add "vt.handoff=7" to the command line args for the kernel, like grub does, but the result is even worse. The system freezes completely at the moment of starting X. Please note also that booting via grub is working. X starts, much more slowly but starts. (Actually i'm reporting this bug from the very same system booted using GRUB. I have a second HFS+ partition where i installed grub and i can access it by holding down the ALT key at power-up) Thanks for your work. I really hope that booting directly via EFI stubs will grow mature because the performance increase is really big. Thanks again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 8 10:20:35 2015 DistUpgraded: 2015-05-06 18:46:56,830 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-16-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-16-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2013-10-27 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Apple Inc. iMac7,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-05-06 (1 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238CC8 dmi.
[Desktop-packages] [Bug 1435905] Re: gnome-terminal randomly outputs control characters
Vivid ships 3 parallel versions of vte: libvte9 0.28.x - used by Gtk2 apps such as terminator, xfce4-terminal libvte-2.90-9 0.36.x - a tiny bit older than the newest, used by e.g. roxterm-gtk3 libvte-2.91-0 0.38.x - the newest, used by e.g. gnome-terminal As stated above, the bug was fixed in 0.35.x, so apps using either of the two new versions of vte should be fine. -- 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/1435905 Title: gnome-terminal randomly outputs control characters Status in gnome-terminal package in Ubuntu: Confirmed Status in terminator package in Ubuntu: Confirmed Bug description: Observed behavior: When using tmux, the terminal occasionally displays the "boxed" version of the 0x001b character followed by two ']' characters either in the cursor's current location or at the end of a refreshed line, or sometimes at an apparently random position on the screen. The times at which this character appears seem to be completely random. To reproduce: Get a clean install of tmux and gnome-terminal from the repositories. It is difficult to quantify this, but it appears that the bug will present itself most readily when working in vim or another refresh-heavy cli program. Why it's not a tmux bug: The bug appears to affect gnome-terminal and terminator, but not xterm or e.g. sessions connected over putty. In fact, if I open all of these screens side-by-size (using a virtual machine), and simultaneously attach to the same tmux session, only gnome-terminal and terminator show the strange characters, while the other two terminals render the screen as expected. Please see this superuser discussion for a link to a video of what the bug looks like: http://superuser.com/questions/864364/tmux-printing-u0x001b-and-112-randomly Let me know if there is anything else I can do to help reproduce/solve this, as using xterm is a really bad workaround to have to put up with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 24 10:30:12 2015 InstallationDate: Installed on 2015-01-11 (71 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435905/+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 1392887] Re: serial wacom devices gone after upgrade to utopic/14.10
** Description changed: + [Impact] + udev rules and systemd service file are installed in the wrong path due to assuming that dh_install can rename files, instead it installed the files under the "renamed" directory + + [Test case] + try to use a serial wacom device, it fails + + [Regression potential] + none, restore original behaviour + + -- + Recently I upgraded ubuntu from 14.04 to 14.10 on my HP EliteBook 2760p. After that, all serial wacom devices (for the touchscreen) are gone: serial wacom stylus serial wacom eraser serial wacom touch xinput -list and xsetwacom --list don't show these devices and the Wacom Tablet section of the system setings reports 'no tablet detected' rather than showing the usual settings. Booting with the old linux 3.13 kernel makes no difference to the new version 3.16. To find out what happened I played around on a spare partition with the following results: 1) fresh installation of 14.10 - result is the same like reported above: no touch devices 2) fresh installation of 14.04 - touch works out of the box 3) upgraded the fresh installation of trusty to utopic: touch devices gone again 4) manually changed repos to utopic after fresh installation of 14.04 and updated ONLY the xserver-xorg-input-wacom package: apt pulled some dependencies and installed without errors, touch devices gone (so it reproduces the error exactly as the full upgrade) WORKAROUND: Replace the udev rule /lib/udev/rules.d/69-wacom.rules/wacom.rules by the old file from Ubuntu 14.04 by putting it in /lib/udev/rules.d/ : https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+attachment/4264135/+files/69-xserver-xorg-input-wacom.rules ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-input-wacom 1:0.25.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 14 22:51:05 2014 DistUpgraded: 2014-11-01 04:28:11,674 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu InstallationDate: Installed on 2012-10-16 (759 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP EliteBook 2760p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 ro quiet splash vt.handoff=7 SourcePackage: xf86-input-wacom UpgradeStatus: Upgraded to utopic on 2014-11-01 (13 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.50 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2760p dmi.product.version: A0005F02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 14 21:19:38 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22337 vendor SEC xserver.version: 2:1.16.0-1ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1392887 Title: serial wacom devices gone after upgrade to utopic/14.10 Status in xf86-input-wacom package in Ubuntu: Fix Released Status in xf86-input-wacom-lts-utopic package in Ubuntu: New Status in xf86-input-wacom source package in Trusty: New Status in xf86-input-wacom-lts-utopic source package in Trusty: New Status in xf86-input-wacom source package in Utopic: New Status in xf86-input-wacom source package in Vivid: New Status in xf86-input-wacom source package in Wily: Fix Released Bug description: [Impact] udev rules and systemd service file are installed in the wrong path due to assuming that dh_install can rename files,
[Desktop-packages] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
I'm having big problems getting the new 2:15.200-0ubuntu0.3 installed. I've tried over five times and can't get it to work - can't even get into the OS in 14.04.2 when it is installed and reboot. What special 'sauce' is needed? I'm not very proficient with Linux and have tried in terminal and by synaptic [when all fglrx drivers are purged I can get in on Xorg - but even that is no longer seeing my three monitors and has each one as a separate monitor, rather than one big desktop, as before. Downloaded the fglrx-installer-updates_15.200.orig.tar.gz for Trusty, but don't see how one is supposed to install it...the only method I didn't try. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 Status in AMD fglrx video driver: Invalid Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Status in fglrx-installer source package in Precise: In Progress Status in fglrx-installer-updates source package in Precise: In Progress Status in fglrx-installer source package in Trusty: Fix Released Status in fglrx-installer-updates source package in Trusty: Fix Released Bug description: SRU Request: [Impact] fglrx cannot be installed correctly together with the new lts stacks. [Test case] Installing the xserver from lts-utopic will prevent the current fglrx from being installed. The new fglrx will install correctly [Regression potential] Low. This fglrx release is already in use in 15.04 without any major issues. -- Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2 Expected behavior: fglrx would intall Observed behavior: fglrx is not installed as follows Attempt to install fglrx fails as follows: zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx-updates : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. Attempt to insatll xorg-video-abi-15 yields: zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Attempting to install xserver-xorg-core instead yields: zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been mo
[Desktop-packages] [Bug 1450991] Re: hided launcher does not show urgent icons in 15.04
** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: unity Status: New => In Progress ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity Importance: Undecided => Medium -- 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/1450991 Title: hided launcher does not show urgent icons in 15.04 Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: When a program requests to wiggle its icons on the launcher, if the launcher is visible, it works fine and the icon shakes properly. But when it is not visible (auto-hide option is enabled), desired behavior would be that its icon should slide inside while it is shaking and then go off the screen after a short while. This behavior already hes been applied in 14.10 and older versions, but in 15.04 launcher does not show urgent animation when it is hide that it could be bug. Why this bug annoys me? I usually would use IM apps and in such apps, Pidgin for instance, when a user becomes on-line or off-line, its icon on the launcher starts to shaking and in this way informs me. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1450991/+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 1456445] Re: fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build [error: implicit declaration of function ‘read_cr4’]
** Summary changed: - fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build + fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build [error: implicit declaration of function ‘read_cr4’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1456445 Title: fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build [error: implicit declaration of function ‘read_cr4’] Status in fglrx-installer package in Ubuntu: New Bug description: DKMS make.log for fglrx-core-15.200 for kernel 4.0.4-040004-generic (x86_64) Tue May 19 00:32:40 EDT 2015 /usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200/build: No such file or directory AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/4.0.4-040004-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules make[1]: Entering directory '/usr/src/linux-headers-4.0.4-040004-generic' CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: In function ‘kcl_mem_pat_setup’: /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration] cr4 = read_cr4(); ^ /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4500:9: error: implicit declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration] write_cr4(cr4 & ~X86_CR4_PGE); ^ /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: At top level: /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ cc1: some warnings being treated as errors scripts/Makefile.build:258: recipe for target '/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o' failed make[2]: *** [/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o] Error 1 Makefile:1390: recipe for target '_module_/var/lib/dkms/fglrx-core/15.200/build/2.6.x' failed make[1]: *** [_module_/var/lib/dkms/fglrx-core/15.200/build/2.6.x] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.0.4-040004-generic' Makefile:88: recipe for target 'kmod_build' failed make: *** [kmod_build] Error 2 build failed with return value 2 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 4.0.4-040004-generic Date: Tue May 19 00:32:43 2015 DuplicateSignature: dkms:fglrx-core:2:15.200-0ubuntu4:/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2015-05-01 (17 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageVersion: 2:15.200-0ubuntu4 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: fglrx-installer SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown Title: fglrx-core 2:15.200-0ubuntu4: fglrx-core 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/fglrx-installer/+bug/1456445/+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 1457490] Re: Chrome using only one core after S3/resume
I think this was in the same boot cycle. the bug was tracked at the problematic resume and after a restart i finished it. It happends after every S3/resume and CPU3(4th core) is getting the whole load everytime. Youtube videos are very laggy, im using many tabs all the time. Ive got a small tray widget, what shows the load. The problem still exist after restarting chrome, i havent better choice, just a reboot. -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: Incomplete Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1457490/+subscriptio
[Desktop-packages] [Bug 1457557] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
Public bug reported: Dunno details. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 DKMSKernelVersion: 3.13.0-53-generic Date: Wed May 20 20:43:53 2015 InstallationDate: Installed on 2014-07-10 (314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1457557 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Dunno details. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 DKMSKernelVersion: 3.13.0-53-generic Date: Wed May 20 20:43:53 2015 InstallationDate: Installed on 2014-07-10 (314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 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/+bug/1457557/+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 1457516] Re: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build
*** This bug is a duplicate of bug 1373136 *** https://bugs.launchpad.net/bugs/1373136 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1373136, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1373136 nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed to build [nvidia-modules-common.mk: No such file or directory] -- 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/1457516 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.113-0ubuntu0.0.4 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.1-0ubuntu3.10 Architecture: amd64 DKMSBuildLog: DKMS make.log for nvidia-331-uvm-331.113 for kernel 3.13.0-53-generic (x86_64) Wed May 20 20:41:16 GET 2015 Makefile:216: /var/lib/dkms/nvidia-331/331.113/build/nvidia-modules-common.mk: No such file or directory make: *** No rule to make target `/var/lib/dkms/nvidia-331/331.113/build/nvidia-modules-common.mk'. Stop. DKMSKernelVersion: 3.13.0-53-generic Date: Wed May 20 20:41:23 2015 InstallationDate: Installed on 2014-10-03 (229 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-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/+bug/1457516/+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 1453052] Re: X fails to automatically detect ATI radeon RV600 card
Hi, Christopher. What do you really mean by "testing with the latest kernel"? I try to guess, so please correct me if I'm wrong. When the 3.19.0-16 kernel was installed, the process ended up with two vmlinuz files: vmlinuz-3-19.0-16-generic and vmlinuz-3-19.0-16-generic.efi.signed. Now, after the latest update I can find in the /boot folder only the vmlinuz-3-19.0-18-generic file. This can mean only two things: first) efi stub support has been temporarily suspended in this kernel's version (but I don't think so) second) the latest kernel is definitely an efi image that can be booted directly. In this case, ok, I'll try copying this kernel's version to my hfs+ boot partition. That said, I'm not sure if new macs do have the possibility to tweak the BIOS but my old model for sure doesn't have. In no way I can switch between secure/unsecure boot mode. My guess is that the EFI firmware is booting in UNSAFE mode by default (and actually this is what grub says very early at boot, BEFORE displaying the classical purple screen). Anyway, I'll try with the latest kernel. -- 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/1453052 Title: X fails to automatically detect ATI radeon RV600 card Status in xorg package in Ubuntu: Incomplete Bug description: Good day. I'm testing pure EFI boot capability on my iMac 7.1 (graphic card ATI radeon HD2600 pro). So far, with Ubuntu 14.10, i've been able to boot directly into a perfectly working system using the EFI kernel stub. No GRUB, no ELILO, no rEFIND, no boot manager whatsoever! And the result was amazing! Boot up time reduced to a fraction of the time needed by GRUB, for example, Compiz compositing much more quick, smooth and and efficient. I could notice even some graphical detail (e.g. Text shadows in the GDM log-in screen) that were not present if booting via GRUB. The way to accomplished this is simple: 1) Create a small (40MB or less) HFS+ partition. E.g. #> sudo mkfs.hfsplus /dev/sdaX -v "Ubuntu (EFI-Stub)" 2) Copy to the new partition the files vmlinuz-3.XX.YY-ZZ-generic.efi.signed and initrd.img-3.XX.YY-ZZ-generig. Also rename them to "vmlinuz.efi" and "initrd.img" for sake of simplicity in further command line work. Furthermore, Apple's EFI won't boot anything that doesn't end with the ".efi" extension. 3) Create a boot entry in the NVRAM using efibootmgr like this: #> sudo efibootmgr -d /dev/sdX -p Y -c -L "Ubuntu 14.04 LTS" -l /vmlinuz.efi -u "root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash initrd=\initrd.img" 4) reboot (and enjoy!) As i've said, in Ubuntu 14 all this is working fine, but after the upgrade to Ubuntu 15, "X" doesn't start anymore. The system starts up correctly but X fails (with error: (EE) No devices detected. (EE) Fatal server error: (EE) no screens found) dropping me to a tty console login. I'm not shure if it is a X problem or a kernel KMS bug, but i'm more inclined to think of a problem with X because i've tried to boot Ubuntu 15.0 with the old kernel (3.13/16) and the problem is still there. I've also tried to add "vt.handoff=7" to the command line args for the kernel, like grub does, but the result is even worse. The system freezes completely at the moment of starting X. Please note also that booting via grub is working. X starts, much more slowly but starts. (Actually i'm reporting this bug from the very same system booted using GRUB. I have a second HFS+ partition where i installed grub and i can access it by holding down the ALT key at power-up) Thanks for your work. I really hope that booting directly via EFI stubs will grow mature because the performance increase is really big. Thanks again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 8 10:20:35 2015 DistUpgraded: 2015-05-06 18:46:56,830 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-16-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-16-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00
Re: [Desktop-packages] [Bug 1196251] Re: pacman crashed with SIGSEGV in is_bonus_dot()
What how to? On 05/12/2015 01:47 PM, eric tennant wrote: > Hi, can you please advise me on the how to. > Would appreciate it. > Regards > Eric Tennant > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1196251 Title: pacman crashed with SIGSEGV in is_bonus_dot() Status in xscreensaver package in Ubuntu: Fix Released Bug description: I was just selecting which xscreensavers to allow and had not gotten to pacman yet when this occurred. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xscreensaver-data-extra 5.15-2ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Sun Jun 30 09:56:05 2013 ExecutablePath: /usr/lib/xscreensaver/pacman InstallationDate: Installed on 2013-06-29 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130626) MarkForUpload: True ProcCmdline: pacman -root -window-id 0x1803DB5 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4084bf: cmp0xdb8(%rdi),%esi PC (0x004084bf) ok source "0xdb8(%rdi)" (0x01ed2004) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xscreensaver StacktraceTop: ?? () ?? () ?? () ?? () __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 Title: pacman crashed with SIGSEGV in __libc_start_main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1196251/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
Still not fixed... very annoying -- 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for "LUG" in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+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 1457298] Re: invalid auth for online-account
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 flickr used the standard authentication implementation. On 2015年05月21日 16:18, Alberto Mardegan wrote: > The yupoo API looks very similar to the old Flickr API: > https://www.flickr.com/services/api/auth.spec.html > > Can you please have a look and confirm if they use the same > authentication method? > -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVXfqAAAoJECfSBuGWom3jaGAIAIrdz6LCVLVaWBoqE/NJgbna 3AvQLfg5GnlStRHgQDNidKLBMx8D9sKrKwqnCTT2BpjVEhQUL+4yV6RhzTW3mpTn /jWkRse78F2oG91sfwgCUWe1+Tqvh52j82DGUrcmNvmZvbzZLDl9eQfbPjczKvu2 45N8nWPYg+1P2pVTN2cJteKP5thEUYXEeDq8y4PehOfa7L3ZreUk92gHB+JqOq6v eZKZHKyao4vPCAdWf9K4G3xCv56sijA7H/AxewjuovOM/ArCrbMX5ZscD2dA0+O1 HK8xKxpeN2olgW0AFb0XK44Bk8dsuIe+EU2S2+li67siUgHxbbPqa6WHLX3bm+M= =6mTY -END PGP SIGNATURE- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-plugin-oauth2 in Ubuntu. https://bugs.launchpad.net/bugs/1457298 Title: invalid auth for online-account Status in signon-plugin-oauth2 package in Ubuntu: New Bug description: In order to launch authentication like most other accounts, yupoo need to register a new .provider file to Online accounts. But this XML-format file requires an standard-parameter request for authenticating and accessing token, including client_id, token_path and others, which doesn't match with the request format of yupoo. Yupoo need to launch an auth with a link like http://www.yupoo.com/services/auth/?api_key=[api_key]&frob=[frob]&perms=[perms]&api_sig=[api_sig]. It is an non standard-format request and need additional parameter requests before accessing token. So we can hardly integrating the entire auth of yupoo into Online-accounts. Shall we provide an more agile policy for configure when creating the .provide file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-plugin-oauth2/+bug/1457298/+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 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
Can you confirm the 3.8.13.1 kernel does not have this bug. That way we know we are bisecting between the correct versions. 3.8.13.1: http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.8.13.1-raring/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201528/+subscriptions -- Mailing list: https://launchpad.ne
[Desktop-packages] [Bug 1374841] Re: gstreamer crashes when opening WMA files
Is there any activity on solving this bug? As it stands, Ubuntu has a regression that makes it incapable of playing one of the three most common audio codecs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1374841 Title: gstreamer crashes when opening WMA files Status in rhythmbox package in Ubuntu: Confirmed Bug description: Totem, Rhythmbox and VLC all crash immediately upon trying to load any WMA audio file. On the command line, Totem throws the following error: (totem:7461): GStreamer-CRITICAL **: gst_structure_new_empty: assertion 'gst_structure_validate_name (name)' failed Segmentation fault (core dumped) Ubuntu release: 14.04 gstreamer version: apt-cache policy ubuntu-restricted-extras ubuntu-restricted-extras: Installed: 60 Candidate: 60 Version table: *** 60 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: The WMA audio files should play. What happened instead: Every media player that uses gstreamer crashes immediately upon trying to open a WMA audio file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1374841/+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 1457518] [NEW] Knime freezes after viewing a plot (since upgrade to 15.04)
Public bug reported: Knime (an eclipse based program) https://www.knime.org/ was working perfectly in 14.04. Since my upgrade to 15.05 each time a try to visualize any kind of plot or table (that means a new window), the new window is created and the plot appears. But, from that point on, Knime entirely freezes ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 21 16:40:55 2015 DistUpgraded: 2015-04-28 15:12:19,082 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1522] InstallationDate: Installed on 2014-06-20 (335 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK Computer Inc. N53Jq ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=b4957094-21ba-430f-b351-d88669003f19 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago) dmi.bios.date: 09/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53Jq.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53Jq 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.:bvrN53Jq.207:bd09/30/2010:svnASUSTeKComputerInc.:pnN53Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN53Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53Jq dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu May 21 11:27:54 2015 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.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- 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/1457518 Title: Knime freezes after viewing a plot (since upgrade to 15.04) Status in unity package in Ubuntu: New Bug description: Knime (an eclipse based program) https://www.knime.org/ was working perfectly in 14.04. Since my upgrade to 15.05 each time a try to visualize any kind of plot or table (that means a new window), the new window is created and the plot appears. But, from that point on, Knime entirely freezes ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 21 16:40:55 2015 DistUpgraded: 2015-04-28 15:12:19,082 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1522] InstallationDate: Installed on 2014-06-20 (335 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Rele
[Desktop-packages] [Bug 1457514] [NEW] package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: подпроцесс новый сценарий pre-installation возвратил код ошибки 1
Public bug reported: This error occurs after installing updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:14.501-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 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: Thu May 21 17:37:59 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ErrorMessage: подпроцесс новый сценарий pre-installation возвратил код ошибки 1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] [1002:9804] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84a4] InstallationDate: Installed on 2014-04-20 (395 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK Computer INC. 1015BX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=ec7175ba-06bf-4e7c-af78-b08579bdf9b6 ro quiet splash acpi_osi= acpi_backlight=vendor vt.handoff=7 SourcePackage: fglrx-installer Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: подпроцесс новый сценарий pre-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1015BX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd05/17/2012:svnASUSTeKComputerINC.:pn1015BX:pvrx.x:rvnASUSTeKComputerINC.:rn1015BX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015BX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 21 17:28:41 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] 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] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1457514 Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: подпроцесс новый сценарий pre-installation возвратил код ошибки 1 Status in fglrx-installer package in Ubuntu: New Bug description: This error occurs after installing updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:14.501-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 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: Thu May 21 17:37:59 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ErrorMessage: подпроцесс новый сценарий pre-installation возвратил код ошибки 1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] [1002:9804] (prog
[Desktop-packages] [Bug 1457516] [NEW] nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.113-0ubuntu0.0.4 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.1-0ubuntu3.10 Architecture: amd64 DKMSBuildLog: DKMS make.log for nvidia-331-uvm-331.113 for kernel 3.13.0-53-generic (x86_64) Wed May 20 20:41:16 GET 2015 Makefile:216: /var/lib/dkms/nvidia-331/331.113/build/nvidia-modules-common.mk: No such file or directory make: *** No rule to make target `/var/lib/dkms/nvidia-331/331.113/build/nvidia-modules-common.mk'. Stop. DKMSKernelVersion: 3.13.0-53-generic Date: Wed May 20 20:41:23 2015 InstallationDate: Installed on 2014-10-03 (229 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1457516 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-uvm 331.113-0ubuntu0.0.4 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.1-0ubuntu3.10 Architecture: amd64 DKMSBuildLog: DKMS make.log for nvidia-331-uvm-331.113 for kernel 3.13.0-53-generic (x86_64) Wed May 20 20:41:16 GET 2015 Makefile:216: /var/lib/dkms/nvidia-331/331.113/build/nvidia-modules-common.mk: No such file or directory make: *** No rule to make target `/var/lib/dkms/nvidia-331/331.113/build/nvidia-modules-common.mk'. Stop. DKMSKernelVersion: 3.13.0-53-generic Date: Wed May 20 20:41:23 2015 InstallationDate: Installed on 2014-10-03 (229 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-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/+bug/1457516/+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 1432194] Re: Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics 5500
I am running Ubuntu 15.04 on a Dell XPS 13 (2015 edition, model 9343, dual boot w/ Windows) and I believe I am affected by this bug as well. I am experiencing crashes when suspending (to RAM). See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457447 cribari@darwin4:/etc/default$ uname -a Linux darwin4 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux cribari@darwin4:/etc/default$ sudo lshw -c video *-display description: VGA compatible controller product: Broadwell-U Integrated Graphics vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:48 memory:f600-f6ff memory:e000-efff ioport:f000(size=64) cribari@darwin4:/etc/default$ modinfo i915 | head filename: /lib/modules/3.19.0-18-generic/kernel/drivers/gpu/drm/i915/i915.ko license:GPL and additional rights description:Intel Graphics author: Intel Corporation author: Tungsten Graphics, Inc. srcversion: D9518833453F92314BDA2ED alias: pci:v8086d162Dsv*sd*bc03sc*i* alias: pci:v8086d162Asv*sd*bc03sc*i* alias: pci:v8086d162Esv*sd*bc03sc*i* alias: pci:v8086d162Bsv*sd*bc03sc*i* cribari@darwin4:/etc/default$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1432194 Title: Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics 5500 Status in X.org xf86-video-intel: Unknown Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Utopic: In Progress Bug description: Trying to achieve: Get a more stable graphics environment up and running Steps to take: basic ubtuntu 14.04 install. Boot up and run for a few minutes and then ... What happens: After running for a few minutes the graphics gets flacky. What should happen: Graphics should not get flaky. I have just installed ubuntu 14.04 on my new thinkpad t450s. Everything basically works, but something is very flaky about my keyboard or display or both. After running for awhile some apps (E.g., thunderbird and sometimes emacs for example) will display garbage. If I refresh by moving the screen around or changing buffers/tabs/etc. they can often recover. I see that there is an [Intel(R) Graphics Installer for Linux* 1.0.7](https://01.org/linuxgraphics/downloads/2014/intelr-graphics- installer-linux-1.0.7). I am leery about just loading this and running it. Any suggestions about how I should proceed? $ sudo lshw -c video *-display description: VGA compatible controller product: Broadwell-U Integrated Graphics vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:63 memory:e000-e0ff memory:d000-dfff ioport:3000(size=64) $ modinfo i915 | head filename: /lib/modules/3.16.0-31-generic/kernel/drivers/gpu/drm/i915/i915.ko license:GPL and additional rights description:Intel Graphics author: Tungsten Graphics, Inc. srcversion: 9929027A8A6F05972AD6986 alias: pci:v8086d22B3sv*sd*bc03sc*i* alias: pci:v8086d22B2sv*sd*bc03sc*i* alias: pci:v8086d22B1sv*sd*bc03sc*i* alias: pci:v8086d22B0sv*sd*bc03sc*i* alias: pci:v8086d162Dsv*sd*bc03sc*i* $ uname -a Linux mypad 3.16.0-31-generic #43~14.04.1-Ubuntu SMP Tue Mar 10 20:13:38 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1432194/+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 1457508] [NEW] [USB-Audio - Logitech USB Headset, recording] No sound at all
Public bug reported: Since upgrade to Vivid, my Logitech Clearchat Pro USB Headset mic is not working any more. No recording activity in pavucontrol from ClearChat Pro USB, although i can see recording activity from my Logitech C270 USB Webcam. By the past i noticed similar issues, always corrected by kernel upgrades. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: manu 31450 F pulseaudio /dev/snd/controlC1: manu 31450 F pulseaudio /dev/snd/controlC0: manu 31450 F pulseaudio CurrentDesktop: GNOME Date: Thu May 21 16:11:55 2015 InstallationDate: Installed on 2014-03-27 (419 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : N o s u c h d e v i c e Symptom_Card: Webcam C270 - USB Device 0x46d:0x825 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: manu 31450 F pulseaudio /dev/snd/controlC1: manu 31450 F pulseaudio /dev/snd/controlC0: manu 31450 F pulseaudio Symptom_Type: No sound at all Title: [USB-Audio - Logitech USB Headset, recording] No sound at all UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago) dmi.bios.date: 09/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XCR8D dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1457508 Title: [USB-Audio - Logitech USB Headset, recording] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Since upgrade to Vivid, my Logitech Clearchat Pro USB Headset mic is not working any more. No recording activity in pavucontrol from ClearChat Pro USB, although i can see recording activity from my Logitech C270 USB Webcam. By the past i noticed similar issues, always corrected by kernel upgrades. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: manu 31450 F pulseaudio /dev/snd/controlC1: manu 31450 F pulseaudio /dev/snd/controlC0: manu 31450 F pulseaudio CurrentDesktop: GNOME Date: Thu May 21 16:11:55 2015 InstallationDate: Installed on 2014-03-27 (419 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : N o s u c h d e v i c e Symptom_Card: Webcam C270 - USB Device 0x46d:0x825 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: manu 31450 F pulseaudio /dev/snd/controlC1: manu 31450 F pulseaudio /dev/snd/controlC0: manu 31450 F pulseaudio Symptom_Type: No sound at all Title: [USB-Audio - Logitech USB Headset, recording] No sound at all UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago) dmi.bios.date: 09/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XCR8D dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1457508/+sub
[Desktop-packages] [Bug 1457490] Re: Chrome using only one core after S3/resume
Also, how are you measuring what core is being used? It is a running chromium that no longer uses more than a speficific, named core core? A running chromium that alternates cores, but never uses uses more than one? Does it happen with a new chromium session? Needless to say, I can't reproduce, and I'm interested in what you are reporting. -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: Incomplete Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1457490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1457490] Re: Chrome using only one core after S3/resume
(I really can spell "specific". Don't laugh too much.) -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: Incomplete Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1457490/+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 1456816] Re: Key binding with F-# keys don't work anymore
** Tags added: trusty ** Changed in: metacity (Ubuntu) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1456816 Title: Key binding with F-# keys don't work anymore Status in metacity package in Ubuntu: New Bug description: 1) Ubuntu version: Ubuntu 14.04.2 LTS 2) Metacity version: 1:2.34.13-0ubuntu4.1 3) What you expected to happen: Key binding on keys "F1" or "F2" etc.. should process the command bound on them. 4) What happened instead: Pressing "F1" executes the application operation (often Help) instead of the system "F1" key binding **Possible regression** Everything worked fine with the version 1:2.34.13-0ubuntu4 This bug appeared with the update 1:2.34.13-0ubuntu4.1 **Note** The key binding "F1" is mapped to "switch to workspace 1" The key binding "F2" is mapped to "switch to workspace 2" and so on. Changing the binding to "+F1" makes the binding work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1456816/+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 1453052] Re: X fails to automatically detect ATI radeon RV600 card
(Sorry for the typos but apparently there's no way to edit one's own comments after publishing :-( ) -- 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/1453052 Title: X fails to automatically detect ATI radeon RV600 card Status in xorg package in Ubuntu: Incomplete Bug description: Good day. I'm testing pure EFI boot capability on my iMac 7.1 (graphic card ATI radeon HD2600 pro). So far, with Ubuntu 14.10, i've been able to boot directly into a perfectly working system using the EFI kernel stub. No GRUB, no ELILO, no rEFIND, no boot manager whatsoever! And the result was amazing! Boot up time reduced to a fraction of the time needed by GRUB, for example, Compiz compositing much more quick, smooth and and efficient. I could notice even some graphical detail (e.g. Text shadows in the GDM log-in screen) that were not present if booting via GRUB. The way to accomplished this is simple: 1) Create a small (40MB or less) HFS+ partition. E.g. #> sudo mkfs.hfsplus /dev/sdaX -v "Ubuntu (EFI-Stub)" 2) Copy to the new partition the files vmlinuz-3.XX.YY-ZZ-generic.efi.signed and initrd.img-3.XX.YY-ZZ-generig. Also rename them to "vmlinuz.efi" and "initrd.img" for sake of simplicity in further command line work. Furthermore, Apple's EFI won't boot anything that doesn't end with the ".efi" extension. 3) Create a boot entry in the NVRAM using efibootmgr like this: #> sudo efibootmgr -d /dev/sdX -p Y -c -L "Ubuntu 14.04 LTS" -l /vmlinuz.efi -u "root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash initrd=\initrd.img" 4) reboot (and enjoy!) As i've said, in Ubuntu 14 all this is working fine, but after the upgrade to Ubuntu 15, "X" doesn't start anymore. The system starts up correctly but X fails (with error: (EE) No devices detected. (EE) Fatal server error: (EE) no screens found) dropping me to a tty console login. I'm not shure if it is a X problem or a kernel KMS bug, but i'm more inclined to think of a problem with X because i've tried to boot Ubuntu 15.0 with the old kernel (3.13/16) and the problem is still there. I've also tried to add "vt.handoff=7" to the command line args for the kernel, like grub does, but the result is even worse. The system freezes completely at the moment of starting X. Please note also that booting via grub is working. X starts, much more slowly but starts. (Actually i'm reporting this bug from the very same system booted using GRUB. I have a second HFS+ partition where i installed grub and i can access it by holding down the ALT key at power-up) Thanks for your work. I really hope that booting directly via EFI stubs will grow mature because the performance increase is really big. Thanks again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 8 10:20:35 2015 DistUpgraded: 2015-05-06 18:46:56,830 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-16-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-16-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2013-10-27 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Apple Inc. iMac7,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-05-06 (1 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238CC8 dmi.modalias: dmi:bvnAppleI
[Desktop-packages] [Bug 1457490] Re: Chrome using only one core after S3/resume
Also, it seems unlikely to be related, but does it happen every time, or only when you see, in "dmesg", [13078.843784] Corrupted low memory at 880067f0 (67f0 phys) = 2001 [13078.843808] [ cut here ] [13078.843819] WARNING: CPU: 0 PID: 17156 at /home/kernel/COD/linux/arch/x86/kernel/check.c:140 check_for_bios_corruption+0x10e/0x120() [13078.843821] Memory corruption detected in low memory -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: Incomplete Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bu
[Desktop-packages] [Bug 1457490] Re: Chrome using only one core after S3/resume
Is this reported in the same boot lifetime as seeing the bug? I want to know if the proccpuinfo attachment is after seeing the bug. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: Incomplete Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1457490/+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/Li
[Desktop-packages] [Bug 1453052] Re: X fails to automatically detect ATI radeon RV600 card
RaffaeleC, if you install with UEFI/Secure Boot disabled in the BIOS, does that allow you to test the latest kernel? -- 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/1453052 Title: X fails to automatically detect ATI radeon RV600 card Status in xorg package in Ubuntu: Incomplete Bug description: Good day. I'm testing pure EFI boot capability on my iMac 7.1 (graphic card ATI radeon HD2600 pro). So far, with Ubuntu 14.10, i've been able to boot directly into a perfectly working system using the EFI kernel stub. No GRUB, no ELILO, no rEFIND, no boot manager whatsoever! And the result was amazing! Boot up time reduced to a fraction of the time needed by GRUB, for example, Compiz compositing much more quick, smooth and and efficient. I could notice even some graphical detail (e.g. Text shadows in the GDM log-in screen) that were not present if booting via GRUB. The way to accomplished this is simple: 1) Create a small (40MB or less) HFS+ partition. E.g. #> sudo mkfs.hfsplus /dev/sdaX -v "Ubuntu (EFI-Stub)" 2) Copy to the new partition the files vmlinuz-3.XX.YY-ZZ-generic.efi.signed and initrd.img-3.XX.YY-ZZ-generig. Also rename them to "vmlinuz.efi" and "initrd.img" for sake of simplicity in further command line work. Furthermore, Apple's EFI won't boot anything that doesn't end with the ".efi" extension. 3) Create a boot entry in the NVRAM using efibootmgr like this: #> sudo efibootmgr -d /dev/sdX -p Y -c -L "Ubuntu 14.04 LTS" -l /vmlinuz.efi -u "root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash initrd=\initrd.img" 4) reboot (and enjoy!) As i've said, in Ubuntu 14 all this is working fine, but after the upgrade to Ubuntu 15, "X" doesn't start anymore. The system starts up correctly but X fails (with error: (EE) No devices detected. (EE) Fatal server error: (EE) no screens found) dropping me to a tty console login. I'm not shure if it is a X problem or a kernel KMS bug, but i'm more inclined to think of a problem with X because i've tried to boot Ubuntu 15.0 with the old kernel (3.13/16) and the problem is still there. I've also tried to add "vt.handoff=7" to the command line args for the kernel, like grub does, but the result is even worse. The system freezes completely at the moment of starting X. Please note also that booting via grub is working. X starts, much more slowly but starts. (Actually i'm reporting this bug from the very same system booted using GRUB. I have a second HFS+ partition where i installed grub and i can access it by holding down the ALT key at power-up) Thanks for your work. I really hope that booting directly via EFI stubs will grow mature because the performance increase is really big. Thanks again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 8 10:20:35 2015 DistUpgraded: 2015-05-06 18:46:56,830 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-16-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-16-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2013-10-27 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Apple Inc. iMac7,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-05-06 (1 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238CC8 dmi.modalias:
[Desktop-packages] [Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
weird, it seems that it keeps getting change events ... does "gvfs-ls trash:///" works? does it work if you uninstall python-nautilus? do you get the same issue in a guest session? ** Changed in: nautilus (Ubuntu) Status: Incomplete => 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/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// Status in nautilus package in Ubuntu: New Bug description: Package version 1:3.14.2-0ubuntu9 from http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages Ubuntu 15.04 amd64 on an i5-4670K CPU Hi, I'm currently getting a consistent SIGSEGV from Nautilus when attempting to open the rubbish bin. This happens whether I click the bookmark on the left or instantaneously if I run `nautilus trash://`. The crash occurs before the icons have fully loaded, but a second after the rubbish bin is selected. I installed the debug symbols for nautilus and ran with gdb and got the following output: (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". (nautilus:21736): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:21736): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:21736): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [Thread 0x77f8ba00 (LWP 21736) exited] [Inferior 1 (process 21736) exited normally] (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". nautilus-wipe-Message: Initializing [New Thread 0x7fffe9017700 (LWP 22649)] [Thread 0x7fffe9017700 (LWP 22649) exited] [New Thread 0x7fffc1347700 (LWP 22680)] [New Thread 0x7fffe35f1700 (LWP 22651)] [New Thread 0x7fffe3fff700 (LWP 22650)] [New Thread 0x7fffe9818700 (LWP 22648)] Program received signal SIGSEGV, Segmentation fault. 0x7372332e in __GI__IO_default_xsputn (f=0x7f7ff5f0, data=0x50e080, n=6) at genops.c:447 447 genops.c: No such file or directory. I can provide more info if needed as I can easily reproduce the bug. I know a little about using gdb as well, but may need a bit of guidance as I'm no hardened C programmer. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+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 1457490] [NEW] Chrome using only one core after S3/resume
Public bug reported: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwMDAwCiAgAaQCAQQAAjqA0HI4LUAQLEWACSUhAAAeAR0AclHQHiBuKFUACSUhAAAeAR0AvFLQHiC4KFVACSUhAAAejArQkCBAMSAMQFUACSUhAAAYjArQiiDgLRAQPpYACSUhAAAYXg== dpms: On modes: 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: AP///wAebaxZAQEBAQUWAQOAMx146mJ1o1VPoCcSUFQhCABxQIHAgQCBgJUAkECpwLMAAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/AAyNEVBNTMKICAgICAg/wAKICAgICAgICAgICAgAQYCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1400x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 640x480 640x480 enabled: enabled status: connected Date: Thu May 21 15:34:51 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6096 bytes, mtime: Sun Apr 5 13:24:25 2015) Load-Avg-1min: 5.28 Load-Processes-Running-Percent: 0.5% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc2-generic root=/dev/sda6 ro nosplash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75Pro4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. etcconfigc09flashstalenesscheck: FLASH_STALENESS_REWARN_AT_SOONEST=3 #days FLASH_STALENESS_MAX_TRIES_PER_100_DAYS=5 FLASH_STALENESS_WARN_DIR=~/.config/chromium/Ubuntu/stale-flashplayer-warned FLASH_STALENESS_OBSELETE_PACKAGES="flashplugin-installer adobe-flash-player" FLASH_STALENESS_GOOD_PACKAGE=adobe-flashplugin gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium.browser.default: [modified] modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-21T22:10:33.392304 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed third-party-packages wily -- 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/1457490 Title: Chrome using only one core after S3/resume Status in chromium-browser package in Ubuntu: New Bug description: Cant say anymore. I experienced the same issue with many kernels. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 42.0.2311.135-1ubuntu1.1160 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DVI.D.1: edid-base64: AP///wBMLZUHNDJBMykUAQOANB14KizBpFZQoSgPUFS/74CBAIFAgYCVAKlAswBxT5UPAjqAGHE4LUBYLEUACSUhAAAe/QA4Sx5REQAKICAgICAg/ABTQTMwMC9TQTM1MAog/wBIMUFLNTAwM
[Desktop-packages] [Bug 1453052] Re: X fails to automatically detect ATI radeon RV600 card
Ok. Here I am with fresh test results. I've swapped everything and reinstalled Vivid from scratch, from the amd64.iso. The bug is still there. Something has changed but the main problem is still there. This time systemd, instead of simply dropping me to a console login, complains about the system running in low graphics mode and asks me what to do next (whether to continue in low graphics mode, to display error logs or fall back to a tty login). However, strangely enough, I've noticed that in the last update the efi stub has disappeared from the kernel. The latest kernel (3.19.0-18) version doesn't install an efi stub, so I've been forced to use the old 3.19.0-16 version. Problems with efi stubs? ?field.comment=Ok. Here I am with fresh test results. I've swapped everything and reinstalled Vivid from scratch, from the amd64.iso. The bug is still there. Something has changed but the main problem is still there. This time systemd, instead of simply dropping me to a console login, complains about the system running in low graphics mode and asks me what to do next (whether to continue in low graphics mode, to display error logs or fall back to a tty login). However, strangely enough, I've noticed that in the last update the efi stub has disappeared from the kernel. The latest kernel (3.19.0-18) version doesn't install an efi stub, so I've been forced to use the old 3.19.0-16 version. Problems with efi stubs? ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453052/+attachment/4401742/+files/Xorg.0.log -- 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/1453052 Title: X fails to automatically detect ATI radeon RV600 card Status in xorg package in Ubuntu: Incomplete Bug description: Good day. I'm testing pure EFI boot capability on my iMac 7.1 (graphic card ATI radeon HD2600 pro). So far, with Ubuntu 14.10, i've been able to boot directly into a perfectly working system using the EFI kernel stub. No GRUB, no ELILO, no rEFIND, no boot manager whatsoever! And the result was amazing! Boot up time reduced to a fraction of the time needed by GRUB, for example, Compiz compositing much more quick, smooth and and efficient. I could notice even some graphical detail (e.g. Text shadows in the GDM log-in screen) that were not present if booting via GRUB. The way to accomplished this is simple: 1) Create a small (40MB or less) HFS+ partition. E.g. #> sudo mkfs.hfsplus /dev/sdaX -v "Ubuntu (EFI-Stub)" 2) Copy to the new partition the files vmlinuz-3.XX.YY-ZZ-generic.efi.signed and initrd.img-3.XX.YY-ZZ-generig. Also rename them to "vmlinuz.efi" and "initrd.img" for sake of simplicity in further command line work. Furthermore, Apple's EFI won't boot anything that doesn't end with the ".efi" extension. 3) Create a boot entry in the NVRAM using efibootmgr like this: #> sudo efibootmgr -d /dev/sdX -p Y -c -L "Ubuntu 14.04 LTS" -l /vmlinuz.efi -u "root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash initrd=\initrd.img" 4) reboot (and enjoy!) As i've said, in Ubuntu 14 all this is working fine, but after the upgrade to Ubuntu 15, "X" doesn't start anymore. The system starts up correctly but X fails (with error: (EE) No devices detected. (EE) Fatal server error: (EE) no screens found) dropping me to a tty console login. I'm not shure if it is a X problem or a kernel KMS bug, but i'm more inclined to think of a problem with X because i've tried to boot Ubuntu 15.0 with the old kernel (3.13/16) and the problem is still there. I've also tried to add "vt.handoff=7" to the command line args for the kernel, like grub does, but the result is even worse. The system freezes completely at the moment of starting X. Please note also that booting via grub is working. X starts, much more slowly but starts. (Actually i'm reporting this bug from the very same system booted using GRUB. I have a second HFS+ partition where i installed grub and i can access it by holding down the ALT key at power-up) Thanks for your work. I really hope that booting directly via EFI stubs will grow mature because the performance increase is really big. Thanks again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date:
[Desktop-packages] [Bug 1453052] Re: X fails to automatically detect ATI radeon RV600 card
** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453052/+attachment/4401743/+files/Xorg.0.log.old -- 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/1453052 Title: X fails to automatically detect ATI radeon RV600 card Status in xorg package in Ubuntu: Incomplete Bug description: Good day. I'm testing pure EFI boot capability on my iMac 7.1 (graphic card ATI radeon HD2600 pro). So far, with Ubuntu 14.10, i've been able to boot directly into a perfectly working system using the EFI kernel stub. No GRUB, no ELILO, no rEFIND, no boot manager whatsoever! And the result was amazing! Boot up time reduced to a fraction of the time needed by GRUB, for example, Compiz compositing much more quick, smooth and and efficient. I could notice even some graphical detail (e.g. Text shadows in the GDM log-in screen) that were not present if booting via GRUB. The way to accomplished this is simple: 1) Create a small (40MB or less) HFS+ partition. E.g. #> sudo mkfs.hfsplus /dev/sdaX -v "Ubuntu (EFI-Stub)" 2) Copy to the new partition the files vmlinuz-3.XX.YY-ZZ-generic.efi.signed and initrd.img-3.XX.YY-ZZ-generig. Also rename them to "vmlinuz.efi" and "initrd.img" for sake of simplicity in further command line work. Furthermore, Apple's EFI won't boot anything that doesn't end with the ".efi" extension. 3) Create a boot entry in the NVRAM using efibootmgr like this: #> sudo efibootmgr -d /dev/sdX -p Y -c -L "Ubuntu 14.04 LTS" -l /vmlinuz.efi -u "root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash initrd=\initrd.img" 4) reboot (and enjoy!) As i've said, in Ubuntu 14 all this is working fine, but after the upgrade to Ubuntu 15, "X" doesn't start anymore. The system starts up correctly but X fails (with error: (EE) No devices detected. (EE) Fatal server error: (EE) no screens found) dropping me to a tty console login. I'm not shure if it is a X problem or a kernel KMS bug, but i'm more inclined to think of a problem with X because i've tried to boot Ubuntu 15.0 with the old kernel (3.13/16) and the problem is still there. I've also tried to add "vt.handoff=7" to the command line args for the kernel, like grub does, but the result is even worse. The system freezes completely at the moment of starting X. Please note also that booting via grub is working. X starts, much more slowly but starts. (Actually i'm reporting this bug from the very same system booted using GRUB. I have a second HFS+ partition where i installed grub and i can access it by holding down the ALT key at power-up) Thanks for your work. I really hope that booting directly via EFI stubs will grow mature because the performance increase is really big. Thanks again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 8 10:20:35 2015 DistUpgraded: 2015-05-06 18:46:56,830 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-16-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-16-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2013-10-27 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Apple Inc. iMac7,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=b0c4efb9-95b0-4e5d-98e1-8beb43f413c2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-05-06 (1 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Ma
[Desktop-packages] [Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors
This bug was fixed in the package at-spi2-core - 2.16.0-1ubuntu1 --- at-spi2-core (2.16.0-1ubuntu1) wily; urgency=medium * Merge from Debian unstable, remaining changes: - Load the at-spi2 registry as part of the Ubuntu upstart user session * Remove respawn keyword from upstart file, the service gets restarted via dbus if required (LP: #1228567) -- Luke Yelavich Mon, 18 May 2015 14:43:06 +1000 ** Changed in: at-spi2-core (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors Status in at-spi2-core package in Ubuntu: Fix Released Bug description: Sometimes I get the following messages in .xsession-errors init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+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 1453812] Re: System freeze when using LibreOffice Writer
** Tags removed: bios-outdated-3.57 ** Tags added: latest-bios-3.57 -- 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/1453812 Title: System freeze when using LibreOffice Writer Status in linux package in Ubuntu: Incomplete Bug description: LibreOffice Writer is freezing the system after a few minutes (Ubuntu 15.04, libreoffice-writer 4.4.2-0ubuntu1): the only possible action is moving the mouse pointer on the screen. Impossible to connect to a tty session to kill Xorg. A physical reboot is necessary. Note that I used LibreOffice Calc without problem. The problem has been encountered also under Fedora 21: http://forums.fedora-fr.org/viewtopic.php?id=63428 The solution proposed on this french forum is to replace the "nouveau" driver by the "nvidia" proprietary driver (340.76). It works for me. --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 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 DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:063a] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Z400 Workstation Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G3 v03.07 dmi.board.asset.tag: CZC0195Y06 dmi.board.name: 0B4Ch dmi.board.vendor: Hewlett-Packard dmi.board.version: D dmi.chassis.asset.tag: CZC0195Y06 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G3v03.07:bd04/06/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z400 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed May 20 08:19:58 2015 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453812/+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 1453812] Re: System freeze when using LibreOffice Writer
vmagnin, 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where XY and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ 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. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1453812 Title: System freeze when using LibreOffice Writer Status in linux package in Ubuntu: Incomplete Bug description: LibreOffice Writer is freezing the system after a few minutes (Ubuntu 15.04, libreoffice-writer 4.4.2-0ubuntu1): the only possible action is moving the mouse pointer on the screen. Impossible to connect to a tty session to kill Xorg. A physical reboot is necessary. Note that I used LibreOffice Calc without problem. The problem has been encountered also under Fedora 21: http://forums.fedora-fr.org/viewtopic.php?id=63428 The solution proposed on this french forum is to replace the "nouveau" driver by the "nvidia" proprietary driver (340.76). It works for me. --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 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 DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:063a] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Z400 Workstation Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G3 v03.07 dmi.board.asset.tag: CZC0195Y06 dmi.board.name: 0B4Ch dmi.board.vendor: Hewlett-Packard dmi.board.version: D dmi.chassis.asset.tag: CZC0195Y06 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G3v03.07:bd04/06/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z400 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1442979] Re: Simple Scan crashes with Brother DCP-J4120DW
This bug is now fixed: a driver update from Brother has solved the issue. Updated driver brscan4 version 0.4.3-1 is available for download from the Brother support web site, along with full installation instructions. ** Changed in: simple-scan (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1442979 Title: Simple Scan crashes with Brother DCP-J4120DW Status in simple-scan package in Ubuntu: Invalid Bug description: I am using Ubuntu 14.04.2 LTS Simple Scan, version 3.12.1-0ubuntu1, crashes when attempting to scan from Brother multi-function printer/scanner DCP-J4120DW. I have installed the Brother drivers using the software linux-brpinter-installer-2.0.0-1 from the Brother support web site. I then edited the file /lib/udev/rules.d/40-libsane.rules to add the two lines:- # Brother scanners ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes" as per this web site:- http://support.brother.com/g/s/id/linux/en/instruction_scn1c.html?c=gb&lang=en&prod=dcpj4120dw_eu_as&redirect=on When scanning using Simple Scan the scanner starts the scanning process but Simple Scan crashes. Debug output:- Segmentation fault (core dumped) lsusb output:- Bus 001 Device 005: ID 04f9:0339 Brother Industries, Ltd I have installed xsane and the scanner works correctly with this software. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: simple-scan 3.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: Unity Date: Sat Apr 11 23:41:08 2015 DriverPackageVersions: libsane 1.0.23-3ubuntu3.1 libsane-extras N/A hplip 3.14.3-0ubuntu3.2 hpoj N/A InstallationDate: Installed on 2014-05-27 (319 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP Compaq dx2400 Microtower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=3ca5b603-b5e7-46b4-ab1a-5e7bccd70761 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.23 dmi.board.name: 2A73 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: CZC8272QGT dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.23:bd04/21/2008:svnHewlett-Packard:pnHPCompaqdx2400Microtower:pvr:rvnPEGATRONCORPORATION:rn2A73:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: HP Compaq dx2400 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1442979/+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