[Desktop-packages] [Bug 897188] Re: Evolution doesn't get new messages from an IMAP server after suspend/resume
Have bug, will travel (to the competition). The reports, esp. those by iannis67 are acccurate and complete. Even a plausible diagnosis is offered. Isn't evolution Ubuntu's default install for a mail reader? Is this yet another example of we don't care under the guise of we're incompetent? Meanwhile evolution spins and spins and spins and hangs. Nice day. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/897188 Title: Evolution doesn't get new messages from an IMAP server after suspend/resume Status in evolution package in Ubuntu: Confirmed Bug description: Hi, if you have an open imap session and suspend/resume your notebook, evolution is unable to fetch new messages (at least if you are doing NAT). Most probably this is caused by open tcp sessions that aren't reestablished after resume. Best would be to kill all tcp connections when suspending and recreating them after a resume. This is a regression! It still worked in Ubuntu 11.04. Cheers, Andreas ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Nov 28 12:57:50 2011 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-11-18 (10 days ago) XsessionErrors: (gnome-settings-daemon:1786): Gdk-WARNING **: The program 'gnome-settings-daemon' received an X Window System error. (krb5-auth-dialog:1814): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/897188/+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 1430818] Re: package firefox 36.0+build2-0ubuntu0.14.04.4 failed to install/upgrade: cannot copy extracted data for './usr/lib/firefox/omni.ja' to '/usr/lib/firefox/omni.ja.dpk
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: firefox (Ubuntu) Status: New = Invalid -- 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/1430818 Title: package firefox 36.0+build2-0ubuntu0.14.04.4 failed to install/upgrade: cannot copy extracted data for './usr/lib/firefox/omni.ja' to '/usr/lib/firefox/omni.ja.dpkg-new': unexpected end of file or stream Status in firefox package in Ubuntu: Invalid Bug description: in an effort to sllow down firefox crashes, and to get flash plug-in installer working again, I used a downloaded firefox and installed into /opt. Perhaps the installer would have worked looking for firefox-old or if I had guidance to change back to the original Ubuntu firefox firefox.so. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: firefox 36.0+build2-0ubuntu0.14.04.4 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vcbrad 2071 F pulseaudio BuildID: 20150224134236 Channel: Unavailable Date: Wed Mar 11 09:12:01 2015 DuplicateSignature: package:firefox:36.0+build2-0ubuntu0.14.04.4:cannot copy extracted data for './usr/lib/firefox/omni.ja' to '/usr/lib/firefox/omni.ja.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/firefox/omni.ja' to '/usr/lib/firefox/omni.ja.dpkg-new': unexpected end of file or stream ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-09-02 (190 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.5 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 36.0+build2-0ubuntu0.14.04.4 failed to install/upgrade: cannot copy extracted data for './usr/lib/firefox/omni.ja' to '/usr/lib/firefox/omni.ja.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/25/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 0405 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision0405:bd08/25/2006:svnwortmann:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: wortmann To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1430818/+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 1420395] Re: upower consuming over 17% cpu
** Changed in: canonical-devices-system-image Milestone: ww11-ota = ww13-ota -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: upower consuming over 17% cpu Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
This bug was fixed in the package fglrx-installer - 2:15.200-0ubuntu1 --- fglrx-installer (2:15.200-0ubuntu1) vivid; urgency=medium * New upstream release: - Add support for X ABI 19. * debian/control.in: - Drop conflicts/provides/replaces libopencl1 (LP: #1129409). * debian/dkms.conf.in: - Drop all the patches. * debian/substvars: - Add support for X ABI 19. * debian/patches/series: - Drop amdxdg-su-add-support-for-pkexec.patch. -- Alberto Milone alberto.mil...@canonical.com Wed, 11 Mar 2015 16:03:18 +0100 ** Changed in: fglrx-installer (Ubuntu) Status: In Progress = Fix Released -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
Hi Natalia, Can you please download the ' hplip-3.15.2.run ' auto installer file from http://hplipopensource.com/hplip-web/gethplip.html. Run command 'sh hplip-3.15.2.run' in terminal. This will warn that auto installation is not supported for ubuntu 15.04 . But you can still proceed to install. Let us know if the installation went smooth. After installation, try configuring the printer using command 'hp-setup' . Let us know if you are facing the same as above. Rgds, goutam -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1430561 Title: hp-plugin crashes with error: Python gobject/dbus may be not installed Status in HP Linux Imaging and Printing: Confirmed Status in One Hundred Papercuts: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: When trying to configure an HP LaserJet P1102w, when running hp-plugin I get errors and can not proceed: nessita@miro:~$ hp-plugin error: Unable to locate models.dat file HP Linux Imaging and Printing System (ver. 3.15.2) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Plugin Self Extracting Archive... Error importing HPLIP modules. Is HPLIP installed? error: Python gobject/dbus may be not installed error: Plug-in install failed. Done. nessita@miro:~$ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hplip 3.15.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 19:23:41 2015 InstallationDate: Installed on 2014-11-30 (100 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet MachineType: LENOVO 3249CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET61WW (1.31 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1430561/+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 1430867] [NEW] [15.04] Unity quicklists disappear when mouse is not focused over launcher.
Public bug reported: Right-clicking an icon on the Unity tray (not sure of the real name) and attempting to click any menu item causes the menu to disappear, before it can even be reached. The menu disappears the moment the mouse exits the panel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic i686 ApportVersion: 2.16.2-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 11 10:46:22 2015 InstallationDate: Installed on 2015-03-11 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150306) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 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/1430867 Title: [15.04] Unity quicklists disappear when mouse is not focused over launcher. Status in unity package in Ubuntu: New Bug description: Right-clicking an icon on the Unity tray (not sure of the real name) and attempting to click any menu item causes the menu to disappear, before it can even be reached. The menu disappears the moment the mouse exits the panel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic i686 ApportVersion: 2.16.2-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 11 10:46:22 2015 InstallationDate: Installed on 2015-03-11 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150306) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1430867/+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 1427344] Re: cups-browsed crashed with SIGSEGV in timeout_free()
** Branch linked: lp:ubuntu/vivid-proposed/cups-filters -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1427344 Title: cups-browsed crashed with SIGSEGV in timeout_free() Status in cups-filters package in Ubuntu: Triaged Bug description: on every boot ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.66-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Mar 2 17:27:28 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-01-25 (35 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150125) Lpstat: device for HP-Photosmart-C3100-series: usb://HP/Photosmart%20C3100%20series?serial=MY6ABC32ND04P9interface=1 MachineType: ASUS All Series Papersize: a4 PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 3.14.6 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=a1f4e400-6d47-4810-8d22-d51139013aa1 ro resume=UUID=c756b5d8-0950-4dd7-8532-4932aac06078 quiet splash vga=845 SegvAnalysis: Segfault happened at: 0x7fdf8bc9a15a:movl $0x1,0xa8(%rax) PC (0x7fdf8bc9a15a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C 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.:bvr1802:bd01/28/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1427344/+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 1430887] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1427344 *** https://bugs.launchpad.net/bugs/1427344 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 #1427344, 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/1430887/+attachment/4341389/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1430887/+attachment/4341392/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1430887/+attachment/4341399/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1430887/+attachment/4341401/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1430887/+attachment/4341402/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1430887/+attachment/4341403/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1430887/+attachment/4341404/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1427344 cups-browsed crashed with SIGSEGV in timeout_free() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1430887 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() Status in cups-filters package in Ubuntu: New Bug description: I'm not sure what else is going on - I'm using XFCE, have the indicator panel item removed (oh, it causes a MESS) and see this at most startups. This does appear to happen BEFORE the panels load, so it may be that a dependency is MIA. Disabling cups-browsed might be an option, but not one that would be sustainable, I expect, for the majority of users. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.66-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CupsErrorLog: Date: Wed Mar 11 11:21:49 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-07 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Lpstat: device for EPSON_Epson_Stylus_Photo_R3000: ipps://Valhalla-5.local:631/printers/EPSON_Epson_Stylus_Photo_R3000 device for OfficeDeskjet: hp:/net/Deskjet_3050_J610_series?zc=HP4CDBF8 MachineType: Dell Inc. Inspiron 7547 Papersize: letter PpdFiles: OfficeDeskjet: HP Deskjet 3050 j610 Series, hpcups 3.15.2 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic.efi.signed root=UUID=821f9366-ae73-4bfe-871f-14244850b95c ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7feb26ce215a:movl $0x1,0xa8(%rax) PC (0x7feb26ce215a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to vivid on 2015-03-07 (4 days ago) UserGroups: dmi.bios.date: 10/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0AM670 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/27/2014:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7547 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1430887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users
** Description changed: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so - this FFe is a proposal to make Fcitx the default for Chinese locales - this cycle, as a transition towards making Fcitx the default for all - users next cycle. The changes should simply be seeding Fcitx and its - related packages on the CD image, as well as possible changes to im- - config. Those who have explicitly selected IBus as their chosen input - method should be unaffected; these changes will only affect new users, - and users who have never explicitly chosen an input method framework in - their language settings. + this FFe is a proposal to install Fcitx via language-selector for users + who want the Chinese langpacks installed, as a transition towards making + Fcitx the default for all users next cycle. This will involve changes to + language-selector, im-config, and language-pack-zh-*. Those who are not + using the Chinese langpack, or have explicitly selected IBus as their + chosen input method should be unaffected; these changes will only affect + new Chinese users, and Chinese users who have never explicitly chosen an + input method framework in their language settings. ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Also affects: im-config (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to install Fcitx via language-selector for users who want the Chinese langpacks installed, as a transition towards making Fcitx the default for all users next cycle. This will involve changes to language-selector, im-config, and language-pack- zh-*. Those who are not using the Chinese langpack, or have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new Chinese users, and Chinese users who have never explicitly chosen an input method framework in their language settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 859101] Re: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete file: .../linux/version.h)
Same problem on Ubuntu 14.04.2. Can't install fglrx for HD3300. version.h is missing. The worst part is that the default drivers are very slow and trying to run a virtual machine with them is almost impossible. I hope this can be fixed, it seems it's been a problem for a long time. -- 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/859101 Title: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete file: .../linux/version.h) Status in fglrx-installer package in Ubuntu: Confirmed Status in fglrx-installer-experimental-12 package in Ubuntu: Confirmed Status in fglrx-installer-updates package in Ubuntu: Confirmed Bug description: attempting to install ATI proprietry drivers ProblemType: Package DistroRelease: Ubuntu 11.10 Package: fglrx 2:8.881-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 DKMSBuildLog: DKMS make.log for fglrx-8.881 for kernel 3.0.0-11-generic (i686) Sun Sep 25 19:46:44 BST 2011 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.0.0-11-generic/build/include not found or incomplete file: /lib/modules/3.0.0-11-generic/build/include/linux/version.h DKMSKernelVersion: 3.0.0-11-generic Date: Sun Sep 25 19:46:48 2011 DuplicateSignature: DKMS make.log for fglrx-8.881 for kernel 3.0.0-11-generic (i686) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.0.0-11-generic/build/include not found or incomplete file: /lib/modules/3.0.0-11-generic/build/include/linux/version.h InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.1) PackageVersion: 2:8.881-0ubuntu2 SourcePackage: fglrx-installer Title: fglrx 2:8.881-0ubuntu2: fglrx 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/859101/+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 1427602] Re: input language change in login screen is not persisted after login
is anybody on this ? :) it BUGS me :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1427602 Title: input language change in login screen is not persisted after login Status in unity-greeter package in Ubuntu: Incomplete Bug description: environment details === - release: 14.10 - OS arch: 64bit - relevant package versions: - unity-greeter: 14.10.2-0ubuntu1 - lightdm: 1.12.1-0ubuntu1 - language-selector-common/language-selector-gnome: 0.135 prerequisites = - system is configured with two installed input languages/keyboard layouts. - login is configured to be locked by password. steps to reproduce == 1. when logged in, change the input language to one other than the default (He in my case, En is default). 2. log out/lock. 3. while still in the login screen, change the input language back to the default (En in my case). 4. login using a password. expected result === after login, the input language selected in the login screen should be selected. actual result = after login, the input language selection made in the login screen is not persisted, and the input language selected in the previous session is now active again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1427602/+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 1430838] Re: package ffmpeg (not installed) failed to install/upgrade: zkouším přepsat soubor „/usr/bin/ffmpeg“, který je také v balíku clipgrab 3.4.8-b~utopic~NoobsLab.com
** Tags removed: need-duplicate-check -- 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/1430838 Title: package ffmpeg (not installed) failed to install/upgrade: zkouším přepsat soubor „/usr/bin/ffmpeg“, který je také v balíku clipgrab 3.4.8-b~utopic~NoobsLab.com Status in libav package in Ubuntu: New Bug description: ffmpeg not install ProblemType: Package DistroRelease: Ubuntu 14.10 Package: ffmpeg (not installed) ProcVersionSignature: Ubuntu 3.16.0-32.42-generic 3.16.7-ckt7 Uname: Linux 3.16.0-32-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 AptOrdering: ffmpeg: Install ffmpeg: Configure Architecture: amd64 Date: Wed Mar 11 15:49:17 2015 DuplicateSignature: package:ffmpeg:(not installed):zkouším přepsat soubor „/usr/bin/ffmpeg“, který je také v balíku clipgrab 3.4.8-b~utopic~NoobsLab.com ErrorMessage: zkouším přepsat soubor „/usr/bin/ffmpeg“, který je také v balíku clipgrab 3.4.8-b~utopic~NoobsLab.com InstallationDate: Installed on 2014-07-10 (243 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: libav Title: package ffmpeg (not installed) failed to install/upgrade: zkouším přepsat soubor „/usr/bin/ffmpeg“, který je také v balíku clipgrab 3.4.8-b~utopic~NoobsLab.com UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1430838/+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 1430280] Re: NetworkManager-wait-online.service not enabled after package installation
** Branch linked: lp:ubuntu/vivid-proposed/console-setup -- 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/1430280 Title: NetworkManager-wait-online.service not enabled after package installation Status in console-setup package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Triaged Bug description: After installing NetworkManager in a fresh vivid VM, NetworkManager- wait-online.service is disabled. We should consider enabling it on systems which don't have any static interfaces in /etc/network/interfaces, so that units that need network-online.target work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1430280/+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 1430280] Re: NetworkManager-wait-online.service not enabled after package installation
This bug was fixed in the package console-setup - 1.108ubuntu4 --- console-setup (1.108ubuntu4) vivid; urgency=medium * Add systemd unit for console-setup. That avoids waiting for $remote_fs during early boot. (Note: there is no need to enable it, it gets pulled in through systemd-vconsole-setup.service) (LP: #1430280) -- Martin Pitt martin.p...@ubuntu.com Wed, 11 Mar 2015 15:33:49 +0100 ** Changed in: console-setup (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1430280 Title: NetworkManager-wait-online.service not enabled after package installation Status in NetworkManager: Unknown Status in console-setup package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Bug description: After installing NetworkManager in a fresh vivid VM, NetworkManager- wait-online.service is disabled. We should consider enabling it on systems which don't have any static interfaces in /etc/network/interfaces, so that units that need network-online.target work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1430280/+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 1430280] Re: NetworkManager-wait-online.service not enabled after package installation
** Changed in: network-manager Status: Unknown = Confirmed ** Changed in: network-manager Importance: Unknown = Medium -- 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/1430280 Title: NetworkManager-wait-online.service not enabled after package installation Status in NetworkManager: Confirmed Status in console-setup package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Bug description: After installing NetworkManager in a fresh vivid VM, NetworkManager- wait-online.service is disabled. We should consider enabling it on systems which don't have any static interfaces in /etc/network/interfaces, so that units that need network-online.target work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1430280/+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 1429011] Re: 15.04 wallpapers package
Can you increase the quality of the default purple wallpaper, or have it as png? Those jpeg compression marks are ruining it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1429011 Title: 15.04 wallpapers package Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: This is the bug we'll attach the wallpapers to for the 15.04 release ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1429011/+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 1427344] Re: cups-browsed crashed with SIGSEGV in timeout_free()
Replaced g_source_destroy() by g_source_remove() in cups-browsed in upstream BZR rev. 7335. Will be included in cups-filters 1.0.67. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1427344 Title: cups-browsed crashed with SIGSEGV in timeout_free() Status in cups-filters package in Ubuntu: Triaged Bug description: on every boot ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.66-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Mar 2 17:27:28 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-01-25 (35 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150125) Lpstat: device for HP-Photosmart-C3100-series: usb://HP/Photosmart%20C3100%20series?serial=MY6ABC32ND04P9interface=1 MachineType: ASUS All Series Papersize: a4 PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 3.14.6 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=a1f4e400-6d47-4810-8d22-d51139013aa1 ro resume=UUID=c756b5d8-0950-4dd7-8532-4932aac06078 quiet splash vga=845 SegvAnalysis: Segfault happened at: 0x7fdf8bc9a15a:movl $0x1,0xa8(%rax) PC (0x7fdf8bc9a15a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C 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.:bvr1802:bd01/28/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1427344/+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 1425972]
(In reply to noitidart from comment #78) I opened my 2nd profile with this: firefox.exe -P Dev -no-remote Try firefox.exe -P Dev -new-instance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1425972 Title: Firefox no longer supports -remote parameter Status in exo: Fix Released Status in The Mozilla Firefox Browser: Fix Released Status in One Hundred Papercuts: Confirmed Status in emacs24 package in Ubuntu: Confirmed Status in exo package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in emacs24 source package in Trusty: Confirmed Status in exo source package in Trusty: Fix Committed Status in firefox source package in Trusty: Fix Released Status in emacs24 source package in Utopic: Confirmed Status in exo source package in Utopic: In Progress Status in firefox source package in Utopic: Fix Released Status in exo package in Debian: New Bug description: [Impact] As of Firefox version 36, the -remote commandline parameter was dropped. This parameter is used in versions of exo prior to 0.10.3. Because of this, opening any URLs via exo-open will cause a new firefox window to launch at the home screen. As reported, this affects the terminal, ubuntu-bug, xchat, and numerous other applications. [Test Case] 1. Set Firefox as the default web browser in Preferred Applications. 2. From a terminal, type the following: exo-open http://www.xfce.org; Expected: Firefox opens at http://www.xfce.org Actual: Firefox opens at the home page. [Regression Potential] No regressions by this change. This fixes the application call to correctly open URLs. --- [Original Report] When I click a link from an email it does not work any more. Instead of opening the link in a new tab, Firefox opens a new empty window and does not follow the link. If I change the default browser for my desktop from Firefox to Chrome, then Chrome can open the link fine. I have started seeing this today since firefox was upgraded from v35 to 36. My email client is Mozilla thunderbird at the latest stable version. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: firefox 36.0+build2-0ubuntu0.14.10.4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpottage 3729 F pulseaudio BuildID: 20150224133805 Channel: Unavailable CurrentDesktop: XFCE Date: Thu Feb 26 14:30:41 2015 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org English (GB) Language Pack - langpack-en...@firefox.mozilla.org Français Language Pack - langpack...@firefox.mozilla.org Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2013-07-02 (604 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) IpRoute: default via 192.168.1.254 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric 1 MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so (browser-plugin-libreoffice) Java(TM) Plug-in 11.25.2 - /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use) RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no RunningIncompatibleAddons: True SourcePackage: firefox SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304 UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago) dmi.bios.date: 11/23/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0XR1GT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 270 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1425972/+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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
I tried the latest suggestion (full outout below) and got an error on: error: A required dependency 'libtool (libtool - Library building support services)' is still missing. But the package is available and installed: nessita@miro:~$ apt-cache policy libtool libtool: Installed: 2.4.2-1.11 Candidate: 2.4.2-1.11 Version table: *** 2.4.2-1.11 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Full output: nessita@miro:~$ ls -l hplip-3.15.2.run -rw-rw-r-- 1 nessita nessita 21804469 Mar 11 13:05 hplip-3.15.2.run nessita@miro:~$ md5sum hplip-3.15.2.run 87307b116e58339337a7675c71e07bc1 hplip-3.15.2.run nessita@miro:~$ sh hplip-3.15.2.run Creating directory hplip-3.15.2nessita@miro:~$ ls -l hplip-3.15.2.run -rw-rw-r-- 1 nessita nessita 21804469 Mar 11 13:05 hplip-3.15.2.run nessita@miro:~$ md5sum hplip-3.15.2.run 87307b116e58339337a7675c71e07bc1 hplip-3.15.2.run nessita@miro:~$ sh hplip-3.15.2.run Creating directory hplip-3.15.2 Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Self Extracting Archive . . . HP Linux Imaging and Printing System (ver. 3.15.2) HPLIP Installer ver. 5.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Installer log saved in: hplip-install_Wed-11-Mar-2015_13:05:24.log \ note: Defaults for each question are maked with a '*'. Press enter to accept the default. error: ubuntu-15.04 version is not supported, so all dependencies may not be installed. However trying to install using ubuntu-14.10 version packages. Press 'y' to continue auto installation. Press 'n' to quit auto instalation(y=yes, n=no*): y INSTALLATION MODE - Automatic mode will install the full HPLIP solution with the most common options. Custom mode allows you to choose installation options to fit specific requirements. Please choose the
[Desktop-packages] [Bug 1430905] Re: gdm crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1419324 *** https://bugs.launchpad.net/bugs/1419324 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 #1419324, 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/1430905/+attachment/4341474/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1430905/+attachment/4341476/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1430905/+attachment/4341477/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1430905/+attachment/4341478/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1430905/+attachment/4341479/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1430905/+attachment/4341480/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1430905/+attachment/4341481/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1419324 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1430905 Title: gdm crashed with SIGSEGV in g_main_context_dispatch() Status in gdm package in Ubuntu: New Bug description: sudo apt-get install gnome-session-wayland and login with wayland. show a black screen and return gdm. cannot use wayland ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gdm 3.14.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Thu Mar 12 00:33:42 2015 ExecutablePath: /usr/sbin/gdm InstallationDate: Installed on 2015-03-08 (3 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcCmdline: /usr/sbin/gdm ProcEnviron: LANG=en_HK.UTF-8 LANGUAGE=en_HK:en PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x411b50: mov0x18(%rdi),%rax PC (0x00411b50) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gdm StacktraceTop: ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gdm crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to vivid on 2015-03-08 (2 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1430905/+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 1403828] Re: Can't set the time as Automatically from the Internet
Problem vanished after switching to systemd, so that close the task for development release. ** Changed in: unity-control-center (Ubuntu) Status: Confirmed = Won't Fix ** Changed in: ubuntukylin Status: New = Fix Released -- 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/1403828 Title: Can't set the time as Automatically from the Internet Status in Ubuntu Kylin: Fix Released Status in unity-control-center package in Ubuntu: Won't Fix Bug description: Can't set the time as Automatically from the Internet。 时间不能设置为自动从互联网获取 Steps: 1. Login system 2. Enter into system settings--TimeDate 3. Check the item Automatically from the Internet --Failed. Can't set the time as Automatically from the Internet Configuration: OS: Ubuntu Kylin Vivid x32 Daily Build 20141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1403828/+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 221288] from: Cameron Dale
*** This bug is a duplicate of bug 206898 *** https://bugs.launchpad.net/bugs/206898 Hi http://srisivan.com/product.php?chance=ksaqac67zmhdu6x7xaw Cameron Dale Sent from my iPhone -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bittornado in Ubuntu. https://bugs.launchpad.net/bugs/221288 Title: gutsy-hardy bittornado broken Status in bittornado package in Ubuntu: Incomplete Bug description: After upgarding from Gutsy to Hardy, by adjusting sources.list and upgrading all packages in Synaptic. The commands Bittornado and Bittornado-gui are no longer found. A reinstall of the two packages didn't fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bittornado/+bug/221288/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
@LocutusOfBorg: We don't need to write 'utopic-proposed' anymore, uploads are automatically mapped. ** Also affects: boinc (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: fglrx-installer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pyopencl (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-cuda-toolkit (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: starpu-contrib (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: viennacl (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pycuda (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-310-updates (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-313-updates (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319-updates (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: boinc (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: fglrx-installer (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: pyopencl (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-cuda-toolkit (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: starpu-contrib (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: viennacl (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: pycuda (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-310-updates (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-313-updates (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319-updates (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: fglrx-installer (Ubuntu Trusty) Status: New = Confirmed ** Changed in: fglrx-installer (Ubuntu Utopic) Status: New = Confirmed ** Changed in: fglrx-installer-updates (Ubuntu Trusty) Status: New = Confirmed ** Changed in: fglrx-installer-updates (Ubuntu Utopic) Status: New = Confirmed ** Changed in: boinc (Ubuntu Trusty) Status: New = Invalid ** Changed in: boinc (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-cuda-toolkit (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-cuda-toolkit (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-310-updates (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-310-updates (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-313-updates (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-313-updates (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-319 (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-319 (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu Trusty) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu Utopic) Status: New = Invalid ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Status: New = Invalid ** Changed in:
[Desktop-packages] [Bug 1431012] [NEW] network-manager, edit connections + connect + disconnect functions are disabled
Public bug reported: Some important functions in network-manager are grayed out: * edit connections * connect * disconnect To resolve the problem: * When i start nm-connection-editor in terminal as normal user it's possible to edit all interfaces without any problems. * When i start users-admin in terminal as normal user, press button advanced settings and enter my password, then the functions edit connections + connect + disconnect are possible to operate and not grayed any more untile a reboot! I already set my user to user-group netdev, but nothing happened. I tryed to dpkg-reconfigure network-manager and /etc/init.d/network-manager restart, but nothing happened. lsb_release -rd: Description:Ubuntu 12.04.5 LTS Release:12.04 apt-cache policy network-manager: network-manager: Installiert: 0.9.4.0-0ubuntu4.4.1 Kandidat:0.9.4.0-0ubuntu4.4.1 Versionstabelle: *** 0.9.4.0-0ubuntu4.4.1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.4.0-0ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.4.1 ProcVersionSignature: Ubuntu 3.2.0-77.112-generic-pae 3.2.66 Uname: Linux 3.2.0-77-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 Date: Wed Mar 11 20:57:48 2015 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.92 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-18T15:36:47 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled disabled disabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ** Attachment added: Print-Screen https://bugs.launchpad.net/bugs/1431012/+attachment/4341839/+files/nm-applet_printscreen_01.png -- 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/1431012 Title: network-manager, edit connections + connect + disconnect functions are disabled Status in network-manager package in Ubuntu: New Bug description: Some important functions in network-manager are grayed out: * edit connections * connect * disconnect To resolve the problem: * When i start nm-connection-editor in terminal as normal user it's possible to edit all interfaces without any problems. * When i start users-admin in terminal as normal user, press button advanced settings and enter my password, then the functions edit connections + connect + disconnect are possible to operate and not grayed any more untile a reboot! I already set my user to user-group netdev, but nothing happened. I tryed to dpkg-reconfigure network-manager and /etc/init.d/network-manager restart, but nothing happened. lsb_release -rd: Description: Ubuntu 12.04.5 LTS Release: 12.04 apt-cache policy network-manager: network-manager: Installiert: 0.9.4.0-0ubuntu4.4.1 Kandidat:0.9.4.0-0ubuntu4.4.1 Versionstabelle: *** 0.9.4.0-0ubuntu4.4.1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.4.0-0ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.4.1 ProcVersionSignature: Ubuntu 3.2.0-77.112-generic-pae 3.2.66 Uname: Linux 3.2.0-77-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 Date: Wed Mar 11 20:57:48 2015 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Hi Graham, are you sure trusty is affected? I grabbed today a debian directory and seemed not affected, but I might be wrong! BTW thanks for the proposed mapping hint, it will simplify the overall process :-) -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1430996] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1427344 *** https://bugs.launchpad.net/bugs/1427344 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 #1427344, 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/1430996/+attachment/4341704/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1430996/+attachment/4341707/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1430996/+attachment/4341714/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1430996/+attachment/4341716/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1430996/+attachment/4341717/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1430996/+attachment/4341718/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1430996/+attachment/4341719/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1427344 cups-browsed crashed with SIGSEGV in timeout_free() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1430996 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() Status in cups-filters package in Ubuntu: New Bug description: Crashed while I was loading a browser. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.66-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CupsErrorLog: W [10/Mar/2015:16:05:04 -0500] Notifier for subscription 488 (dbus://) went away, retrying! W [10/Mar/2015:16:05:04 -0500] Notifier for subscription 490 (dbus://) went away, retrying! W [10/Mar/2015:19:05:42 -0500] Notifier for subscription 490 (dbus://) went away, retrying! W [10/Mar/2015:19:05:42 -0500] Notifier for subscription 492 (dbus://) went away, retrying! Date: Wed Mar 11 08:34:07 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2014-11-01 (129 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Lpstat: device for Brother-DCP-7040: usb://Brother/DCP-7040?serial=000H0N393284 MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P Papersize: letter PpdFiles: Brother-DCP-7040: Brother DCP-7020 Foomatic/hl1250 (recommended) ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=6c91f609-3b5f-439a-afcd-34cb7b8a87c2 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fa04191215a:movl $0x1,0xa8(%rax) PC (0x7fa04191215a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-MA790XT-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd01/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790XT-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1430996/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1424509] Re: lsclusters claims clusters are not running, when they are under systemd
would appear to cause fallout of bug 1430025 also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1424509 Title: lsclusters claims clusters are not running, when they are under systemd Status in postgresql-common package in Ubuntu: New Bug description: $ pg_lsclusters Ver Cluster Port Status OwnerData directory Log file 9.4 main5432 down postgres /var/lib/postgresql/9.4/main /var/log/postgresql/postgresql-9.4-main.log 9.4 xnox5433 down postgres /var/lib/postgresql/9.4/xnox /var/log/postgresql/postgresql-9.4-xnox.log yet $ sudo systemctl list-units 'postgresql*' UNITLOAD ACTIVE SUB DESCRIPTION postgresql.service loaded active exited PostgreSQL RDBMS postgresql@9.4-main.service loaded active running PostgreSQL Cluster 9.4-main postgresql@9.4-xnox.service loaded active running PostgreSQL Cluster 9.4-xnox ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: postgresql-common 166bzr1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 23 02:57:52 2015 InstallationDate: Installed on 2013-08-29 (542 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829) PackageArchitecture: all SourcePackage: postgresql-common UpgradeStatus: Upgraded to vivid on 2014-11-16 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1424509/+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 1425987] Re: Cellular data connection stops after a while
So it looks you indeed have hit #1418077. This is pretty obvious by looking in the attached nmlog file, and search for connection '/208150102671184/context1'. You'll see it get disabled at 18:41:24 after a bunch of failed attempts ( modem-no-carrier ). It gets successfully auto-activated again in +5m. That said, I also see something else that concerns me. If you look at the netlog, after '/208150102671184/context1' is disabled, you'll see NM try a 'context3', 'context5', and 'context1' again. The odd thing is that the related IMSI is not '208150102671184' it's '208103698221268'. Looking at network-test-session.log ( also attached ), you'll see that '208150102671184' is the IMSI for ril_0, and that ril_1 is PIN-locked. It appears to me that NM may be trying contexts from other SIM directories it finds in /var/lib/ofono/. -- 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/1425987 Title: Cellular data connection stops after a while Status in network-manager package in Ubuntu: Incomplete Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case: 1. Disable Wifi 2. Verify that a cellular data connection is established 3. Wait... Actual result After a while (several minutes) the cellular data connection stops, eventually it'll come back but not always. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Feb 26 16:14:14 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-02-25T03:31:54 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/ubuntu/+source/network-manager/+bug/1425987/+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 1425987] Re: Cellular data connection stops after a while
I need some confirmation from Mathieu before I change this bug to Confirmed and re-title it... -- 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/1425987 Title: Cellular data connection stops after a while Status in network-manager package in Ubuntu: Incomplete Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case: 1. Disable Wifi 2. Verify that a cellular data connection is established 3. Wait... Actual result After a while (several minutes) the cellular data connection stops, eventually it'll come back but not always. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Feb 26 16:14:14 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-02-25T03:31:54 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/ubuntu/+source/network-manager/+bug/1425987/+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 1424509] Re: lsclusters claims clusters are not running, when they are under systemd
That is indeed strange. Yesterday I fixed two bugs (bug 1429734 and https://launchpad.net/ubuntu/+source/postgresql-common/166bzr2) which both caused the 9.4-main cluster to not start after package installation. To make sure it's not that, can you re-try with latest vivid? (p-common should land within the hour now, it was stuck in -proposed for a while). Otherwise, are these clusters *really* running? Check with ps aux|grep post? Can you please give me the output of systemctl status -l postgresql@9.4-main.service, and ls -la /var/run/postgresql/? ** Changed in: postgresql-common (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1424509 Title: lsclusters claims clusters are not running, when they are under systemd Status in postgresql-common package in Ubuntu: Incomplete Bug description: $ pg_lsclusters Ver Cluster Port Status OwnerData directory Log file 9.4 main5432 down postgres /var/lib/postgresql/9.4/main /var/log/postgresql/postgresql-9.4-main.log 9.4 xnox5433 down postgres /var/lib/postgresql/9.4/xnox /var/log/postgresql/postgresql-9.4-xnox.log yet $ sudo systemctl list-units 'postgresql*' UNITLOAD ACTIVE SUB DESCRIPTION postgresql.service loaded active exited PostgreSQL RDBMS postgresql@9.4-main.service loaded active running PostgreSQL Cluster 9.4-main postgresql@9.4-xnox.service loaded active running PostgreSQL Cluster 9.4-xnox ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: postgresql-common 166bzr1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 23 02:57:52 2015 InstallationDate: Installed on 2013-08-29 (542 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130829) PackageArchitecture: all SourcePackage: postgresql-common UpgradeStatus: Upgraded to vivid on 2014-11-16 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1424509/+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 1300557] Re: Screen resolution no longer works
Jeroen T. Vermeulen, could you please advise what packages were upgraded precisely on 2014-04-01 that correlates to this issue? -- 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/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+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 1424864] Re: Xorg crash
Galen Thurber, please see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/comments/13 . -- 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/1424864 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Xorg crashing out back into login manager and apport failed This problem report is damaged and cannot be processed. IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated: expected core file size = 75243520, found: 6356992.',) openConnection: connect: No such file or directory cannot connect to brltty at :0 xfce4-settings-helper: Another instance is already running. Leaving... (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Feb 23 19:14:16 2015 InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140205) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+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 1393169] Re: [Toshiba Satellite Pro C650] Double mouse cursor
** Summary changed: - Double mouse cursor + [Toshiba Satellite Pro C650] Double mouse cursor -- 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/1393169 Title: [Toshiba Satellite Pro C650] Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 28 08:29:52 2014 xserver.configfile: default xserver.errors: xserver.logfile:
[Desktop-packages] [Bug 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze
Wow! It actually works! Thanks a lot Tomasz! I hope this also helps others wth this problem and also the Ubuntu developers to find the reasons behind this error. It has been an issue for a while now... Greets. -- 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/1362848 Title: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89 from Additional Drivers application then reboot, it shows black screen, no login window, I even can't use ctrl+alt+F2 to switch to text mode, then I reboot and go to recovery mode, use 'prime-select intel' to switch to intel GPU and reboot, everything is fine, but as soon as I switch to nvidia GPU, still same issue. OS: Ubuntu 14.04 64bit Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600 Desktop: Unity Kernel: 3.13.0 CPU: Intel® Core™ i7-4700MQ Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
@LocutusOfBorg: I don't know for sure that Trusty is affected, but fglrx-installer has been marked as being affected by this bug since before Trusty was released. Also, there are specific reports about 14.04 in duplicate bug LP: #1376587. -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.
@Mark: That sounds like a MATE specific issue, related to an Ubuntu version where MATE was not an official flavour. Does it exist a mate- user-guide package, and do you have it installed? Probably you should ask the MATE team for help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1360756 Title: The URI ‘help:ubuntu-help/index’ does not point to a valid page. Status in yelp package in Ubuntu: Incomplete Bug description: after upgrading to 14.10 alpha 2 when i try to launch yelp from command or from menu it shows The URI ‘help:ubuntu-help/index’ does not point to a valid page. even when i try to search it shows the same ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.6-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Aug 24 11:53:45 2014 InstallationDate: Installed on 2012-03-24 (882 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324) SourcePackage: yelp SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1360756/+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 1430759] Re: Software center does not show up configuration dialogue for applications that needs configuration at install time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-center (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1430759 Title: Software center does not show up configuration dialogue for applications that needs configuration at install time Status in software-center package in Ubuntu: Confirmed Bug description: When I try to install lirc with Ubuntu Software Center, lirc remaining unconfigure because here does not show up configuration window for lirc package. (same same behavior for another applications that needs configuration on install e.g. tvtime) This problem does not occur when I try to install lirc from commandline with sudo apt-get install lirc. See screenshot. Steps to reproduce (example): - Open Ubuntu Software Center - Try to install tvtime (or lirc) Expected result: - An configuration dialogue shown to enter same options, after which the changed would be applied. Actual result: - Software center does not show up configuration dialogue and freezes while installing. As results users that use Ubuntu Software Center to install this apllication report same bugs: https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1374762 https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1428681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1430759/+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 1393169] Re: Double mouse cursor
the affect every ubuntu 14.04.2 (xubuntu, ubuntu gnome...) distribution and release -- 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/1393169 Title: Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 28 08:29:52 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
Re: [Desktop-packages] [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
Hey goutam, libtool was already installed in the system, I did not install it manually. I re-tried the command, and I got the same error about libtool being missing. Any other thing I can try? On Wed, Mar 11, 2015 at 2:41 PM, goutam kodu 1430...@bugs.launchpad.net wrote: After installing libtool manually.. can you retry 'sh hplip-3.15.2.run' and let us know if the installation proceeds without any issue. After install, run command ' hp-setup' to configure the device . Original message From: Natalia Bidart 1430...@bugs.launchpad.net Date: 11/03/2015 9:51 PM (GMT+05:30) To: goutam.hp...@gmail.com Subject: [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed I tried the latest suggestion (full outout below) and got an error on: error: A required dependency 'libtool (libtool - Library building support services)' is still missing. But the package is available and installed: nessita@miro:~$ apt-cache policy libtool libtool: Installed: 2.4.2-1.11 Candidate: 2.4.2-1.11 Version table: *** 2.4.2-1.11 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Full output: nessita@miro:~$ ls -l hplip-3.15.2.run -rw-rw-r-- 1 nessita nessita 21804469 Mar 11 13:05 hplip-3.15.2.run nessita@miro:~$ md5sum hplip-3.15.2.run 87307b116e58339337a7675c71e07bc1 hplip-3.15.2.run nessita@miro:~$ sh hplip-3.15.2.run Creating directory hplip-3.15.2nessita@miro:~$ ls -l hplip-3.15.2.run -rw-rw-r-- 1 nessita nessita 21804469 Mar 11 13:05 hplip-3.15.2.run nessita@miro:~$ md5sum hplip-3.15.2.run 87307b116e58339337a7675c71e07bc1 hplip-3.15.2.run nessita@miro:~$ sh hplip-3.15.2.run Creating directory hplip-3.15.2 Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Self Extracting Archive.. . . ... HP Linux Imaging and Printing System (ver. 3.15.2) HPLIP Installer ver. 5.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO
[Desktop-packages] [Bug 1429011] Re: 15.04 wallpapers package
Apparently there's some kind of tweaked version coming anyway, so there will be a new release then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1429011 Title: 15.04 wallpapers package Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: This is the bug we'll attach the wallpapers to for the 15.04 release ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1429011/+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 1309801] Re: [xubuntu] chromium redraw issue after switching workspaces
I was getting the same issue with a couple of other Blink-related browsers like Opera and Vivaldi -- 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/1309801 Title: [xubuntu] chromium redraw issue after switching workspaces Status in chromium-browser package in Ubuntu: Confirmed Bug description: When I switch between workspaces in xubuntu, the chromium windows more often than not are only partially visible or else completely transparent. Moving the window (hold alt and drag) does not always fix the issue, but resizing always does. I've taken a video I will attach to the bug. Expected: See the chromium window and tabs I have open. Actual: Window is invisible or partially invisible. See attached video. % lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 % apt-cache policy chromium-browser chromium-browser: Installed: 34.0.1847.116-0ubuntu2 Candidate: 34.0.1847.116-0ubuntu2 Version table: *** 34.0.1847.116-0ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 18 17:38:04 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 228G 16G 201G 8% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 3.7G 4.0K 3.7G 1% /dev\ntmpfs tmpfs 755M 1.1M 754M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 3.7G 20M 3.7G 1% /run/shm\nnone tmpfs 100M 52K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 15M 298K 15M3% /\nnone 944K 2 944K1% /sys/fs/cgroup\nudev 942K 500 941K1% /dev\ntmpfs 944K 495 944K1% /run\nnone 944K 3 944K1% /run/lock\nnone 944K40 944K1% /run/shm\nnone 944K85 944K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2014-04-18 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= 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.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1309801/+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 1413411] Re: underscore in mounted drive name mishandled in menu
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = In Progress ** Changed in: unity/7.2 Importance: Undecided = Medium ** Changed in: unity/7.2 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Milestone: None = 7.2.5 -- 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/1413411 Title: underscore in mounted drive name mishandled in menu Status in One Hundred Papercuts: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct host_S name; the bug is only in the right-click menu. Note that right-clicking on the Files icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. Ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 22 11:51:46 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+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 1425987] Re: Cellular data connection stops after a while
** Attachment added: NM log messages from network-test-session_20150603_102306 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425987/+attachment/4341813/+files/nmlog-lp1425987.txt -- 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/1425987 Title: Cellular data connection stops after a while Status in network-manager package in Ubuntu: Incomplete Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Test Case: 1. Disable Wifi 2. Verify that a cellular data connection is established 3. Wait... Actual result After a while (several minutes) the cellular data connection stops, eventually it'll come back but not always. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Feb 26 16:14:14 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2015-02-25 (1 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true PciNetwork: RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2015-02-25T03:31:54 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/ubuntu/+source/network-manager/+bug/1425987/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
For me, I had to check the All users may connect to this network box. -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Packages are ready in https://launchpad.net/~costamagnagianfranco/+archive/ubuntu /locutusofborg-ppa -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
** Patch added: utopic-fglrx-installer-updates.debdiff https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4341572/+files/utopic-fglrx-installer-updates.debdiff -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
oops utopic-fglrx-installer.debdiff should be against utopic-proposed -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
opened https://bugzilla.gnome.org/show_bug.cgi?id=746044 upstream about it, maybe they can comment on the issue ** Bug watch added: GNOME Bug Tracker #746044 https://bugzilla.gnome.org/show_bug.cgi?id=746044 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in unity-settings-daemon package in Ubuntu: Confirmed Status in ubiquity source package in Trusty: Confirmed Status in unity-settings-daemon source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+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 1424864] Re: Xorg crash
actually Chris the activity log shows you as the person deleting attachments. why? -- 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/1424864 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Xorg crashing out back into login manager and apport failed This problem report is damaged and cannot be processed. IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated: expected core file size = 75243520, found: 6356992.',) openConnection: connect: No such file or directory cannot connect to brltty at :0 xfce4-settings-helper: Another instance is already running. Leaving... (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Feb 23 19:14:16 2015 InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140205) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+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 1094114] Re: Disk Usage Analyzer crashes when selecting the About dialog from the menu
I no longer get a problem in Trusty either. As far as I am concerned you can close this now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1094114 Title: Disk Usage Analyzer crashes when selecting the About dialog from the menu Status in baobab package in Ubuntu: Incomplete Bug description: The Disk Usage Analyzer crashes when selecting the About dialog from the menu. I am using Ubuntu 12.10 and baobab 3.6.0-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1094114/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
This bug was fixed in the package fglrx-installer-updates - 2:15.200-0ubuntu1 --- fglrx-installer-updates (2:15.200-0ubuntu1) vivid; urgency=medium * New upstream release: - Add support for X ABI 19. * debian/control.in: - Drop conflicts/provides/replaces libopencl1 (LP: #1129409). * debian/dkms.conf.in: - Drop all the patches. * debian/substvars: - Add support for X ABI 19. * debian/patches/series: - Drop amdxdg-su-add-support-for-pkexec.patch. -- Alberto Milone alberto.mil...@canonical.com Wed, 11 Mar 2015 16:10:56 +0100 ** Changed in: fglrx-installer-updates (Ubuntu) Status: In Progress = Fix Released -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
After installing libtool manually.. can you retry 'sh hplip-3.15.2.run' and let us know if the installation proceeds without any issue. After install, run command ' hp-setup' to configure the device . Original message From: Natalia Bidart 1430...@bugs.launchpad.net Date: 11/03/2015 9:51 PM (GMT+05:30) To: goutam.hp...@gmail.com Subject: [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed I tried the latest suggestion (full outout below) and got an error on: error: A required dependency 'libtool (libtool - Library building support services)' is still missing. But the package is available and installed: nessita@miro:~$ apt-cache policy libtool libtool: Installed: 2.4.2-1.11 Candidate: 2.4.2-1.11 Version table: *** 2.4.2-1.11 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Full output: nessita@miro:~$ ls -l hplip-3.15.2.run -rw-rw-r-- 1 nessita nessita 21804469 Mar 11 13:05 hplip-3.15.2.run nessita@miro:~$ md5sum hplip-3.15.2.run 87307b116e58339337a7675c71e07bc1 hplip-3.15.2.run nessita@miro:~$ sh hplip-3.15.2.run Creating directory hplip-3.15.2nessita@miro:~$ ls -l hplip-3.15.2.run -rw-rw-r-- 1 nessita nessita 21804469 Mar 11 13:05 hplip-3.15.2.run nessita@miro:~$ md5sum hplip-3.15.2.run 87307b116e58339337a7675c71e07bc1 hplip-3.15.2.run nessita@miro:~$ sh hplip-3.15.2.run Creating directory hplip-3.15.2 Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Self Extracting Archive... HP Linux Imaging and Printing System (ver. 3.15.2) HPLIP Installer ver. 5.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Installer log saved in: hplip-install_Wed-11-Mar-2015_13:05:24.log \ note: Defaults for each question are maked with a '*'. Press enter to accept the default. error: ubuntu-15.04
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
now that the bug is fixed in the current development release I prepared two debdiffs against utopic. -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
** Patch added: utopic-fglrx-installer.debdiff https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1129409/+attachment/4341571/+files/utopic-fglrx-installer.debdiff -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1424864] Re: Xorg crash
dmesg is reporting firefox crashing out [ 529.218461] show_signal_msg: 27 callbacks suppressed [ 529.218468] Chrome_ChildThr[2807]: segfault at 0 ip 7f7bc7206210 sp 7f7bb7a2d430 error 6 in libmozalloc.so[7f7bc7205000+2000] -- 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/1424864 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Xorg crashing out back into login manager and apport failed This problem report is damaged and cannot be processed. IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated: expected core file size = 75243520, found: 6356992.',) openConnection: connect: No such file or directory cannot connect to brltty at :0 xfce4-settings-helper: Another instance is already running. Leaving... (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations ERROR: Error querying target relations (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: assertion `G_IS_FILE_INFO (info)' failed WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Feb 23 19:14:16 2015 InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140205) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
Completely purged libtool and re-installed it: nessita@miro:~$ sudo apt-get purge libtool Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libtool* 0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded. After this operation, 826 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 296116 files and directories currently installed.) Removing libtool (2.4.2-1.11) ... Processing triggers for man-db (2.7.0.2-5) ... nessita@miro:~$ sudo rm -rf /usr/share/libtool/ nessita@miro:~$ sudo rm -rf /var/cache/apt/archives/libtool_2.4.2-1.11_all.deb nessita@miro:~$ sudo apt-get install libtool Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: libtool-doc gfortran fortran95-compiler gcj-jdk The following NEW packages will be installed: libtool 0 upgraded, 1 newly installed, 0 to remove and 52 not upgraded. Need to get 180 kB of archives. After this operation, 826 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ vivid/main libtool all 2.4.2-1.11 [180 kB] Fetched 180 kB in 15s (11.4 kB/s) Selecting previously unselected package libtool. (Reading database ... 296092 files and directories currently installed.) Preparing to unpack .../libtool_2.4.2-1.11_all.deb ... Unpacking libtool (2.4.2-1.11) ... Processing triggers for man-db (2.7.0.2-5) ... Same error when running sh hplip-3.15.2.run: INSTALL MISSING REQUIRED DEPENDENCIES - warning: There are 1 missing REQUIRED dependencies. note: Installation of dependencies requires an active internet connection. warning: Missing REQUIRED dependency: libtool (libtool - Library building support services) RE-CHECKING DEPENDENCIES error: A required dependency 'libtool (libtool - Library building support services)' is still missing. error: Installation cannot continue without this dependency. error: Please manually install this dependency and re-run this installer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1430561 Title: hp-plugin crashes with error: Python gobject/dbus may be not installed Status in HP Linux Imaging and Printing: Confirmed Status in One Hundred Papercuts: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: When trying to configure an HP LaserJet P1102w, when running hp-plugin I get errors and can not proceed: nessita@miro:~$ hp-plugin error: Unable to locate models.dat file HP Linux Imaging and Printing System (ver. 3.15.2) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Plugin Self Extracting Archive... Error importing HPLIP modules. Is HPLIP installed? error: Python gobject/dbus may be not installed error: Plug-in install failed. Done. nessita@miro:~$ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hplip 3.15.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 19:23:41 2015 InstallationDate: Installed on 2014-11-30 (100 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet MachineType: LENOVO 3249CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET61WW (1.31 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor:
[Desktop-packages] [Bug 1427344] Re: cups-browsed crashed with SIGSEGV in timeout_free()
This bug was fixed in the package cups-filters - 1.0.67-0ubuntu1 --- cups-filters (1.0.67-0ubuntu1) vivid; urgency=medium * New upstream release - cups-browsed: Use g_source_remove() instead of g_source_destroy() for killing auto shutdown timers (LP: #1427344). -- Till Kamppeter till.kamppe...@gmail.com Wed, 11 Mar 2015 16:31:03 +0100 ** Changed in: cups-filters (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1427344 Title: cups-browsed crashed with SIGSEGV in timeout_free() Status in cups-filters package in Ubuntu: Fix Released Bug description: on every boot ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.66-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Mar 2 17:27:28 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-01-25 (35 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150125) Lpstat: device for HP-Photosmart-C3100-series: usb://HP/Photosmart%20C3100%20series?serial=MY6ABC32ND04P9interface=1 MachineType: ASUS All Series Papersize: a4 PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 3.14.6 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=a1f4e400-6d47-4810-8d22-d51139013aa1 ro resume=UUID=c756b5d8-0950-4dd7-8532-4932aac06078 quiet splash vga=845 SegvAnalysis: Segfault happened at: 0x7fdf8bc9a15a:movl $0x1,0xa8(%rax) PC (0x7fdf8bc9a15a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C 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.:bvr1802:bd01/28/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1427344/+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 1413773] Re: [Regressions] Dash dnd icons rendered behind dash.
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = In Progress ** Changed in: unity/7.2 Importance: Undecided = High ** Changed in: unity/7.2 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Milestone: None = 7.2.5 -- 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/1413773 Title: [Regressions] Dash dnd icons rendered behind dash. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: In Ubuntu 15.04 dragged icons are rendered behind dash. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413773/+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 1404486] Re: Session dialog does not show up over fullscreen windows.
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = In Progress ** Changed in: unity/7.2 Importance: Undecided = Medium ** Changed in: unity/7.2 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Milestone: None = 7.2.5 -- 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/1404486 Title: Session dialog does not show up over fullscreen windows. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Unity session dialog does not show up over a fullscreen window if you press the hardware button. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404486/+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 517021] Re: gvfsd-metadata causes 100% CPU usage
I applied the patch to gvfs 1.20.3 on Linux Lite 2.2 (14.04l LTS) it seems to fix the issue with Super Start Firefox extension. -- 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 package in Ubuntu: Confirmed 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/ubuntu/+source/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 1311316] Re: After locking screen there is no input field to type password for unlock
The fix for this was included in some other fixes released into Ubuntu 14.04 LTS in Unity 7.2.4 (see bug #1308540). ** Changed in: unity/7.2 Status: In Progress = Fix Released ** Changed in: unity/7.2 Milestone: 7.2.5 = None -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.
The HelpContents bug still exists on MATE 1.8.x, various programs (on Ubuntu 14.04.2 LTS), including: Caja The URI ‘help:mate-user-guide/goscaja-1’ does not point to a valid page. MATE Calculator The URI ‘help:mate-user-guide/goscaja-1’ does not point to a valid page. MATE System Monitor The URI ‘help:mate-system-monitor/index’ does not point to a valid page. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1360756 Title: The URI ‘help:ubuntu-help/index’ does not point to a valid page. Status in yelp package in Ubuntu: Incomplete Bug description: after upgrading to 14.10 alpha 2 when i try to launch yelp from command or from menu it shows The URI ‘help:ubuntu-help/index’ does not point to a valid page. even when i try to search it shows the same ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.6-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Aug 24 11:53:45 2014 InstallationDate: Installed on 2012-03-24 (882 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324) SourcePackage: yelp SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1360756/+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 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts
I had this issue and then purged my system of the Intel Linux Graphics Installer packages, downgrading packages to the latest available in trusty-updates as appropriate. After doing that I was successfully able to install 14.04.2 using the Utopic HWE stack. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1429529 Title: Package resolver can't find *-lts-utopic package dependencies, aborts Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html Guess APT just get overwhelmed by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
** Also affects: ubuntukylin Importance: Undecided Status: New ** Changed in: ubuntukylin Status: New = Fix Released ** Changed in: ubuntukylin Milestone: None = vivid-beta2 ** Changed in: ubuntukylin Assignee: (unassigned) = Aron Xu (happyaron) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: New Status in Ubuntu Kylin: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+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 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Milestone: None = 7.2.5 ** Changed in: unity/7.2 Status: New = In Progress ** Changed in: unity/7.2 Importance: Undecided = Medium ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity/7.2 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity (Ubuntu) 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/1413790 Title: It's possible to bypasss lockscreen if user is in nopasswdlogin group. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Lightdm should not emit logind unlock signal when the user is not prompted for a password. This can lead to a security issue: # Log-in (unity session). # Add the current user to nopasswdlogin group. # Lock the sessions. # Session indicator-Switch account... # Login in again. Expected behavior: The lockscreen is still active. Current behavior: The session in unlocked. We could workaround the issue directly in unity, but IMHO would be cleaner to avoid that lightdm is emitting the logind signal. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413790/+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 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.
Still seems broken in Vivid? $ pulseaudio --version pulseaudio 6.0 (it's the pulseaudio 1:6.0-0ubuntu4 package) $ pactl load-module module-echo-cancel aec_method=WebRTC Failure: Module initialization failed libwebrtc is installed: libwebrtc-audio-processing-dev libwebrtc-audio-processing-0 -- 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/1261666 Title: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. Status in pulseaudio package in Ubuntu: Fix Released Bug description: Hello! 13.10. Trying to load module-echo-cancel with webrtc and get: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. I guess this is wrong... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+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 1412036] Re: Korean typing doesn't work
Not a bug, please select Hangul as the backend to be able to input Korean characters. ** Changed in: ibus-hangul (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-hangul in Ubuntu. https://bugs.launchpad.net/bugs/1412036 Title: Korean typing doesn't work Status in IBus: Unknown Status in ibus-hangul package in Ubuntu: Invalid Bug description: At the moment I have got Russian and English (UK) installed on my computer. I installed them through System Settings Language Support. But now I want to add Korean and that is where the problem has come up. So I go into the Language Support settings and click Install / Remove Languages..., I then select Korean from the list and click Apply Changes. After the installation has finished I go into the Text Entry settings: Text_Entry_GUI.bmp And click the little + sign. Then I find and add Korean from the list: Choose_an_input_source_GUI.bmp But then when I select Korean as the language I want to type as, it still stays at English. And not matter what I do, I cannot seem to get any other languages working. I am running Ubuntu 14.10. Package information: ibus-hangul: Installed: 1.4.2+git20140818-1 Candidate: 1.4.2+git20140818-1 Version table: *** 1.4.2+git20140818-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1412036/+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 1391024] Update Released
The verification of the Stable Release Update for libpwquality 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 libpwquality in Ubuntu. https://bugs.launchpad.net/bugs/1391024 Title: The prompt of Password Strength Meter hasn't been translated. Status in Ubuntu Translations: Fix Committed Status in Ubuntu Kylin: Fix Committed Status in libpwquality package in Ubuntu: Fix Released Status in libpwquality source package in Trusty: Fix Released Status in libpwquality source package in Utopic: Fix Released Bug description: * Impact the password meter hints from the user account settings are not translated * Test case - use unity7 with a non english locale - System settings-User Accounts-Unlock - Click password - place the mouse on the Password Strength Meter - the hint should be translated * Impact regression Shouldn't be one, there is no code change, it's only for launchpad import of the template --- 1. System settings-User Accounts-Unlock 2. Click password 3. place the mouse on the Password Strength Meter Failed- The prompt of Password Strength Meter hasn't been translated. Ubuntukylin-14.10-utopic; 32bit ;lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1391024/+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 1431058] Re: Stable Release Update to provide possiblity of automatically reporting crashes
** Changed in: apport (Ubuntu) Status: New = Invalid ** Changed in: apport (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: apport (Ubuntu Trusty) Status: New = In Progress ** Changed in: apport (Ubuntu Trusty) Assignee: (unassigned) = Brian Murray (brian-murray) ** Description changed: + [Test Case] + --- + 1) Install apport-noui + 2) Verify /var/lib/apport/autoreport is created + 3) sleep 1000 + 4) pkill -11 sleep + 5) observe /var/crash/_bin_sleep.crash file + 6) wait a wee bit + 7) observe /var/crash/_bin_sleep.upload and .uploaded are created + The version of apport in Ubuntu 14.04 is missing a few changes that would allow users to install apport-noui and allow crash reports to be submitted automatically from systems with it installed. The changes are the following: - * debian/apport-noui.upstart: remove early exit (LP: #1235436) - * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436) - * data/whoopsie-upload-all: backport utopic version of it - * apport-noui: make the package installation automatically enable - autosubmission, and update the package description accordingly. - LP: #1351137. + * debian/apport-noui.upstart: remove early exit (LP: #1235436) + * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436) + * data/whoopsie-upload-all: backport utopic version of it + * apport-noui: make the package installation automatically enable + autosubmission, and update the package description accordingly. + LP: #1351137. The changes to whoopsie-upload-all can be found in this revision (http://bazaar.launchpad.net/~ubuntu-core- dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP: #1354318. It would be useful if users of 14.04 could install apport- noui and have crash reports automatically submitted for them. -- 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/1431058 Title: Stable Release Update to provide possiblity of automatically reporting crashes Status in apport package in Ubuntu: Invalid Status in apport source package in Trusty: In Progress Bug description: [Test Case] --- 1) Install apport-noui 2) Verify /var/lib/apport/autoreport is created 3) sleep 1000 4) pkill -11 sleep 5) observe /var/crash/_bin_sleep.crash file 6) wait a wee bit 7) observe /var/crash/_bin_sleep.upload and .uploaded are created The version of apport in Ubuntu 14.04 is missing a few changes that would allow users to install apport-noui and allow crash reports to be submitted automatically from systems with it installed. The changes are the following: * debian/apport-noui.upstart: remove early exit (LP: #1235436) * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436) * data/whoopsie-upload-all: backport utopic version of it * apport-noui: make the package installation automatically enable autosubmission, and update the package description accordingly. LP: #1351137. The changes to whoopsie-upload-all can be found in this revision (http://bazaar.launchpad.net/~ubuntu-core- dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP: #1354318. It would be useful if users of 14.04 could install apport- noui and have crash reports automatically submitted for them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1431058/+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 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts
*** This bug is a duplicate of bug 1424466 *** https://bugs.launchpad.net/bugs/1424466 ** This bug has been marked a duplicate of bug 1424466 Devel package not installable in 14.04.2 (mesa-lts-utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1429529 Title: Package resolver can't find *-lts-utopic package dependencies, aborts Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html Guess APT just get overwhelmed by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1427344] Re: cups-browsed crashed with SIGSEGV in timeout_free()
Everyone who was able to rreproduce the crash with the old package, please test with the new package and tell us whether it solves the problem. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1427344 Title: cups-browsed crashed with SIGSEGV in timeout_free() Status in cups-filters package in Ubuntu: Fix Released Bug description: on every boot ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.66-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Mar 2 17:27:28 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-01-25 (35 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150125) Lpstat: device for HP-Photosmart-C3100-series: usb://HP/Photosmart%20C3100%20series?serial=MY6ABC32ND04P9interface=1 MachineType: ASUS All Series Papersize: a4 PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 3.14.6 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=a1f4e400-6d47-4810-8d22-d51139013aa1 ro resume=UUID=c756b5d8-0950-4dd7-8532-4932aac06078 quiet splash vga=845 SegvAnalysis: Segfault happened at: 0x7fdf8bc9a15a:movl $0x1,0xa8(%rax) PC (0x7fdf8bc9a15a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C 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.:bvr1802:bd01/28/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1427344/+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 1190344] Re: Daemon end of session/greeter pipes not closed
Hello rumen, or anyone else affected, Accepted lightdm into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lightdm (Ubuntu Utopic) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1190344 Title: Daemon end of session/greeter pipes not closed Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Committed Status in lightdm source package in Vivid: Fix Released Status in Fedora: Unknown Bug description: [Impact] LightDM doesn't close the server side end of the pipes used to communicate with session processes and greeters. This means each session/greeter that is created leaks two file descriptors eventually leading to the system stopping it from creating new pipes. [Test Case] 1. Start LightDM 2. Check how many pipes are open # lsof -p {lightdm_pid} | grep FIFO | wc -l 3. Create sessions by either cycling between users in Unity Greeter or logging in and out 4. Check how many pipes exist using step 2. Expected result: No more pipes should be open Observed result: Many pipes remain open [Regression Potential] Low. Fix is to close pipes when finished with them. Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190344/+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 678421] Re: Error message for a faulty ~/.profile script
Hello Egon, or anyone else affected, Accepted lightdm into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** 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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script Status in GDM: The Gnome Display Manager: New Status in gdm package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in gdm source package in Trusty: Fix Released Status in lightdm source package in Trusty: Fix Released Status in gdm source package in Utopic: Fix Released Status in lightdm source package in Utopic: Fix Committed Status in gdm package in Debian: New Bug description: trusty and utopic SRU requests == [Impact] In case of a syntax error in either of ~/.profile or a few other similar files, the Xorg login is interrupted, and the user is taken back to the login screen without an explanation. Debugging this problem may be a time consuming exercise, especially for non- experienced users. With the proposed change, lightdm/gdm does not try to load such a file, but shows a warning dialog instead. (A warning dialog is also shown in case of some other type of error, which would not have caused the login to fail.) [Test Case] To reproduce: * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis. * Log out and find that you can't log in to a graphical session. After installing the proposed lightdm/gdm version, you'll instead see the dialog and can log in. [Regression Potential] Since this is only about improved exception handling, it does not at all affect users with correct configuration files. The regression risk ought to be minimal. [Original description] Binary package hint: gdm After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile made the Xorg startup fail. (At that moment I had already forgotten the changes made to the .profile). As I had autologin that meant it kept trying to login and finally showed me the graphics reconfiguration screen. That sent me to a huge hunt for xorg conf and setup problems. Anyway finally tracked this down. I had used bash syntax in .profile file whereas it was run with sh. This is not a bug per se but I think a user mistake in .profile shouldn't bring the whole xorg startup to a halt as it does with autologin. I propose running user .profile and .xprofile scripts so that Xsession script continues running even if they have errors. I'm not sure whether this change would have some negative effects as well. 1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 i686 GNU/Linux 2) gdm 2.30.2.is.2.30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+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 1383321] Re: Support XDG DesktopNames field in session files
Hello Robert, or anyone else affected, Accepted lightdm into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1383321 Title: Support XDG DesktopNames field in session files Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Utopic: Fix Committed Status in lightdm source package in Vivid: Fix Released Bug description: [Impact] LightDM doesn't support the XDG standard DesktopNames field in session .desktop files. Instead we only support X-LightDM-DesktopName which was used before the standard was set. Newer sessions might expect DesktopNames to work. [Test Case] 1. Install a session which has DesktopNames set in /usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity; 2. Start this session Expected result: XDG_CURRENT_DESKTOP is set to GNOME:Unity Observed result: XDG_CURRENT_DESKTOP is not set [Regression Potential] Low. This feature is only activated if the field is set. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1383321/+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 1411100] Please test proposed package
Hello Schlomo, or anyone else affected, Accepted lightdm into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.10.5-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1411100 Title: Guest user not removed after guest session ends when using bash as default shell Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Committed Bug description: The /usr/sbin/giest-account script contains a bug which prevents the removal of guest accounts: $ sudo /usr/sbin/guest-account remove guest-Hhiook /usr/sbin/guest-account: line 129: UID: readonly variable Maybe this is related to /bin/sh actually beeing a Bash: $ ll -d /bin/sh lrwxrwxrwx 1 root root 4 Jan 1 01:44 /bin/sh - bash* But since using Bash as default sh is still a feature of Ubuntu, all scripts should work with both. Running the script with dash actually works: $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva umount: /tmp/guest-ZWCtva: mountpoint not found umount: /tmp/guest-ZWCtva: mountpoint not found Removing user `guest-ZWCtva' ... Warning: group `guest-ZWCtva' has no more members. Done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+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 1411100] Re: Guest user not removed after guest session ends when using bash as default shell
** Branch linked: lp:ubuntu/trusty-proposed/lightdm ** Branch linked: lp:ubuntu/utopic-proposed/lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1411100 Title: Guest user not removed after guest session ends when using bash as default shell Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Committed Bug description: The /usr/sbin/giest-account script contains a bug which prevents the removal of guest accounts: $ sudo /usr/sbin/guest-account remove guest-Hhiook /usr/sbin/guest-account: line 129: UID: readonly variable Maybe this is related to /bin/sh actually beeing a Bash: $ ll -d /bin/sh lrwxrwxrwx 1 root root 4 Jan 1 01:44 /bin/sh - bash* But since using Bash as default sh is still a feature of Ubuntu, all scripts should work with both. Running the script with dash actually works: $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva umount: /tmp/guest-ZWCtva: mountpoint not found umount: /tmp/guest-ZWCtva: mountpoint not found Removing user `guest-ZWCtva' ... Warning: group `guest-ZWCtva' has no more members. Done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+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 1190344] Re: Daemon end of session/greeter pipes not closed
Hello rumen, or anyone else affected, Accepted lightdm into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.10.5-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lightdm (Ubuntu Trusty) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1190344 Title: Daemon end of session/greeter pipes not closed Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Committed Status in lightdm source package in Vivid: Fix Released Status in Fedora: Unknown Bug description: [Impact] LightDM doesn't close the server side end of the pipes used to communicate with session processes and greeters. This means each session/greeter that is created leaks two file descriptors eventually leading to the system stopping it from creating new pipes. [Test Case] 1. Start LightDM 2. Check how many pipes are open # lsof -p {lightdm_pid} | grep FIFO | wc -l 3. Create sessions by either cycling between users in Unity Greeter or logging in and out 4. Check how many pipes exist using step 2. Expected result: No more pipes should be open Observed result: Many pipes remain open [Regression Potential] Low. Fix is to close pipes when finished with them. Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190344/+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 778054] Re: Packages shouldn't depend on the transitional package python-gobject
Hello Fred, or anyone else affected, Accepted zeitgeist into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zeitgeist/0.9.14-0ubuntu4.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: zeitgeist (Ubuntu Trusty) Status: In Progress = Fix Committed ** 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 gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/778054 Title: Packages shouldn't depend on the transitional package python-gobject Status in aptdaemon package in Ubuntu: Fix Released Status in desktopcouch package in Ubuntu: Invalid Status in eglibc package in Ubuntu: Invalid Status in gnome-utils package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Status in system-config-printer package in Ubuntu: Fix Released Status in wine1.4 package in Ubuntu: Fix Released Status in zeitgeist package in Ubuntu: Fix Released Status in aptdaemon source package in Trusty: Fix Released Status in desktopcouch source package in Trusty: Invalid Status in eglibc source package in Trusty: Invalid Status in gnome-utils source package in Trusty: Invalid Status in libreoffice source package in Trusty: Fix Released Status in openoffice.org source package in Trusty: Invalid Status in system-config-printer source package in Trusty: Fix Released Status in wine1.4 source package in Trusty: Invalid Status in zeitgeist source package in Trusty: Fix Committed Bug description: [Impact] python-zeitgeist depends on python-gobject, which means python-gobject cannot be removed from the system. python-gobject is a transitional package, and packages should be updated to no longer depend on it. [Test Case] * Install python-zeitgeist, and verify that python-gobject is not installed with it. * If it is already installed, you should be able to run 'apt-get purge python-gobject' without removing python-zeitgeist. [Regression Potential] Negligible. There are no code changes. The fix only removes a dependency on a transitional package that doesn't provide any files. --- [Impact] system-config-printer-gnome depends on python-gobject, which means python-gobject cannot be removed from the system. python-gobject is a transitional package, and packages should be updated to no longer depend on it. [Test Case] * Install system-config-printer-gnome, and verify that python-gobject is not installed with it. * If it is already installed, you should be able to run 'apt-get purge python-gobject' without removing system-config-printer-gnome. [Regression Potential] Negligible. There are no code changes. The fix only removes a dependency on a transitional package that doesn't provide any files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+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 1429771] Re: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-menus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1429771 Title: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: Confirmed Bug description: During apt-get dist-upgrade, after reboot, this popped out. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: gnome-menus 3.10.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Mon Mar 9 09:05:09 2015 DuplicateSignature: package:gnome-menus:3.10.1-0ubuntu5:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-06-20 (626 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: gnome-menus Title: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2013-11-10 (483 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1429771/+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 445333] Re: remember password on printing to windows printers does not work
** Branch linked: lp:ubuntu/trusty-proposed/gtk+2.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/445333 Title: remember password on printing to windows printers does not work Status in GTK+ GUI Toolkit: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Trusty: Fix Committed Status in gtk+3.0 source package in Trusty: Fix Released Bug description: [Impact] * Passwords for printers are not stored and the users are required to retype it with every print job for password protected printers [Test Case] * Configure a remote (shared via SMB), password-protected printer. * Request a print job. * Each subsequent job will require retyping the password. [Regression Potential] * Cherry-pick from upstream (present in Gtk+3.13.8). * Minor conflict resolution needed (line numbers changed) [Other Info] * Original bug description: i am printing from my ubuntu karmic to a windows box. everytime i print i get asked to input username and password to windows box, then the document gets printed. there is a remember password checkbox, but it keeps asking me when printing the next document. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/445333/+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 1159821] Re: Menus of a time set to 12:00:00 are initialised at 00:00:00
** Changed in: shotwell Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1159821 Title: Menus of a time set to 12:00:00 are initialised at 00:00:00 Status in Shotwell: Fix Released Status in shotwell package in Ubuntu: Confirmed Bug description: 1. Select any .jpeg file 2. Photos Adjust Date and Time... 3. Set it to 12:00:00 with 24hrs and click OK 4. Photos Adjust Date and Time... What you should see : the +/- menus should be set at 12:00:00 - 24hrs What you do see : 00:00:00 - 24hrs However, the information recorded seems correct as you see in the left side : Original: 03/25/2013, 12:00:00 (see screenshot attached) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: shotwell 0.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic i686 ApportVersion: 2.9.2-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Mon Mar 25 14:37:30 2013 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130325) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1159821/+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 1431083] Re: soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()
*** This bug is a duplicate of bug 1418551 *** https://bugs.launchpad.net/bugs/1418551 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 #1418551, 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/1431083/+attachment/4342084/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1431083/+attachment/4342086/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1431083/+attachment/4342088/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1431083/+attachment/4342089/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1431083/+attachment/4342090/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1431083/+attachment/4342091/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1431083/+attachment/4342092/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1418551 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1431083 Title: soffice.bin crashed with SIGSEGV in Application::GetSolarMutex() Status in libreoffice package in Ubuntu: New Bug description: Happened while closing a spreadsheet. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: libreoffice-core 1:4.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Mar 12 00:27:24 2015 EcryptfsInUse: Yes ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-05-05 (310 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/$somefile --splash-pipe=5 SegvAnalysis: Segfault happened at: 0x7fbc328f932a _ZN11Application13GetSolarMutexEv+10: mov0x8(%rax),%rdi PC (0x7fbc328f932a) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: Application::GetSolarMutex() () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /lib/x86_64-linux-gnu/libc.so.6 Title: soffice.bin crashed with SIGSEGV in Application::GetSolarMutex() UpgradeStatus: Upgraded to vivid on 2015-03-06 (5 days ago) UserGroups: bumblebee cdrom lpadmin plugdev sambashare sudo vboxusers wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1431083/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Well, in respect to what I see in the nVidia drivers (nvidia-opencl- icd-331-updates) and in the AMD drivers, shouldn't there be an enhances line (Enhances libopencl1) - the AMD driver is afterall providing enhancements, but in it's base package as opposed to a seperate opencl pacakge... -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Sorry for pointing that out - I just want to see this fixed right the first time -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 474514] Re: Banshee very slow when interacting with track lists
Eesh, sorry Chow, I wasn't subscribed to notifications for this! Done now - run debug script, found a file with an errant tag, edited tag, saved, waited for CPU to drop, quit banshee, pasted all terminal to text file, attached. ** Attachment added: terminal debug output https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/474514/+attachment/4342128/+files/BansheeHighCPU.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/474514 Title: Banshee very slow when interacting with track lists Status in banshee package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Invalid Status in banshee package in Debian: Invalid Status in sqlite3 package in Debian: Invalid Bug description: Binary package hint: banshee Banshee's great, but since I've added a few more songs it's become unbearably slow. Scrolling up and down the library is ok, provided it's settled for a while, However, whenever a song finishes playing or I rate a track or skip a track there's a delay whist 2 of my 8 CPU cores are maxed out. The UI takes an age to redraw or respond to clicks. The delay can be just half a second, or sometimes around 5. This usually coincides with some network activity. It makes interacting with the application nearly unbearable. Don't want to go back to Rhythmbox, but might have to :( I have: * Banshee 1.6 Beta 2 (1.5.1) * about 5,300 songs in the library * Ubuntu 9.10 Karmic 64bit * 6Gb of memory and an i7 920 processor Banshee extensions running: * Audio CD Support * Bookmarks * Cover Art Fetching * DAAP * Digital Media Player Support * IPod Support * Karma Support * Mass Storage Media Player Support * MTP Media Player Support * File System Queue * Internet Radio * Last.fm Radio Scrobbling * Multimedia Keys * Play Queue * Importers for Amarok Rhythmbox * Podcasts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/474514/+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 445333] Re: remember password on printing to windows printers does not work
Hello segler, or anyone else affected, Accepted gtk+2.0 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.23-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gtk+2.0 (Ubuntu Trusty) Status: In Progress = Fix Committed ** 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 gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/445333 Title: remember password on printing to windows printers does not work Status in GTK+ GUI Toolkit: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Trusty: Fix Committed Status in gtk+3.0 source package in Trusty: Fix Released Bug description: [Impact] * Passwords for printers are not stored and the users are required to retype it with every print job for password protected printers [Test Case] * Configure a remote (shared via SMB), password-protected printer. * Request a print job. * Each subsequent job will require retyping the password. [Regression Potential] * Cherry-pick from upstream (present in Gtk+3.13.8). * Minor conflict resolution needed (line numbers changed) [Other Info] * Original bug description: i am printing from my ubuntu karmic to a windows box. everytime i print i get asked to input username and password to windows box, then the document gets printed. there is a remember password checkbox, but it keeps asking me when printing the next document. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/445333/+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 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()
** Branch linked: lp:ubuntu/precise-proposed/lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1235915 Title: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server() Status in Light Display Manager: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in Light Display Manager 1.4 series: Fix Committed Status in Light Display Manager 1.8 series: Fix Committed Status in indicator-keyboard package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Bug description: The bug report details have been generated automatically. I'm not sure if this bug happens with lightdm or later on. The System Problem Detected dialogue box appears about 15 to 20 seconds after I've logged in (without me running any apps), so it could be that the crash occurs in the lightdm log-in screen but it just takes my system a while to collect the bug info? Everything appears to work normally after the System Problem Detected dialogue, so whatever is crashing seems to restart gracefully. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 11:15:17 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service InstallationDate: Installed on 2013-09-28 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk --use-bamf ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax PC (0x7fa5a9482616) ok source 0x18(%rdx) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-keyboard StacktraceTop: ?? () from /usr/lib/libxklavier.so.16 lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0 lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0 ?? () ?? () Title: indicator-keyboard-service crashed with SIGSEGV in lightdm_get_layouts() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1235915/+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 1431068] [NEW] fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build
Public bug reported: I run Ubuntu 14.04.2 LTS Cinnamon desktop x64, just upgraded my linux kernel to 3.19, via: cd /tmp/ + wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb + wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900_3.19.0-031900.201502091451_all.deb + wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-image-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb + sudo dpkg -i linux-headers-3.19.0-*.deb linux-image-3.19.0-*.deb + sudo reboot The problem I have was reported automatically by my system. So far, I haven't noticed any malfunctions myself... ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-updates 2:13.350.1-0ubuntu2 Uname: Linux 3.19.0-031900-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 3.19.0-031900-generic Date: Thu Mar 12 01:11:58 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-47-generic, x86_64: installed DuplicateSignature: dkms:fglrx-updates:2:13.350.1-0ubuntu2:/var/lib/dkms/fglrx-updates/13.350.1/build/2.6.x/firegl_public.c:4733:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration] GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05ee] Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M] [1002:6821] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05ee] InstallationDate: Installed on 2014-08-09 (214 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) LightdmGreeterLog: (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed LightdmGreeterLogOld: (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed MachineType: Dell Inc. Inspiron 3737 PackageVersion: 2:13.350.1-0ubuntu2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic root=UUID=c18e6c5b-cc8a-40d3-98fe-f9721bd79aab ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer-updates Title: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0HF1CD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3737:pvrA08:rvnDellInc.:rn0HF1CD:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3737 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Mar 12 01:13:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5534 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages 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/1431068 Title: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build Status in
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Trusty was affected too by the Conflicts: thing; I've been running manually-patched fglrx drivers for a while now. -- 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/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1371091] Re: [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in intel_crtc_wait_for_pending_flips()
This error was repeated on me a few times with the same situation: I watched a movie on the site nttp: //kinogo.net in Google Chrome and Xorg freezes after about 30 minutes of viewing My notebook: msi gs 70 2pc (core I7, nvidia gtx 860) Ubuntu 14.10 Amd64 syslog: Mar 12 05:23:54 xxx kernel: [58769.840122] [ cut here ] Mar 12 05:23:54 xxx kernel: [58769.840188] WARNING: CPU: 0 PID: 1472 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() Mar 12 05:23:54 xxx kernel: [58769.840191] Modules linked in: alx mdio ctr ccm bbswitch(OE) bnep rfcomm dm_crypt nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mxm_wmi msi_wmi sparse_keymap snd_hda_intel snd_hda_controller intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 snd_hda_codec kvm snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi ath9k aes_x86_64 lrw gf128mul glue_helper ath9k_common ablk_helper cryptd ath9k_hw snd_seq joydev ath serio_raw ath3k mac80211 btusb bluetooth 6lowpan_iphc snd_seq_device snd_timer cfg80211 snd mei_me lpc_ich mei shpchp soundcore wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci drm libahci video [last unloaded: mdio] Mar 12 05:23:54 xxx kernel: [58769.840268] CPU: 0 PID: 1472 Comm: Xorg Tainted: P OE 3.16.0-31-generic #41-Ubuntu Mar 12 05:23:54 xxx kernel: [58769.840272] Hardware name: Micro-Star International Co., Ltd. GS70 2PC Stealth/MS-1772, BIOS E1772IMS.10C 10/21/2014 Mar 12 05:23:54 xxx kernel: [58769.840274] 0009 880221677c18 82782d0b Mar 12 05:23:54 xxx kernel: [58769.840280] 880221677c50 8206ff2d 880223883000 Mar 12 05:23:54 xxx kernel: [58769.840285] 88021fd98210 8802238eb800 8802238eb800 880221677c60 Mar 12 05:23:54 xxx kernel: [58769.840290] Call Trace: Mar 12 05:23:54 xxx kernel: [58769.840303] [82782d0b] dump_stack+0x45/0x56 Mar 12 05:23:54 xxx kernel: [58769.840312] [8206ff2d] warn_slowpath_common+0x7d/0xa0 Mar 12 05:23:54 xxx kernel: [58769.840318] [8207000a] warn_slowpath_null+0x1a/0x20 Mar 12 05:23:54 xxx kernel: [58769.840350] [c03b813c] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] Mar 12 05:23:54 xxx kernel: [58769.840360] [820b97b0] ? prepare_to_wait_event+0x100/0x100 Mar 12 05:23:54 xxx kernel: [58769.840391] [c03bac03] intel_crtc_disable_planes+0x33/0x1c0 [i915] Mar 12 05:23:54 xxx kernel: [58769.840396] [82787e9b] ? __ww_mutex_lock+0x1b/0xb0 Mar 12 05:23:54 xxx kernel: [58769.840426] [c03bbb47] haswell_crtc_disable+0x57/0x2d0 [i915] Mar 12 05:23:54 xxx kernel: [58769.840431] [82788af2] ? mutex_lock+0x12/0x30 Mar 12 05:23:54 xxx kernel: [58769.840462] [c03bc577] intel_crtc_update_dpms+0x67/0xa0 [i915] Mar 12 05:23:54 xxx kernel: [58769.840494] [c03c0c09] intel_connector_dpms+0x59/0x70 [i915] Mar 12 05:23:54 xxx kernel: [58769.840524] [c02e2e19] drm_mode_obj_set_property_ioctl+0x399/0x3a0 [drm] Mar 12 05:23:54 xxx kernel: [58769.840547] [c02e2e50] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] Mar 12 05:23:54 xxx kernel: [58769.840563] [c02d1a4f] drm_ioctl+0x1df/0x680 [drm] Mar 12 05:23:54 xxx kernel: [58769.840572] [8241770e] ? brightness_store+0xce/0x100 Mar 12 05:23:54 xxx kernel: [58769.840578] [822205ac] ? fsnotify+0x27c/0x350 Mar 12 05:23:54 xxx kernel: [58769.840584] [821f5658] do_vfs_ioctl+0x2c8/0x4a0 Mar 12 05:23:54 xxx kernel: [58769.840589] [821e3b51] ? __sb_end_write+0x31/0x60 Mar 12 05:23:54 xxx kernel: [58769.840594] [821f58b1] SyS_ioctl+0x81/0xa0 Mar 12 05:23:54 xxx kernel: [58769.840600] [8278ad2d] system_call_fastpath+0x1a/0x1f Mar 12 05:23:54 xxx kernel: [58769.840603] ---[ end trace 395e59291d098358 ]--- Mar 12 05:24:06 xxx kernel: [58781.198023] Watchdog[14435]: segfault at 0 ip 7ff20080e476 sp 7ff1f08b66a0 error 6 in chrome[7ff1fc92+5154000] Mar 12 05:24:16 xxx kernel: [58791.474004] Watchdog[23452]: segfault at 0 ip 7f7a0fe44476 sp 7f79ffeec6a0 error 6 in chrome[7f7a0bf56000+5154000] dmesg in attachment What other information to provide? -- 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/1371091 Title: [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in intel_crtc_wait_for_pending_flips() Status in xorg-server package in Ubuntu: Confirmed Bug description: GPU gets stuck. Frequently after wakeup from sleep, but also during normal run. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.16.0-1ubuntu1
[Desktop-packages] [Bug 1411100] Re: Guest user not removed after guest session ends when using bash as default shell
Hello Schlomo, or anyone else affected, Accepted lightdm into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1411100 Title: Guest user not removed after guest session ends when using bash as default shell Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Committed Bug description: The /usr/sbin/giest-account script contains a bug which prevents the removal of guest accounts: $ sudo /usr/sbin/guest-account remove guest-Hhiook /usr/sbin/guest-account: line 129: UID: readonly variable Maybe this is related to /bin/sh actually beeing a Bash: $ ll -d /bin/sh lrwxrwxrwx 1 root root 4 Jan 1 01:44 /bin/sh - bash* But since using Bash as default sh is still a feature of Ubuntu, all scripts should work with both. Running the script with dash actually works: $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva umount: /tmp/guest-ZWCtva: mountpoint not found umount: /tmp/guest-ZWCtva: mountpoint not found Removing user `guest-ZWCtva' ... Warning: group `guest-ZWCtva' has no more members. Done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+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 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
Hello Doug, or anyone else affected, Accepted mesa into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/10.1.3-0ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed ** Package changed: freeglut (Ubuntu) = mesa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freeglut in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Confirmed Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev 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: 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 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 1431058] [NEW] Stable Release Update to provide possiblity of automatically reporting crashes
Public bug reported: The version of apport in Ubuntu 14.04 is missing a few changes that would allow users to install apport-noui and allow crash reports to be submitted automatically from systems with it installed. The changes are the following: * debian/apport-noui.upstart: remove early exit (LP: #1235436) * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436) * data/whoopsie-upload-all: backport utopic version of it * apport-noui: make the package installation automatically enable autosubmission, and update the package description accordingly. LP: #1351137. The changes to whoopsie-upload-all can be found in this revision (http://bazaar.launchpad.net/~ubuntu-core- dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP: #1354318. It would be useful if users of 14.04 could install apport- noui and have crash reports automatically submitted for them. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: apport (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1431058 Title: Stable Release Update to provide possiblity of automatically reporting crashes Status in apport package in Ubuntu: New Status in apport source package in Trusty: New Bug description: The version of apport in Ubuntu 14.04 is missing a few changes that would allow users to install apport-noui and allow crash reports to be submitted automatically from systems with it installed. The changes are the following: * debian/apport-noui.upstart: remove early exit (LP: #1235436) * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436) * data/whoopsie-upload-all: backport utopic version of it * apport-noui: make the package installation automatically enable autosubmission, and update the package description accordingly. LP: #1351137. The changes to whoopsie-upload-all can be found in this revision (http://bazaar.launchpad.net/~ubuntu-core- dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP: #1354318. It would be useful if users of 14.04 could install apport- noui and have crash reports automatically submitted for them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1431058/+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 1391024] Re: The prompt of Password Strength Meter hasn't been translated.
This bug was fixed in the package libpwquality - 1.2.3-1ubuntu1.1 --- libpwquality (1.2.3-1ubuntu1.1) trusty; urgency=medium * No change rebuild to get translations imported in launchpad (lp: #1391024) -- Sebastien Bacher seb...@ubuntu.com Fri, 06 Feb 2015 15:08:24 +0100 ** Changed in: libpwquality (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpwquality in Ubuntu. https://bugs.launchpad.net/bugs/1391024 Title: The prompt of Password Strength Meter hasn't been translated. Status in Ubuntu Translations: Fix Committed Status in Ubuntu Kylin: Fix Committed Status in libpwquality package in Ubuntu: Fix Released Status in libpwquality source package in Trusty: Fix Released Status in libpwquality source package in Utopic: Fix Released Bug description: * Impact the password meter hints from the user account settings are not translated * Test case - use unity7 with a non english locale - System settings-User Accounts-Unlock - Click password - place the mouse on the Password Strength Meter - the hint should be translated * Impact regression Shouldn't be one, there is no code change, it's only for launchpad import of the template --- 1. System settings-User Accounts-Unlock 2. Click password 3. place the mouse on the Password Strength Meter Failed- The prompt of Password Strength Meter hasn't been translated. Ubuntukylin-14.10-utopic; 32bit ;lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1391024/+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 1391024] Re: The prompt of Password Strength Meter hasn't been translated.
This bug was fixed in the package libpwquality - 1.2.3-1ubuntu1.2 --- libpwquality (1.2.3-1ubuntu1.2) utopic; urgency=medium * No change rebuild to get translations imported in launchpad (lp: #1391024) -- Sebastien Bacher seb...@ubuntu.com Fri, 06 Feb 2015 15:08:24 +0100 ** Changed in: libpwquality (Ubuntu Utopic) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpwquality in Ubuntu. https://bugs.launchpad.net/bugs/1391024 Title: The prompt of Password Strength Meter hasn't been translated. Status in Ubuntu Translations: Fix Committed Status in Ubuntu Kylin: Fix Committed Status in libpwquality package in Ubuntu: Fix Released Status in libpwquality source package in Trusty: Fix Released Status in libpwquality source package in Utopic: Fix Released Bug description: * Impact the password meter hints from the user account settings are not translated * Test case - use unity7 with a non english locale - System settings-User Accounts-Unlock - Click password - place the mouse on the Password Strength Meter - the hint should be translated * Impact regression Shouldn't be one, there is no code change, it's only for launchpad import of the template --- 1. System settings-User Accounts-Unlock 2. Click password 3. place the mouse on the Password Strength Meter Failed- The prompt of Password Strength Meter hasn't been translated. Ubuntukylin-14.10-utopic; 32bit ;lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1391024/+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 1412036] Re: Korean typing doesn't work
@Aron: The bug description may not be crystal clear, neither in this bug report nor the upstream ditto, but I for one can reproduce the problem. ibus-hangul simply does not work in Utopic and Vivid. Using 14.10 I can make it work by downgading to ibus-hangul 1.4.2-3 (the trusty version). ** Changed in: ibus-hangul (Ubuntu) Status: Invalid = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-hangul in Ubuntu. https://bugs.launchpad.net/bugs/1412036 Title: Korean typing doesn't work Status in IBus: Unknown Status in ibus-hangul package in Ubuntu: Triaged Bug description: At the moment I have got Russian and English (UK) installed on my computer. I installed them through System Settings Language Support. But now I want to add Korean and that is where the problem has come up. So I go into the Language Support settings and click Install / Remove Languages..., I then select Korean from the list and click Apply Changes. After the installation has finished I go into the Text Entry settings: Text_Entry_GUI.bmp And click the little + sign. Then I find and add Korean from the list: Choose_an_input_source_GUI.bmp But then when I select Korean as the language I want to type as, it still stays at English. And not matter what I do, I cannot seem to get any other languages working. I am running Ubuntu 14.10. Package information: ibus-hangul: Installed: 1.4.2+git20140818-1 Candidate: 1.4.2+git20140818-1 Version table: *** 1.4.2+git20140818-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1412036/+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 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
Tested with -proposed enabled a number of apt-get sims, all looked good. freeglut3-dev libglew-dev libsdl1.2-dev libsdl2-dev So will mark verification-done dupe related bugs that will be fixed. There still are a few cases open, one is obscure enough not to warrant a look? (osmesa is not built in the hwe mesa), others may need to be adjusted in the sources (like fglrx-updates, ect. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Confirmed Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev 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: 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 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 539467] Re: SATA link power management causes disk errors and corruption
Uninstalling the tlp package resolved this issue for me (Ubuntu 14.04). Disabling laptop_mode also seemed to help: echo 0 /proc/sys/vm/laptop_mode -- 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/539467 Title: SATA link power management causes disk errors and corruption Status in The Linux Kernel: Expired Status in linux package in Ubuntu: Invalid Status in pm-utils package in Ubuntu: Fix Released Status in pm-utils-powersave-policy package in Ubuntu: Invalid Status in linux source package in Lucid: Won't Fix Status in pm-utils source package in Lucid: Invalid Status in pm-utils-powersave-policy source package in Lucid: Fix Released Status in linux source package in Maverick: Invalid Status in pm-utils source package in Maverick: Invalid Status in pm-utils-powersave-policy source package in Maverick: Invalid Status in linux source package in Natty: Invalid Status in pm-utils source package in Natty: Fix Released Status in pm-utils-powersave-policy source package in Natty: Invalid Bug description: SRU Justification for pm-utils-powersave-policy: Impact: On certain hardware, enabling power saving for the SATA link can cause data corruption. How Addressed: The proposed branch removes the sata link power policy script. This will cause the link to be maintained at the normal power usage instead of dropping when the power is removed from the machine. Reproduction: On an affected machine, unplug and plug in the power a few times. Data corruption will result. Regression Potential: Removing the script will cause the SATA link to stay fully powered at all times. This may cause an increase in the battery usage for some machines. There should be no functionality regressions or bugs introduced by this change. = Using Lucid on my laptop, I see errors like this in dmesg quite frequently (every few hours): Mar 14 23:00:09 chris-laptop kernel: [42987.460608] ata1.00: exception Emask 0x10 SAct 0x1 SErr 0x5 action 0xe frozen Mar 14 23:00:09 chris-laptop kernel: [42987.460618] ata1.00: irq_stat 0x0040, PHY RDY changed Mar 14 23:00:09 chris-laptop kernel: [42987.460627] ata1: SError: { PHYRdyChg CommWake } Mar 14 23:00:09 chris-laptop kernel: [42987.460635] ata1.00: failed command: READ FPDMA QUEUED Mar 14 23:00:09 chris-laptop kernel: [42987.460649] ata1.00: cmd 60/08:00:97:23:44/00:00:01:00:00/40 tag 0 ncq 4096 in Mar 14 23:00:09 chris-laptop kernel: [42987.460652] res 40/00:04:97:23:44/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Mar 14 23:00:09 chris-laptop kernel: [42987.460669] ata1.00: status: { DRDY } Mar 14 23:00:09 chris-laptop kernel: [42987.460681] ata1: hard resetting link Mar 14 23:00:09 chris-laptop kernel: [42987.523336] ata2: exception Emask 0x10 SAct 0x0 SErr 0x5 action 0xe frozen Mar 14 23:00:09 chris-laptop kernel: [42987.523346] ata2: irq_stat 0x0040, PHY RDY changed Mar 14 23:00:09 chris-laptop kernel: [42987.523355] ata2: SError: { PHYRdyChg CommWake } Mar 14 23:00:09 chris-laptop kernel: [42987.523368] ata2: hard resetting link Mar 14 23:00:09 chris-laptop kernel: [42988.202586] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 14 23:00:09 chris-laptop kernel: [42988.205443] ata1.00: configured for UDMA/133 Mar 14 23:00:09 chris-laptop kernel: [42988.205459] ata1: EH complete Mar 14 23:00:09 chris-laptop kernel: [42988.280089] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Mar 14 23:00:09 chris-laptop kernel: [42988.285567] ata2.00: configured for UDMA/100 Mar 14 23:00:09 chris-laptop kernel: [42988.289370] ata2: EH complete Every couple of days, this results in data corruption and my filesystem being remounted read-only: [ 6148.305806] Aborting journal on device sda1-8. [ 6148.325011] EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal [ 6148.325018] EXT4-fs (sda1): Remounting filesystem read-only [ 6148.326702] journal commit I/O error [ 6148.330975] EXT4-fs error (device sda1) in ext4_reserve_inode_write: Journal has aborted [ 6148.462572] __ratelimit: 15 callbacks suppressed Those messages generally appear at the end of dmesg after the event, just after the hard resetting link message. I then have to boot a live CD and manually run fsck, as I can no longer boot the laptop. This is happening every couple of days generally, although it happened 3 times in one day last Thursday. I did contemplate it being a hardware issue, but I tried running the kernel from Karmic for a couple of days, and that worked ok without a single error message ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chr1s 4010 F pulseaudio
[Desktop-packages] [Bug 1371091] Re: [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in intel_crtc_wait_for_pending_flips()
** Attachment added: dmesg by faunris https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1371091/+attachment/4342129/+files/dmesg -- 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/1371091 Title: [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in intel_crtc_wait_for_pending_flips() Status in xorg-server package in Ubuntu: Confirmed Bug description: GPU gets stuck. Frequently after wakeup from sleep, but also during normal run. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.16.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Thu Sep 18 06:00:32 2014 DistUpgraded: 2014-09-12 07:00:32,485 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.14, 3.16.0-14-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-08-08 (41 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. XPS13 9333 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=8a50e235-2691-4a4a-b587-3bb79f18c59c ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to utopic on 2014-09-12 (5 days ago) UserGroups: dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 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~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Sep 18 06:06:44 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1371091/+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 1341309] Re: [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in Chromium
Hi, I had same issue as described above. I'm happy to report that my problem has been fixed by applying following update per https://bugs.freedesktop.org/show_bug.cgi?id=80568#c99 on the latest kernel release. YMMV. sudo apt-add-repository ppa:xorg-edgers/ppa sudo apt-get update sudo apt-get dist-upgrade dpkg -l libgl1-mesa-dri sudo reboot ** Bug watch added: freedesktop.org Bugzilla #80568 https://bugs.freedesktop.org/show_bug.cgi?id=80568 -- 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/1341309 Title: [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in Chromium Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Chromiun browsing an italian webmail (libero: inwind.it, libero.it, etc. accounts), logon done, using any comand or cheking boxes, system crash in a black screeen (some hd activity's left) or start an about 1 second intermitting screen aspect (few icons, then none, again few icons, then none, etc., in the desktop screen aspect). In both case hard drastic reboot is necessary. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.13.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 Chipset: i965gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 13 15:55:33 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DuplicateSignature: [i965gm] GPU lockup IPEHR: 0x60020100 Ubuntu 14.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:011f] Subsystem: Acer Incorporated [ALI] Device [1025:011f] InstallationDate: Installed on 2014-06-02 (40 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) InterpreterPath: /usr/bin/python3.4 MachineType: Acer Extensa 5620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic root=UUID=6f5ce81b-5a89-4c62-b14d-695a51e7c561 ro quiet splash RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.54-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [i965gm] GPU lockup IPEHR: 0x60020100 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.34 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd04/15/2008:svnAcer:pnExtensa5620:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5620 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 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-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jul 13 16:48:30 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 32884 vendor AUO xserver.version: 2:1.15.1-0ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1341309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :