[Desktop-packages] [Bug 1676002] [NEW] Xorg freeze
Public bug reported: The system freezes randomly since I installed Ubuntu 16.04. I think there's a problem with nvidia drivers. The graphic card is Nvidia GeForce 7050/NForce 610i. I use the nouveau driver. Before this I used Ubuntu 12.04 without problems for almost 5 years with 173 Nvidia driver (which it's recommended), but it's not avaliable. Now when I try to use privete drivers the only avaliable driver is Nvidia 304.xx, but it causes a black screen at start the PC. I can use the terminal to uninstall the nvidia drivers and login, but then the system freezes very frecuently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: 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: Sat Mar 25 08:11:57 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C73 [GeForce 7050 / nForce 610i] [1043:82ae] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=5edf19ce-c17b-4661-bfff-4b32af86a9e4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N73-AM ACPI BIOS Revision 0201 dmi.board.name: P5N73-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.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:bvrASUSP5N73-AMACPIBIOSRevision0201:bd06/11/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N73-AM:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 08:05:47 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 ubuntu xenial -- 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/1676002 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: The system freezes randomly since I installed Ubuntu 16.04. I think there's a problem with nvidia drivers. The graphic card is Nvidia GeForce 7050/NForce 610i. I use the nouveau driver. Before this I used Ubuntu 12.04 without problems for almost 5 years with 173 Nvidia driv
[Desktop-packages] [Bug 1675984] Re: package firefox 51.0.1+build2-0ubuntu0.16.04.2 failed to install/upgrade: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de erro 2
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: fsys-tarfile-error ** 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/1675984 Title: package firefox 51.0.1+build2-0ubuntu0.16.04.2 failed to install/upgrade: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de erro 2 Status in firefox package in Ubuntu: Invalid Bug description: i dont think is this problem stay make a ubuntu, i think mabe is this problem stay an last upgrade this firefox. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: firefox 51.0.1+build2-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabricio 2428 F pulseaudio /dev/snd/controlC1: fabricio 2428 F pulseaudio BuildID: 20170201180315 Channel: Unavailable Date: Tue Mar 21 20:13:19 2017 ErrorMessage: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de erro 2 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-02 (50 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.0.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.113 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 51.0.1+build2-0ubuntu0.16.04.2 failed to install/upgrade: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de erro 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.28 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 5740 dmi.board.vendor: Acer dmi.board.version: V1.28 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd08/12/2010:svnAcer:pnAspire5740:pvrV1.28:rvnAcer:rnAspire5740:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.name: Aspire 5740 dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1675984/+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 1676007] [NEW] package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned erro
Public bug reported: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quiet splash vt.handoff=7 SourcePackage: libxrandr Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RCK3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/18/2015:svnDellInc.:pnLatitude3450:pvr:rvnDellInc.:rn0RCK3X:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 09:44:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.1-0ubuntu3~trusty1 ** Affects: libxrandr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1676007 Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 Status in libxrandr package in Ubuntu: New Bug description: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quiet splash vt.
[Desktop-packages] [Bug 1676007] Re: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1676007 Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 Status in libxrandr package in Ubuntu: New Bug description: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quiet splash vt.handoff=7 SourcePackage: libxrandr Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RCK3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/18/2015:svnDellInc.:pnLatitude3450:pvr:rvnDellInc.:rn0RCK3X:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 09:44:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.1-0ubuntu3~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1676007/+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 1648183] Re: Crackling and popping sound when using headphones
Same issue on HP Pavilion x360 u003ng. (Sorry for German output) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio Liste der Hardware-Geräte (PLAYBACK) Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC295 Analog [ALC295 Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 8: HDMI 2 [HDMI 2] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1086019] Re: cupsd crashes regularly (daily)
all users can't print from libreoffice (oodt) files - only PDF printing works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in cups package in Ubuntu: Fix Released Status in cups-filters package in Ubuntu: Fix Released Status in cups source package in Quantal: Fix Released Status in cups-filters source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pv
[Desktop-packages] [Bug 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
I would recommend you try this staging PPA - https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging it brings the latest X stack - if it resolves your issues please report that fact here on the bug report tracking the request to bring this X stack to zesty: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: After enter password, it starts appearing top bar, dock and then the screen goes off followed by login screen. The system it's updated (full-upgrade) Ubuntu Budgie 17.04 (daily build) Budgie Desktop 10.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
(16.04): in the meantime the connection is not greyed out, but this does not mean that one can reliably use this to connect. Generally I have to suspend, re-awake and then use 'nmcli c up id *' to connect. A poor man's workaround for a defect which has existed for some time now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in Network Manager Applet: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1542733/+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 1671799] Re: FFe: xserver 1.19.3
Ot to FFe Bug filed regarding PRIME synchronization with hybrid hardware implemented via nvidia-prime Bug 1674304 -- 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/1671799 Title: FFe: xserver 1.19.3 Status in xorg-server package in Ubuntu: Confirmed Bug description: xserver 1.19 has been out for quite some time now. Debian Stretch will release with it, and xmir has been recently ported so we can push 1.19 to zesty now. It's currently being staged on a ppa: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging The main features of this release are: - PRIME synchronization support, should reduce tearing on hybrid setups - GLAMOR (2D accel over OpenGL) improvements - threaded input This bugreport is also for gathering testing feedback. Tested to be working fine on: - Intel Kabylake - Intel Broadwell - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers) - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M]) - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M]) - Radeon SI (radeon & amdgpu drivers) - qemu (QXL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Sorry if I missed this in your bug report, but what model Nvidia GPU are you testing? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: After enter password, it starts appearing top bar, dock and then the screen goes off followed by login screen. The system it's updated (full-upgrade) Ubuntu Budgie 17.04 (daily build) Budgie Desktop 10.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window
I am also affected. My plain Ubuntu does not recognize the tablet in the system settings, but I can use it. Same is in Kubuntu, with the little difference that I am able to see it as a joystick. -- 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/1575887 Title: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window Status in unity-control-center package in Ubuntu: Confirmed Bug description: The section in system configuration called "Wacom Tablet" isn't detecting my Wacom Intuos Art Small 2015, i'm using Ubuntu 16.04 with 4.4 kernel, i installed the drivers of linux wacom but the issue continue.I expected that ubuntu will detect the tablet and the wacom properties setting will work. INFO: Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887/+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 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window
Sry forgot to mention that I have the CTH-490. Sensitivity works in GIMP fine. -- 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/1575887 Title: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window Status in unity-control-center package in Ubuntu: Confirmed Bug description: The section in system configuration called "Wacom Tablet" isn't detecting my Wacom Intuos Art Small 2015, i'm using Ubuntu 16.04 with 4.4 kernel, i installed the drivers of linux wacom but the issue continue.I expected that ubuntu will detect the tablet and the wacom properties setting will work. INFO: Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887/+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 1676048] Re: unity-greeter crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1625282 *** https://bugs.launchpad.net/bugs/1625282 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 #1625282, 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/1676048/+attachment/4845635/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1676048/+attachment/4845637/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1676048/+attachment/4845639/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1676048/+attachment/4845640/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1676048/+attachment/4845641/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1676048/+attachment/4845642/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1676048/+attachment/4845643/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1625282 ** 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 unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1676048 Title: unity-greeter crashed with SIGABRT in g_assertion_message() Status in unity-greeter package in Ubuntu: New Bug description: desktop wallpaper appears. then login/passwd screen opens. I login. " " still there but no dash icons appear until I hit some combo of keys. I tried alt-tab or alt-qwerty to wake up desktop. remember Super-key? there a F1 a help box first boot only until a prog run. is it between left cntl and left alt? (win key??) win-l locks screen? win-e displays file explorer. win-m minimizes all to desktop. etc. Having a blank desktop or black screen really stops work! pianobar, netris, and nano in alt-cntl-1 virtual console let me work. I opened another bug when only a guest-cvx0 usr999 session would work. usr1000 alt-1 tty$ export DISPLAY=':0.0'; firefox& refused to work. New vmlinuz grub.cfg has >kernel but no >initrd image.lz !?! progress? /boot has a 7388kb vmlinuz-4.10.0-14-generic but no partner 42532kb initrd.img-4.10.0-13-generic. why does ubuntu-live-cd.iso boot with /boot/memdisk iso but not find append root=uuid=!@!$ or --find-iso=/boot/images/ubunt-desk.iso? and instead drop into (initram) ?? Try mounting /dev/sda4 /root then mount file.iso /cdrom All /isolinux files have no eXec bits set to exec isolinux.bin or exec vesamenu.c32 nogo! next I'll try mount /casper/fs.squash /mnt; chroot /mnt /sbin/init It's really bad when X is dead and win10 sucks so hard. Btw: why has grub-efi-2.02-beta3 refused to chainload /win10/win/EFI/winfw.efi? I added load /win10/other.efi files and they all had same fail to load mesg. I hit a key and win10 would load. now I have to F2 into bios and chose grub.efi or win10.efi ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: unity-greeter 17.04.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Fri Mar 24 00:24:41 2017 ExecutablePath: /usr/sbin/unity-greeter InstallationDate: Installed on 2016-12-18 (97 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161216) ProcCmdline: /usr/sbin/unity-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: unity-greeter StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: unity-greeter crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1676048/+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 1551022] Re: mouse pointer leaves trail
Regression in 16.04.2 this bug has come back. Using Intel i915 driver on a Intel J3160 processor. Connection is dual monitor VGA + HDMI What do you need qua logging or actions to solve this issue? ** Attachment added: "Mouse Pointer Trails" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+attachment/4845654/+files/MousePointerTrails.png -- 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/1551022 Title: mouse pointer leaves trail Status in xorg package in Ubuntu: Expired Bug description: In my desktop system Kubuntu 15.10 I have the integrated graphic card (Intel HD3000) and a discrete graphic card (Nvidia GTX 550). Some days ago I attached a monitor on the iGPU and enabled it, giving me a triple head system (two monitors on the Nvidia and one on the Intel). From that moment, the mouse pointer started to leave a trail when it pass over something that is animating. I'm using nouveau for the nvidia card. I tried to upgrade to Kubuntu 16.04, but it gives me the same glitch. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-02-24 01:06:09,804 DEBUG enabling apt cron job DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d] NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF116 [GeForce GTX 550 Ti] [19da:5194] InstallationDate: Installed on 2015-11-19 (106 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic root=UUID=679d8ad1-4664-4abd-a80a-3ac9339425bb ro quiet splash nomdmonddf nomdmonisw irqnodebug vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Tags: xenial ubuntu single-occurrence reproducible has-workaround Uname: Linux 4.4.0-10-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3707:bd07/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
My GPU is Nvidia GeForce 6150SE nForce 430 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 Notes: The system it's updated (full-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
** Description changed: - After enter password, it starts appearing top bar, dock and then the - screen goes off followed by login screen. + Nvidia 304 graphics kills budgie-window manager process and causes login + loop in Ubuntu Budgie. + + Steps: + - Enter password + - System shows top bar (half cropped) + - Sometimes dock appears + - Screen goes off (with no signal in monitor) + - Screen shows login screen again + + + System description: + - OS: Ubuntu Budgie 17.04 (daily build) + - GPU: Nvidia GeForce 6150SE nForce 430 + + + Packages: + - Budgie Desktop 10.2.9 + - Nvidia Graphics Drivers 304 + + + Notes: The system it's updated (full-upgrade) - - Ubuntu Budgie 17.04 (daily build) - Budgie Desktop 10.2.9 ** Description changed: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. - Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again - System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 - Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 - Notes: The system it's updated (full-upgrade) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 Notes: The system it's updated (full-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1514544] Re: always set "xkb, us" despite set of other layout when input-sources is empty
** Description changed:
When input-sources is empty, unity-settings-daemon try to fill
input-sources/sources by DEFAULT_LAYOUT at get_sources_from_xkb_config().
Please use DEFAULT_LAYOUT only when doesn't other keyboard layout.
How to reproduce:
1. set xkb layout other than us layout
$ setxkbmap -layout jp
2. clear settings
$ gsettings set org.gnome.desktop.input-sources sources "@as []"
3. restart unity-settings-daemon
- $ restart unity-settings-daemon
- unity-settings-daemon start/running, process 13518
+ $ systemctl --user restart unity-settings-daemon.servic
Expected result:
xkb,jp layout and input method settings
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'jp'), ('fcitx', 'mozc')]
Actual result:
xkb,us is always inserted.
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'jp'), ('xkb', 'us'), ('ibus', 'anthy')]
** Branch linked: lp:~cosmos-door/unity-settings-daemon/lp1514544-zesty
** Branch unlinked: lp:~cosmos-door/unity-settings-daemon/lp1514544
--
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/1514544
Title:
always set "xkb,us" despite set of other layout when input-sources is
empty
Status in unity-settings-daemon package in Ubuntu:
Confirmed
Bug description:
When input-sources is empty, unity-settings-daemon try to fill
input-sources/sources by DEFAULT_LAYOUT at get_sources_from_xkb_config().
Please use DEFAULT_LAYOUT only when doesn't other keyboard layout.
How to reproduce:
1. set xkb layout other than us layout
$ setxkbmap -layout jp
2. clear settings
$ gsettings set org.gnome.desktop.input-sources sources "@as []"
3. restart unity-settings-daemon
$ systemctl --user restart unity-settings-daemon.servic
Expected result:
xkb,jp layout and input method settings
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'jp'), ('fcitx', 'mozc')]
Actual result:
xkb,us is always inserted.
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'jp'), ('xkb', 'us'), ('ibus', 'anthy')]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1514544/+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 1514544] Re: always set "xkb, us" despite set of other layout when input-sources is empty
Hi Sebastien and William,
After a long time, finally, I made new patch and sent merge request.
Based on the advice pointed out by Sebastien, all locale except "ja_JP",
add "us" layout as default keyboard layout. "ja_JP" locale (and added
locale to locale_layout array) use layout variable in locale_layout
array as default keyboard layout.
Could you review it?
** Changed in: unity-settings-daemon (Ubuntu)
Status: In Progress => Confirmed
--
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/1514544
Title:
always set "xkb,us" despite set of other layout when input-sources is
empty
Status in unity-settings-daemon package in Ubuntu:
Confirmed
Bug description:
When input-sources is empty, unity-settings-daemon try to fill
input-sources/sources by DEFAULT_LAYOUT at get_sources_from_xkb_config().
Please use DEFAULT_LAYOUT only when doesn't other keyboard layout.
How to reproduce:
1. set xkb layout other than us layout
$ setxkbmap -layout jp
2. clear settings
$ gsettings set org.gnome.desktop.input-sources sources "@as []"
3. restart unity-settings-daemon
$ systemctl --user restart unity-settings-daemon.servic
Expected result:
xkb,jp layout and input method settings
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'jp'), ('fcitx', 'mozc')]
Actual result:
xkb,us is always inserted.
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'jp'), ('xkb', 'us'), ('ibus', 'anthy')]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1514544/+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 1674677] Re: eglGetDisplay(EGL_DEFAULT_DISPLAY) returns EGL_NO_DISPLAY
Pull request here: https://github.com/tseliot/nvidia-graphics-
drivers/pull/9
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1674677
Title:
eglGetDisplay(EGL_DEFAULT_DISPLAY) returns EGL_NO_DISPLAY
Status in nvidia-graphics-drivers-367 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
Confirmed
Bug description:
I am using EGL to obtain offscreen rendering contexts, but upgrading
this package today broke my application. I have written a small test
case, that I expect to print "PASS":
```
#include
#include
int main(int argc, char **argv) {
EGLDisplay eglDpy = eglGetDisplay(EGL_DEFAULT_DISPLAY);
std::cout << ((eglDpy == EGL_NO_DISPLAY) ? "FAIL" : "PASS") << std::endl;
}
```
Build with e.g. `g++ egl_test.cpp -lEGL`. Using nvidia-375
(375.39-0ubuntu0.16.04.1), this test program will print "FAIL",
because `eglGetDisplay(EGL_DEFAULT_DISPLAY)` returns `EGL_NO_DISPLAY`.
If I install the 375.39 driver using Nvidia's installer, the test
passes, so I think it is not an upstream issue.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nvidia-375 375.39-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Mar 21 12:41:31 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-11 (160 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: nvidia-graphics-drivers-375
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1674677/+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 1328301] Fw: plans for the summer
Greetings! Do you have any plans for this summer? I think I found something really interesting here http://6url.ru/mbUv Good wishes, sarek -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1328301 Title: no encripted mail possible with thunderbird - wrong passphrase error Status in thunderbird package in Ubuntu: Invalid Bug description: Installing thunderbird, enigmail, then write mail, activate "sign" mail. Click on send, then watch thunderbird respond with "Wrong passphrase". Since the passphrase never was asked it is true: it is wrong – it's not an empty string! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:30.0~b1+build2-0ubuntu0.14.04.1 Uname: Linux 3.14.6+ x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6119 F pulseaudio BuildID: 20140605085806 Channel: Unavailable CurrentDesktop: XFCE Date: Tue Jun 10 00:59:35 2014 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2011-10-19 (964 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-bebf1f36-e4a4-4665-9efa-6de192140223 PrefErrors: 'utf-8' codec can't decode byte 0xfc in position 2036: invalid start byte Profiles: Profile0 (Default) - LastVersion=30.0/20140605085806 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to trusty on 2014-02-24 (104 days ago) dmi.bios.date: 01/11/2008 dmi.bios.vendor: Acer dmi.bios.version: S1.3502 dmi.board.name: Victoria dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrS1.3502:bd01/11/2008:svnAcer,inc.:pnTravelMate6292:pvrNotApplicable:rvnAcer,Inc.:rnVictoria:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: TravelMate 6292 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1328301/+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 1676076] [NEW] [X556UB, Realtek ALC255, Speaker, Internal] flac files skips or sttuter, rhytmbox and mpd
Public bug reported: Flac Files skips (like an old record scratch) on rhytmbox or mpd server (via soundcard or a DAC). The skip is random. Description:Ubuntu 16.10 Release:16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: brujo 2424 F...m pulseaudio /dev/snd/controlC0: brujo 2424 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 25 12:11:59 2017 InstallationDate: Installed on 2017-01-30 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X556UB, Realtek ALC255, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1676076 Title: [X556UB, Realtek ALC255, Speaker, Internal] flac files skips or sttuter, rhytmbox and mpd Status in alsa-driver package in Ubuntu: New Bug description: Flac Files skips (like an old record scratch) on rhytmbox or mpd server (via soundcard or a DAC). The skip is random. Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: brujo 2424 F...m pulseaudio /dev/snd/controlC0: brujo 2424 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 25 12:11:59 2017 InstallationDate: Installed on 2017-01-30 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X556UB, Realtek ALC255, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1676076/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Okay, I was hoping that I'd be able to suggest, as a simple fix, trying a newer driver. But I see that v304 is, indeed, the most recent Linux driver available for your GPU. http://www.nvidia.com/Download/Find.aspx?lang=en-us -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 Notes: The system it's updated (full-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1676079] [NEW] fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build
Public bug reported: user@machine:~$ sudo apt-get install -y fglrx fglrx-core fglrx-amdcccle fglrx-dev ... Configurando fglrx-core (2:15.201.2-0ubuntu0.14.04.1) ... update-alternatives: a usar /usr/lib/fglrx-core/ld.so.conf para disponibilizar /etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) em modo automático Loading new fglrx-core-15.201.2 DKMS files... First Installation: checking all kernels... Building only for 4.4.0-66-generic Building for architecture x86_64 Building initial module for 4.4.0-66-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/fglrx-core.0.crash' Error! Bad return status for module build on kernel: 4.4.0-66-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.201.2/build/make.log for more information. update-initramfs: deferring update (trigger activated) A processar 'triggers' para initramfs-tools (0.103ubuntu4.6) ... update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic A processar 'triggers' para libc-bin (2.19-0ubuntu6.11) ... A seleccionar pacote anteriormente não seleccionado fglrx. ... user@machine:~$ cat /var/lib/dkms/fglrx-core/15.201.2/build/make.log DKMS make.log for fglrx-core-15.201.2 for kernel 4.4.0-66-generic (x86_64) Sáb Mar 25 14:34:03 BRT 2017 /usr/sbin/dkms: linha 73: cd: /var/lib/dkms/fglrx/15.201.2/build: Arquivo ou diretório não encontrado AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/4.4.0-66-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x modules make[1]: Entrando no diretório `/usr/src/linux-headers-4.4.0-66-generic' CC [M] /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function ‘firegl_major_proc_read’: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be len = seq_printf(m, "%d\n", major); ^ /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function ‘KCL_fpu_save_init’: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: error: ‘XSTATE_FP’ undeclared (first use in this function) if (!(fpu->state.xsave.header.xfeatures & XSTATE_FP)) ^ /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: At top level: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6498:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ make[2]: ** [/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o] Erro 1 make[1]: ** [_module_/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x] Erro 2 make[1]: Saindo do diretório `/usr/src/linux-headers-4.4.0-66-generic' make: ** [kmod_build] Erro 2 build failed with return value 2 user@machine:~$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty user@machine:~$ uname -a Linux machine 4.4.0-66-generic #87~14.04.1-Ubuntu SMP Fri Mar 3 17:32:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-core 2:15.201.2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-66-generic Date: Sat Mar 25 12:46:41 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201.2: added Error! Could not locate dkms.conf file. File: does not exist. DuplicateSignature: dkms:fglrx-core:2:15.201.2-0ubuntu0.14.04.1:/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0640] InstallationDate: Installed on 2014-08-18 (950 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 5547 PackageVersion: 2:15.201.2-0ubuntu0.14.04.1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPa
[Desktop-packages] [Bug 1676079] Re: fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1676079 Title: fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: user@machine:~$ sudo apt-get install -y fglrx fglrx-core fglrx-amdcccle fglrx-dev ... Configurando fglrx-core (2:15.201.2-0ubuntu0.14.04.1) ... update-alternatives: a usar /usr/lib/fglrx-core/ld.so.conf para disponibilizar /etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) em modo automático Loading new fglrx-core-15.201.2 DKMS files... First Installation: checking all kernels... Building only for 4.4.0-66-generic Building for architecture x86_64 Building initial module for 4.4.0-66-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/fglrx-core.0.crash' Error! Bad return status for module build on kernel: 4.4.0-66-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.201.2/build/make.log for more information. update-initramfs: deferring update (trigger activated) A processar 'triggers' para initramfs-tools (0.103ubuntu4.6) ... update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic A processar 'triggers' para libc-bin (2.19-0ubuntu6.11) ... A seleccionar pacote anteriormente não seleccionado fglrx. ... user@machine:~$ cat /var/lib/dkms/fglrx-core/15.201.2/build/make.log DKMS make.log for fglrx-core-15.201.2 for kernel 4.4.0-66-generic (x86_64) Sáb Mar 25 14:34:03 BRT 2017 /usr/sbin/dkms: linha 73: cd: /var/lib/dkms/fglrx/15.201.2/build: Arquivo ou diretório não encontrado AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/4.4.0-66-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x modules make[1]: Entrando no diretório `/usr/src/linux-headers-4.4.0-66-generic' CC [M] /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function ‘firegl_major_proc_read’: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be len = seq_printf(m, "%d\n", major); ^ /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function ‘KCL_fpu_save_init’: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: error: ‘XSTATE_FP’ undeclared (first use in this function) if (!(fpu->state.xsave.header.xfeatures & XSTATE_FP)) ^ /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: At top level: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6498:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ make[2]: ** [/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o] Erro 1 make[1]: ** [_module_/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x] Erro 2 make[1]: Saindo do diretório `/usr/src/linux-headers-4.4.0-66-generic' make: ** [kmod_build] Erro 2 build failed with return value 2 user@machine:~$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty user@machine:~$ uname -a Linux machine 4.4.0-66-generic #87~14.04.1-Ubuntu SMP Fri Mar 3 17:32:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-core 2:15.201.2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-66-generic Date: Sat Mar 25 12:46:41 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201.2: added Error! Could not locate dkms.conf file. File: does not exist. DuplicateSignature: dkms:fglrx-core:2:15.201.2-0ubuntu0.14.04.1:/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be GraphicsCard: Int
[Desktop-packages] [Bug 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Yes, I know. This GPU driver works well in Ubuntu, Ubuntu Mate, etc. Only not works in Budgie. I test install Budgie DE in Ubuntu Mate and I can't login in Bugdie DE neither, only in Mate DE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 Notes: The system it's updated (full-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
I suspect you will have the same issue with gnome-shell. budgie and gnome-shell use the same window manager. On 25 March 2017 at 18:04, Diogo Gomes <1675...@bugs.launchpad.net> wrote: > Yes, I know. > > This GPU driver works well in Ubuntu, Ubuntu Mate, etc. > > Only not works in Budgie. > > I test install Budgie DE in Ubuntu Mate and I can't login in Bugdie DE > neither, only in Mate DE. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1675830 > > Title: > nvidia 304 graphics causes Login loop in Ubuntu Budgie > > Status in Ubuntu Budgie: > New > Status in nvidia-graphics-drivers-304 package in Ubuntu: > New > > Bug description: > Nvidia 304 graphics kills budgie-window manager process and causes > login loop in Ubuntu Budgie. > > Steps: > - Enter password > - System shows top bar (half cropped) > - Sometimes dock appears > - Screen goes off (with no signal in monitor) > - Screen shows login screen again > > System description: > - OS: Ubuntu Budgie 17.04 (daily build) > - GPU: Nvidia GeForce 6150SE nForce 430 > > Packages: > - Budgie Desktop 10.2.9 > - Nvidia Graphics Drivers 304 > > Notes: > The system it's updated (full-upgrade) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 Notes: The system it's updated (full-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1558821] Re: transmission-gtk crashed with SIGABRT in event_errx()
*** This bug is a duplicate of bug 1421440 *** https://bugs.launchpad.net/bugs/1421440 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1558821 Title: transmission-gtk crashed with SIGABRT in event_errx() Status in transmission package in Ubuntu: Confirmed Bug description: The connection was completely disabled and only get back, after kill transmission process. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: transmission-gtk 2.84-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Thu Mar 17 19:13:44 2016 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2016-03-12 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) ProcCmdline: transmission-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: transmission StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 event_errx () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_cancel_request () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_getaddrinfo_cancel () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 ?? () Title: transmission-gtk crashed with SIGABRT in event_errx() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1558821/+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 1429399] Re: transmission-gtk crashed with SIGABRT in event_errx()
*** This bug is a duplicate of bug 1421440 *** https://bugs.launchpad.net/bugs/1421440 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1429399 Title: transmission-gtk crashed with SIGABRT in event_errx() Status in transmission package in Ubuntu: Confirmed Bug description: probably the only bug is the fact that this error message presented itself. What I expected: I shut transmission down very quickly after start up. I expected Transmission to close & then nothing to happen. what happened: I briefly opened transmission to see if any downloads were waiting for a session. Seeing no jobs requiring attention, I then quickly shut transmission down again, whereupon the error message presented itself. >>lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 >>apt-cache policy transmission-gtk transmission-gtk: Installed: 2.84-0.2ubuntu1 Candidate: 2.84-0.2ubuntu1 Version table: *** 2.84-0.2ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: transmission-gtk 2.84-0.2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sat Mar 7 16:09:45 2015 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2014-03-05 (367 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: transmission-gtk Signal: 6 SourcePackage: transmission StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 event_errx () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_cancel_request () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_getaddrinfo_cancel () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 ?? () Title: transmission-gtk crashed with SIGABRT in event_errx() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1429399/+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 1285990] Re: transmission-gtk crashed with SIGABRT in event_errx()
*** This bug is a duplicate of bug 1280082 *** https://bugs.launchpad.net/bugs/1280082 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1285990 Title: transmission-gtk crashed with SIGABRT in event_errx() Status in transmission package in Ubuntu: Confirmed Bug description: Crashed upon closing after adding a new magnet link. New torrent was still downloading metadata from the magnet link when the application was closed. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: transmission-gtk 2.82-1.1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5 Uname: Linux 3.13.0-13-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 28 00:31:49 2014 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2014-01-08 (50 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/bin/transmission-gtk magnet:?xt=urn:btih:DXJECU7ISIWPH7LE4SNWGOW4EMYNJZTB&dn=Elementary.S02E16.720p.HDTV.X264-DIMENSION&tr=udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80&tr=udp://open.demonii.com:80&tr=udp://tracker.coppersurfer.tk:80 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: transmission StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 event_errx () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_cancel_request () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 Title: transmission-gtk crashed with SIGABRT in event_errx() UpgradeStatus: Upgraded to trusty on 2014-02-08 (19 days ago) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1285990/+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 1465283] Re: transmission-gtk crashed with SIGABRT in event_errx()
*** This bug is a duplicate of bug 1421440 *** https://bugs.launchpad.net/bugs/1421440 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1465283 Title: transmission-gtk crashed with SIGABRT in event_errx() Status in transmission package in Ubuntu: Confirmed Bug description: I got this while closing Transmission ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: transmission-gtk 2.84-0.2ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 15 15:21:49 2015 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2014-10-16 (241 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: transmission-gtk ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=it_IT.UTF-8 LANGUAGE=it_IT XDG_RUNTIME_DIR= Signal: 6 SourcePackage: transmission StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 event_errx () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_cancel_request () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 evdns_getaddrinfo_cancel () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 ?? () Title: transmission-gtk crashed with SIGABRT in event_errx() UpgradeStatus: Upgraded to vivid on 2015-04-25 (51 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1465283/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
Done! See bug 1676081. Thanks Seth -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Fix Released Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Won't Fix Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1425397] Re: transmission-gtk crashed with SIGABRT in event_errx()
*** This bug is a duplicate of bug 1421440 *** https://bugs.launchpad.net/bugs/1421440 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1425397 Title: transmission-gtk crashed with SIGABRT in event_errx() Status in transmission package in Ubuntu: Confirmed Bug description: Crash while closes. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: transmission-gtk 2.84-0.2ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-14.15-generic 3.18.7 Uname: Linux 3.18.0-14-generic i686 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Wed Feb 25 02:11:22 2015 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2014-11-28 (89 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcCmdline: transmission-gtk Signal: 6 SourcePackage: transmission StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libevent-2.0.so.5 event_errx () from /usr/lib/i386-linux-gnu/libevent-2.0.so.5 evdns_cancel_request () from /usr/lib/i386-linux-gnu/libevent-2.0.so.5 evdns_getaddrinfo_cancel () from /usr/lib/i386-linux-gnu/libevent-2.0.so.5 ?? () Title: transmission-gtk crashed with SIGABRT in event_errx() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev robots sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1425397/+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 1676081] [NEW] No wifi connection after suspend with a MacBook Pro
Public bug reported: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: macbookpro network suspend-resume systemctl wifi ** Description changed: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 + Side effect: it closes the VPN connection if there was one. + # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1676081 Title: No wifi connection after suspend with a MacBook Pro Status in wpa package in Ubuntu: New Bug description: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1676081/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Okay, I'm in. I replace the window manager installing compiz and now I can login with nvidia 304. Steps: - Install compiz - Add "compiz --replace" to autostart - Install nvidia-304 - Reboot Result: In first login, I have a loop and in the second time that I enter password, I am enable to login. Notes: This confirms that is an incompatibility with budgie window manager and nvidia 304. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie Status in Ubuntu Budgie: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 Notes: The system it's updated (full-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1351939] Re: Sending USSD message does not work
Hello. My device is E3372. After sending any USSD i've get error: "GDBus.Error:org.freedesktop.ModemManader1.Error.Core.Failed: Invalid USSD response received: '^CCIN:2,0,"","",0'". Modem Manager GUI 0.0.18-3 Linux Mint 18.1 In the previous version of the USSD went sometimes and sometimes not. Please fix the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager: New Status in modem-manager-gui package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Confirmed Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+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 1676088] [NEW] unity greeter logs-in when clicking password field
Public bug reported: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1676088 Title: unity greeter logs-in when clicking password field Status in lightdm package in Ubuntu: New Bug description: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1676088/+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 1676088] Re: unity greeter logs-in when clicking password field
** Description changed: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. - Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... + + I think this is also a security issue. I missed checking marking the + checkbox... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1676088 Title: unity greeter logs-in when clicking password field Status in lightdm package in Ubuntu: New Bug description: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... I think this is also a security issue. I missed checking marking the checkbox... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1676088/+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 1674304] Re: PRIME synchronization not working with xserver-1.19.x
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1674304 Title: PRIME synchronization not working with xserver-1.19.x Status in nvidia-prime package in Ubuntu: Confirmed Bug description: xserver-1.19.x is being proposed for 17.04, currently available in test ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 On 2 separate Optimus laptops there is no sign of it actually working, tearing while using nvidia drivers (375.x) is rampart. Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels. Shows this in kern.log so support is enabled Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver supports precise vblank timestamp ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 20 07:53:12 2017 InstallationDate: Installed on 2017-03-15 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+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 1587090] Re: gEdit 3.18.3 in Xenial 16.04 Print Menu capabilities are broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1587090 Title: gEdit 3.18.3 in Xenial 16.04 Print Menu capabilities are broken Status in gedit package in Ubuntu: Confirmed Bug description: I just upgraded from Trusty 14.04 and had the surprise to see the newer version of gEdit 3.18 with a broken Print Menu. First, previously the print menu was accessible from gEdit window control bar alongside the opened file folders. No more, the print menu is only accessible from the global menu. The window control bar has 3 times the height from the previous version I used (3.10) and with less accessible information, as Open, +, and Save are now on a bar of their own. Why the GNOME guys at each new release feel like they need to re- invent the wheel ? And occasionally broke previously working features ... Then when trying to print some text pages I realized that my pages were printed with excessive margins on all side. That was never the case before either in Trusty or Precise. I later tried to configure the margins ... Well there is no margins configuration available to speak off. But the capability appears on the Paper Size --> Manage Custom Sizes --> Paper Margin ... I should mention here that I previously changed the Default Paper Size from U.S. Letter to A4. Then opening the 'Manage Custom Size' I was expecting the A4 Paper Size listed in the pop-window field Paper Size, but still I got the U.S. Letter paper size ... gEdit will provide a name 'Custom Size 1' as the pop-up open. I changed the margins from 0.25 inch to 0.1 and changed the default name to 'A4 Small Margin' and typing the inches size of A4 instead of the listed inches size for U.S. Letter. However to no avail, as when closing the pop-up window the name reverts back to 'Custom Size 1'. Then using this setting to print a text page wouldn't change anything on the printed margins ... Using the 'Margins from printer' --> in my case KONICA-MINOLTA magicolor 1650 EN (which are set at 0.17 inches) wouldn't change anything either. The default paper size change (from U.S. Letter to A4) is not set until you actually print a page ... And there is no option to change inches to cm ... When the GNOME team will stop breaking previously perfectly working application ? May be when I have time I will provide a scan of before / after update to Xenial 16.04. I consider this a damaging regression. Previously we had from the GNOME team a 'blurry' font bug in gEdit 3.10, however hopefully someone (not part of the GNOME) provided a patch. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 30 16:12:20 2016 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2016-05-23 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1587090/+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 1643544] Re: HP Scanjet 7400c Scanner locks USB2 port
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1643544 Title: HP Scanjet 7400c Scanner locks USB2 port Status in sane-backends package in Ubuntu: Confirmed Bug description: When trying to scan with the hp7400c (avision backend), the scanner will stop in the middle of the page, no further commands on a USB mouse or keyboard are possible. xsane will throw a I/O device error. This happens on my desktop with ubuntu 16.10 (Kernel 4.8.0-27) and my laptop (kernel 4.4.0-38) NO USB3 hardware is involved in my case, both machines have USB2-ports only, lsmod does NOT show and xhci modules loaded. I tried the command SANE_DEBUG_AVISION=8 SANE_DEBUG_SANEI_USB=5 scanimage > scanfehlerxx.txt and produced the files attached. The key statement might be: [sanei_usb] sanei_usb_read_bulk: trying to read 61054 bytes [sanei_usb] sanei_usb_read_bulk: read failed: No such device (it may have been disconnected) [avision] read 0 bytes [avision] No data arrived. This error occurs as well with Fedora 24, but NOT with debian 8.6. So it may be related with the more recent kernels and their behaviour on the USB ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1643544/+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 1676094] [NEW] Memory Leak in Firefox 50.1
Public bug reported:
Consistent memory leak during normal use. Seen increase in the firefox
task memory use from <500 met to over 3 gig. Attaching an output of
pidstat showing steady increase over the day.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: firefox 50.1.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cliff 2174 F pulseaudio
BuildID: 20161213225349
Channel: Unavailable
CurrentDesktop: GNOME
Date: Sat Mar 25 18:39:56 2017
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-02-13 (40 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
IpRoute:
default via 192.168.1.1 dev wlp3s0 proto static metric 600
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.194 metric 600
MostRecentCrashID: bp-46c62897-65eb-4932-916e-3061f2170315
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
GNOME Shell Integration -
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
PrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
prefs.js
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=50.1.0/20161213225349 (In use)
RelatedPackageVersions: gnome-shell 3.24.0-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.name: W35_37ET
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug zesty
** Attachment added: "firefoxps.txt"
https://bugs.launchpad.net/bugs/1676094/+attachment/4845917/+files/firefoxps.txt
--
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/1676094
Title:
Memory Leak in Firefox 50.1
Status in firefox package in Ubuntu:
New
Bug description:
Consistent memory leak during normal use. Seen increase in the
firefox task memory use from <500 met to over 3 gig. Attaching an
output of pidstat showing steady increase over the day.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: firefox 50.1.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cliff 2174 F pulseaudio
BuildID: 20161213225349
Channel: Unavailable
CurrentDesktop: GNOME
Date: Sat Mar 25 18:39:56 2017
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-02-13 (40 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
IpRoute:
default via 192.168.1.1 dev wlp3s0 proto static metric 600
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.194 metric
600
MostRecentCrashID: bp-46c62897-65eb-4932-916e-3061f2170315
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
GNOME Shell Integration -
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
PrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
p
[Desktop-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in kdelibs: Unknown Status in shared-mime-info: Confirmed Status in kde4libs package in Ubuntu: Confirmed Status in shared-mime-info package in Ubuntu: Triaged Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/289592/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
Comment 14 from https://bugs.kde.org/show_bug.cgi?id=303627 summarizes the current state of this bug. "I'm taking the liberty to close this report (it was "confirmed" by my vote in the first place). The fake mimetypes have been removed from kcoreaddons's kde5.xml file: https://github.com/KDE/kcoreaddons/commit/36ff1bf60c9b12c28ed4d7566abceac10cab345e They still are defined in the old kdelibs package, but we cannot remove them because it would break all the kde4 apps that are still using them. While kdelibs4 is still being released with new bugfixes, most of those kde4 apps are not." ** Package changed: kde4libs (Debian) => ubuntu ** No longer affects: ubuntu ** Bug watch added: KDE Bug Tracking System #303627 https://bugs.kde.org/show_bug.cgi?id=303627 ** Also affects: kdelibs via https://bugs.kde.org/show_bug.cgi?id=303627 Importance: Unknown Status: Unknown ** Changed in: kde4libs (Ubuntu) Status: Invalid => Confirmed ** Changed in: kde4libs (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in kdelibs: Unknown Status in shared-mime-info: Confirmed Status in kde4libs package in Ubuntu: Confirmed Status in shared-mime-info package in Ubuntu: Triaged Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/289592/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
It seems this was fixed upstream for KDE Frameworks 5. Not sure if we
can backport the fix because of the compatibility problems mentioned.
This is also mentioned in the porting notes for KDE Frameworks 5.
https://community.kde.org/Frameworks/Porting_Notes#Mime_Types
"The following fake MIME types have been removed and should be replaced
as follows:
all/allfiles ➙ application/octet-stream
all/all ➙ application/octet-stream+inode/directory
uri/{mms,mmst,mmsu,pnm,rtspt,rtsptu} ➙ x-scheme-handler/..."
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/289592
Title:
Unknown media types in /usr/share/mime/packages/kde.xml
Status in kdelibs:
Unknown
Status in shared-mime-info:
Confirmed
Status in kde4libs package in Ubuntu:
Confirmed
Status in shared-mime-info package in Ubuntu:
Triaged
Status in shared-mime-info package in Debian:
Confirmed
Bug description:
Here is the problem:
# update-mime-database /usr/share/mime
[...]
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
It seems to come from this file:
/usr/share/mime/packages/kde.xml
To manage notifications about this bug go to:
https://bugs.launchpad.net/kdelibs/+bug/289592/+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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
I've just done a fresh install today of 16.04.2 which has network manager version 1.2.2. Once the updates are completed the network manager has been upgraded to version 1.2.6. I can confirm that the "Connect" button when trying to connect to a Hidden Wireless network so no longer greyed out & the problem has been resolved! As Sebastien mentioned in comment #24 up & coming updates have been passed through & have resolved the issue. Because of this I'd say the status of this bug will need to be changed to Fix Released & close this bug. Cheers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in Network Manager Applet: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1542733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 193325] Re: "unknown media type" during update
** Project changed: nautilus => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Confirmed => New ** Changed in: ubuntu Remote watch: Debian Bug tracker #469833 => None ** No longer affects: ubuntu ** Bug watch removed: Debian Bug tracker #469833 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469833 ** Bug watch removed: freedesktop.org Bugzilla #16816 https://bugs.freedesktop.org/show_bug.cgi?id=16816 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/193325 Title: "unknown media type" during update Status in shared-mime-info: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/193325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
** Changed in: kdelibs Status: Unknown => Won't Fix ** Changed in: kdelibs Importance: Unknown => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in kdelibs: Won't Fix Status in shared-mime-info: Confirmed Status in kde4libs package in Ubuntu: Confirmed Status in shared-mime-info package in Ubuntu: Triaged Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/289592/+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 1643345] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed]
A baseline test I did was to update both a VM with a fresh install of Ubuntu 16.04 and my laptop where I upgraded from 14.04 to 16.04. With both systems up to date (March 25th, 2017) I tried to install the the latest Nvidia 375 drivers. It installed on the VM (though it is kind of worthless here), but hung up on my laptop just like it has in the past. With it both compiling and failing to compile on the same version and patch level of Ubuntu, just different paths to get to this point, I would think this points to an issue with Ubuntu, not Nvidia. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1643345 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [Makefile:81: recipe for target 'modules' failed] Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: The default selected nvidia driver 367 does not work in Ubuntu 16.04 64-bit. Hangs on build. Ran killall make in order to get updates to complete. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-367 (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.4.0-45-generic Date: Sun Nov 20 08:45:49 2016 InstallationDate: Installed on 2014-09-28 (784 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 367.57-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: nvidia-graphics-drivers-367 Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-10-20 (31 days ago) modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643345/+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 1633732] Re: File operation popup and icon progress bar do not go away
I filed a bug report at https://bugzilla.gnome.org/show_bug.cgi?id=780553 ** Bug watch added: GNOME Bug Tracker #780553 https://bugzilla.gnome.org/show_bug.cgi?id=780553 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1633732 Title: File operation popup and icon progress bar do not go away Status in nautilus package in Ubuntu: Confirmed Bug description: On Ubuntu 16.10 x64 with Nautilus 3.20.3. I removed 11097 files three hours ago. Every time I open Nautilus now, a popup saying the operation completed is displayed. The launch icon also displays a progress bar. If I click on the icon with the white circle, the notification goes away. If I close Nautilus window the launch icon still shows the progressbar. If I open Nautilus again, the popup is shown again. A strange thing is that the progressbars do not show a perfect 100% completion, but the popup actually says 11097/11097 files were treated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633732/+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 1676097] Re: unity-control-center crashed with SIGSEGV in _cogl_check_extension()
** Information type changed from Private to Public -- 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/1676097 Title: unity-control-center crashed with SIGSEGV in _cogl_check_extension() Status in unity-control-center package in Ubuntu: New Bug description: I clicked on on the top bar to change sound settings, as soon as I clicked sound settings nothing happened and I received and error. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Mar 26 08:21:41 2017 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2017-03-25 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcCmdline: unity-control-center sound SegvAnalysis: Segfault happened at: 0x7fb573ba3b59:mov(%rsi),%rsi PC (0x7fb573ba3b59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: unity-control-center crashed with SIGSEGV in cogl_renderer_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1676097/+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 1623666] Re: iOS device contents not displayed in Ubuntu
#28 and then #29 work perfectly for me, connecting an iPhone with iOS 10.2 to my laptop with Ubuntu 16.04 running on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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
