[Desktop-packages] [Bug 1573900] Re: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
nothing for now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1573900 Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 Status in pulseaudio package in Ubuntu: New Bug description: I found this problem when I was trying to install wine- qqintl_0.1.3-2_i386.deb. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: libpulse0: Install libasound2-plugins: Install libpulse0: Configure libasound2-plugins: Configure Architecture: amd64 Date: Sat Apr 23 13:26:04 2016 DuplicateSignature: package:libpulse0:(not installed):尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 ErrorMessage: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 InstallationDate: Installed on 2016-04-16 (7 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573900] Re: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1573900 Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 Status in pulseaudio package in Ubuntu: New Bug description: I found this problem when I was trying to install wine- qqintl_0.1.3-2_i386.deb. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: libpulse0: Install libasound2-plugins: Install libpulse0: Configure libasound2-plugins: Configure Architecture: amd64 Date: Sat Apr 23 13:26:04 2016 DuplicateSignature: package:libpulse0:(not installed):尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 ErrorMessage: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 InstallationDate: Installed on 2016-04-16 (7 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573900] [NEW] package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同
Public bug reported: I found this problem when I was trying to install wine- qqintl_0.1.3-2_i386.deb. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: libpulse0: Install libasound2-plugins: Install libpulse0: Configure libasound2-plugins: Configure Architecture: amd64 Date: Sat Apr 23 13:26:04 2016 DuplicateSignature: package:libpulse0:(not installed):尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 ErrorMessage: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 InstallationDate: Installed on 2016-04-16 (7 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1573900 Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 Status in pulseaudio package in Ubuntu: New Bug description: I found this problem when I was trying to install wine- qqintl_0.1.3-2_i386.deb. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: libpulse0: Install libasound2-plugins: Install libpulse0: Configure libasound2-plugins: Configure Architecture: amd64 Date: Sat Apr 23 13:26:04 2016 DuplicateSignature: package:libpulse0:(not installed):尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 ErrorMessage: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 InstallationDate: Installed on 2016-04-16 (7 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/etc/pulse/client.conf', 它与软件包 libpulse0:i386 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking
Facing the same issue on Lubuntu 16.04 - 32 bit after upgrading from lubuntu 15.10. The issue seems to be with Light DM, Light Locker setting also not opening. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434986] Re: Not working network connection after boot
** Changed in: network-manager Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1572640] Re: cursor invisible after timeout and screen-saving
I upgraded from lubuntu 15.10 and also got affected by this bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1572640 Title: cursor invisible after timeout and screen-saving Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: When installed from the *Lubuntu alternate* ISO files, the default systems are affected by this bug: After time-out the screensaver kicks in and the user is locked out. At the unlock screen the cursor is visible, but after unlock the cursor is invisible. This bug does not affect the corresponding desktop ISO files, neither the live session nor the default installed systems. ISO files: The Lubuntu Xenial final version dated 20160419 xenial-alternate-i386.iso xenial-desktop-i386.iso xenial-alternate-amd64.iso xenial-desktop-amd64.iso Links to the computer specs: http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w https://shop.lenovo.com/ISS_Static/ww/wci/products/us/laptop/thinkpad/x-series/x131e-intel/X131e-Datasheet-Intel.pdf Link to detailed description: http://ubuntuforums.org/showthread.php?t=2321069=13473145#post13473145 The cursor appears again after logout and stays after login. This bug is similar to or the same as Bug #1568604: Mouse cursor lost when unlocking ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Apr 20 17:37:20 2016 InstallationDate: Installed on 2016-04-20 (0 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160419) SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1572640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573898] [NEW] Libreoffice calc Version: 4.2.8.2 Build ID: 420m0(Build:2) hangs repeatedly
Public bug reported: Libreoffice calc hangs for a long time when trying to open files of any type. This becomes more pronounced if the file has data links to web resources. The problem also occurs when trying to create a new file and re-opening it after save and close. Output of lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 Output of apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:4.2.8-0ubuntu4 Candidate: 1:4.2.8-0ubuntu4 Version table: *** 1:4.2.8-0ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.8-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-58.64~14.04.1-generic 3.19.8-ckt16 Uname: Linux 3.19.0-58-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 10:32:25 2016 InstallationDate: Installed on 2016-02-17 (65 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1573898 Title: Libreoffice calc Version: 4.2.8.2 Build ID: 420m0(Build:2) hangs repeatedly Status in libreoffice package in Ubuntu: New Bug description: Libreoffice calc hangs for a long time when trying to open files of any type. This becomes more pronounced if the file has data links to web resources. The problem also occurs when trying to create a new file and re-opening it after save and close. Output of lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 Output of apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:4.2.8-0ubuntu4 Candidate: 1:4.2.8-0ubuntu4 Version table: *** 1:4.2.8-0ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.8-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-58.64~14.04.1-generic 3.19.8-ckt16 Uname: Linux 3.19.0-58-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 10:32:25 2016 InstallationDate: Installed on 2016-02-17 (65 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1573898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
** Attachment added: "Screenshot from 2016-04-23 06-49-25.png" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+attachment/4643755/+files/Screenshot%20from%202016-04-23%2006-49-25.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
It came back right after 16,04 was released, only this time it is worse: 1. The font is thin in the dash, menu, clock 2. Nautilus doesn't integrate with Unity 3. The left wallpaper is weird, as if it was trying to display two resolutions at the same time 4. There is no wallpaper on the right monitor 5. There are terrible artefacts on the right monitor if I move a window around This happens around 2/3 of times that I boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Committed Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note the above work-around wont work till llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Committed Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note the above work-around wont work till llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Any chance on providing more instructions on how to resolve? I thought I had installed the above deb successfully, but it didn't seem to make a difference. Most likely I've not done something right. Many thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Committed Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in llvm-toolchain-3.8 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note the above work-around wont work till llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: compose and dead keys stopped working in gnome terminal
Meanwhile I found out that this also affects nautilus, but not e.g. Gedit, Firefox, HexChat, etc. And it only happens when XIM is selected as input method. ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: compose and dead keys stopped working in gnome terminal Status in gnome-terminal package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1230169] Re: screensaver turns on while watching youtube video
[Expired for gnome-screensaver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1230169 Title: screensaver turns on while watching youtube video Status in gnome-screensaver package in Ubuntu: Expired Bug description: Screensaver on laptop turns on while watching youtube videos and laptop is on battery power. It doesn't matter if video is fullscreen or not. Screen saver turns itself on. This shouldn't happen. If video is playing it means someone is using the screen. It doesn't happen in windows. i also didn't see this happening on desktop Kubuntu install. i have not yet tested media players such as VLC to see if it also happens there. Hardware: HP dm1 with E-450 APU (using proprietary AMD drivers), 2 GB RAM, Kubuntu 64bit 13.04 (all updates applied, vanilla install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1230169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1321960] Re: Ubuntu should not lock screen when I watch a long video
[Expired for gnome-screensaver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1321960 Title: Ubuntu should not lock screen when I watch a long video Status in gnome-screensaver package in Ubuntu: Expired Bug description: When a video is playing (youtube or a movie), ubuntu should not consider the period as inactive and lock screen (as specified in the "System Settings - > Brightness and Lock -> Turn screen off when inactive for: " setting). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1321960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1571139] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1571139 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in hicolor-icon-theme package in Ubuntu: Fix Released Bug description: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 15 21:34:16 2016 Dependencies: ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2015-11-09 (158 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1571139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573893] [NEW] Can't use Epson XP-310 printer with 16.04 no lsb
Public bug reported: Clean Ubuntu 16.04 install. I can't install the driver for my Epson XP-310 printer. I get a dependency error of lsb. Lsb won't install due to missing lsb-core, lsb-printer and a few other issues. I downloaded the deb packages from 15.10 but then another missing dependency message comes up, about 10 more. There is a work around if the driver is installed but I can't install the driver. Will this be fixed by 16.04.1? I plan to use 15.10 until then. Thanks ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1573893 Title: Can't use Epson XP-310 printer with 16.04 no lsb Status in cups-filters package in Ubuntu: New Bug description: Clean Ubuntu 16.04 install. I can't install the driver for my Epson XP-310 printer. I get a dependency error of lsb. Lsb won't install due to missing lsb-core, lsb-printer and a few other issues. I downloaded the deb packages from 15.10 but then another missing dependency message comes up, about 10 more. There is a work around if the driver is installed but I can't install the driver. Will this be fixed by 16.04.1? I plan to use 15.10 until then. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1573893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573891] [NEW] Closing lid doesn't suspend despite setting in 16.04
Public bug reported: Not sure this is the right place but after my upgrade to 16.04 my laptop no longer suspends when the lid is closed. The lap top is an HP Envy 17-3090NR. Not sure what else you'd like to know but I'm happy to help debug this. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573891 Title: Closing lid doesn't suspend despite setting in 16.04 Status in gnome-power-manager package in Ubuntu: New Bug description: Not sure this is the right place but after my upgrade to 16.04 my laptop no longer suspends when the lid is closed. The lap top is an HP Envy 17-3090NR. Not sure what else you'd like to know but I'm happy to help debug this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1573891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565349] Re: No such file or directory while executing existing 64bit binary
The workaround doesn't work for me. I can get the driver to install because it says the dependency is lsb, then I need lsb-core and lsb- printer and about 5 more. So I downloaded the 15.10 deb packages but they depend on other installs, about 10 so until lsb in back in Ubuntu 16.04 I can't use my printer. Hopefully it will be fixed by 16.04.1 and then I will switch over from 15.10. I'll open a separate bug for it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1565349 Title: No such file or directory while executing existing 64bit binary Status in cups-filters package in Ubuntu: Triaged Bug description: With this error, I can only find references for 32bit executables on 64bit system. This is not the case: the binary is 64bit, the interpreter and every library seems in place. ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ ./epson-escpr-wrapper bash: ./epson-escpr-wrapper: No such file or directory ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ ldd epson-escpr-wrapper linux-vdso.so.1 => (0x7ffdc3f7a000) libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 (0x7f0ce852c000) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7f0ce82ac000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0ce808e000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0ce7d85000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0ce79bb000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7f0ce777) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7f0ce743f000) libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 (0x7f0ce7233000) libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 (0x7f0ce7021000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0ce6e07000) /lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2 (0x55ed62393000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7f0ce6b35000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7f0ce6905000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7f0ce6701000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7f0ce64f6000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7f0ce629) libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 (0x7f0ce605d000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7f0ce5e4a000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7f0ce5c13000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7f0ce59e) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f0ce576) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f0ce5513000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ce530f000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7f0ce510b000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f0ce4eef000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7f0ce4ce7000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7f0ce4c61000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7f0ce4a3f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0ce4837000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0ce4614000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f0ce4333000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f0ce40c3000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7f0ce3eae000) ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ file epson-escpr-wrapper epson-escpr-wrapper: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-lsb-x86-64.so.3, for GNU/Linux 2.6.15, BuildID[sha1]=558bd286d0e69cd3994a848c7c04d09a026cc2c4, stripped ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lsb-base 9.20160110 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 2 22:16:04 2016 Dependencies: InstallationDate: Installed on 2016-03-25 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all SourcePackage: lsb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1565349/+subscriptions --
[Desktop-packages] [Bug 1419523] Re: GVFS MTP paths are not stable
** Changed in: gvfs Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1419523 Title: GVFS MTP paths are not stable Status in gvfs: Confirmed Status in gvfs package in Ubuntu: Triaged Bug description: Every time I unplug my Android phone and reconnect it, its URL changes. E.g. when it is mounted as mtp://[usb:002,002]/ and I unplug and recoonect it, it gets a new URL, e.g. mtp://[usb:002,003]/. This behavior breaks all use cases which depend on a stable path (e.g. shell scripts, synching via Unison etc.). Is there any way to implement a behavior similar to removable drives? They get a consistent mounting path, which is /media//, where is either the volume label (if present) or the volume ID. In GVFS this would require uniquely identifying MTP devices. If there is something as a volume ID, GUID or any other element that can uniquely identify a MTP device, this would be the way to go. If MTP doesn't provide this kind of ID (don't know if it does), then maybe "fingerprinting" the device (based on characteristics as the USB vendor & device IDs) may be a valid workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1419523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 447497] Re: No bindings for WINDOW_STATE_* in python-wnck
** Changed in: gnome-python-desktop (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-python-desktop in Ubuntu. https://bugs.launchpad.net/bugs/447497 Title: No bindings for WINDOW_STATE_* in python-wnck Status in Gnome Python Desktop: Fix Released Status in gnome-python-desktop package in Ubuntu: Fix Released Status in gnome-python-desktop package in Debian: Fix Released Bug description: There is no bindings for WINDOW_STATE_* constants in gnome-python-desktop 2.28. Some taskbar-like applets can not work. Sorry for bad English. Reproducer for this bug: python -c "import wnck; print wnck.WINDOW_STATE_URGENT" ** (-c:3362): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum' ** (-c:3362): WARNING **: Trying to register gtype 'WnckWindowActions' as flags when in fact it is of type 'GEnum' ** (-c:3362): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum' Traceback (most recent call last): File "", line 1, in AttributeError: 'module' object has no attribute 'WINDOW_STATE_URGENT' To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-python-desktop/+bug/447497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1572855] Re: libgbm.so.1: cannot open shared object file
if you upgraded before the fix landed see Comment #4 for manual fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1572855 Title: libgbm.so.1: cannot open shared object file Status in xorg-lts-transitional package in Ubuntu: Fix Released Bug description: After upgrading from 14.04 -> 16.04, there are still some dpkg-diverts left in place. This stops gdm/gnome-shell from booting up at all. Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-shell: error while loading shared libraries: libgbm.so.1: cannot open shared object file: No such file or directory Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-session-binary[1018]: WARNING: App 'gnome-shell-wayland.desktop' exited with code 127 Apr 20 23:22:12 ubuntu gnome-session-binary[1018]: WARNING: App 'gnome-shell-wayland.desktop' exited with code 127 Apr 20 23:22:13 ubuntu gnome-session[1213]: gnome-shell: error while loading shared libraries: libgbm.so.1: cannot open shared $dpkg -L libgbm1 /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0 diverted by libgbm1-lts-wily to: /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1572855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 510059] Re: Gvfs keeps asking for password when trying to mount Samba share
** Changed in: gvfs Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/510059 Title: Gvfs keeps asking for password when trying to mount Samba share Status in gvfs: Incomplete Status in gvfs package in Ubuntu: Triaged Bug description: Binary package hint: nautilus My Ubuntu Desktop (9.10, 64-bit) VM can't connect to my Windows 7 (64-bit, Ultimate) File Share using Nautilus. I enter "smb://" in the address bar and then it comes up with a password dialog (see screenshot) and then after entering the correct login info, the dialog disappears for a second or two but then reappears again. The dialog always comes back up and the share is never mounted. * Connecting from an XP box on the network to the windows 7 share works just fine. * Connecting from the Ubuntu machine to the windows 7 share using the appropriate 'smbmount' command works just fine. * Connecting from the Ubuntu machine (using the nautilus GUI) to the XP box (password protected) works just fine. * Then I turned off password protection in Win7, rebooted the win7 machine, and still all of the above tests turned out the same. And the Ubuntu machine still doesn't connect to the windows share using the nautilus GUI, and still displays the password dialog even though no password is required anymore. * I tried using smbclient to view the shares, here is the output (not sure if I should be trying something else using the smbclient program): o eddie@eddie-ubuntu:~$ smbclient -L eddie-win7 Enter eddie's password: session setup failed: SUCCESS - 0 ProblemType: Bug Architecture: amd64 Date: Sun Jan 17 15:41:28 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) Package: nautilus 1:2.28.1-0ubuntu3 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-server SourcePackage: nautilus Uname: Linux 2.6.31-17-server x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/510059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059872] Re: Error formatting disk using disk utility
I can not reproduce this using the steps listed in the bug description
on 15.10, can you?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1059872
Title:
Error formatting disk using disk utility
Status in DarGUI:
New
Status in OEM Priority Project:
New
Status in udisks2 package in Ubuntu:
Invalid
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Trusty:
Triaged
Status in util-linux package in Debian:
Fix Released
Bug description:
[Impact]
Formatting a SD card using the disk utility fails with an error
message
"Error formatting disk - Error synchronizing after initial wipe: Timed
out waiting for object (udisks-error-quark, 0)"
The underlying problem is that the "wipefs" tool from util-linux does
not work any more.
You can work around this bug in gnome-disk-utility using these steps:
* After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.
* Delete the partition ("minus" icon)
* Create a new partition
[Test Case]
$ sudo modprobe scsi_debug dev_size_mb=200
# this creates a new /dev/sdX, usually /dev/sdb; check dmesg!
# now create a partition table
$ cat
[Desktop-packages] [Bug 1480673] Re: Asus T300 CHI bluetooth Touchpad is recognized incorrectly
Confirmed here too... although with 16.04 / Unity there was touchscreen input during live session but after booting the installed system I just realised there is no touchscreen input device. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1480673 Title: Asus T300 CHI bluetooth Touchpad is recognized incorrectly Status in xinput package in Ubuntu: Confirmed Bug description: The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo. Both (touchscreen, touchpad) only work like a mouse (moving pointer, left and right click), scrolling, zooming, etc. is not working. the keyboard works fine. relevant content of /proc/bus/input/devices: [...] I: Bus=0003 Vendor=06cb Product=11f0 Version=0111 N: Name="SYNAPTICS Synaptics Touch Digitizer V04" P: Phys=usb-:00:14.0-7/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input9 U: Uniq= H: Handlers=mouse1 event9 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=2608003 I: Bus=0003 Vendor=06cb Product=11f0 Version=0111 N: Name="SYNAPTICS Synaptics Touch Digitizer V04 Pen" P: Phys=usb-:00:14.0-7/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input10 U: Uniq= H: Handlers=mouse2 event10 B: PROP=0 B: EV=1b B: KEY=c03 1 0 0 0 0 B: ABS=103 B: MSC=10 [...] I: Bus=0005 Vendor=0b05 Product=8502 Version=0001 N: Name="ASUS T300CHI DOCKING" P: Phys=34:02:86:7b:3b:9d S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0006/input/input18 U: Uniq=1c:b7:2c:15:94:8b H: Handlers=sysrq kbd mouse3 event17 B: PROP=0 B: EV=12001f B: KEY=20 0 0 2000 40 3 10207 ff9f387ad9405fff febeffdfffef fffe B: REL=303 B: ABS=700 B: MSC=10 B: LED=1f output of xinput --list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ B16_b_02 USB-PS/2 Optical Mouse id=9[slave pointer (2)] ⎜ ↳ HID 0566:3108 id=11 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=14 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=15 [slave pointer (2)] ⎜ ↳ ASUS T300CHI DOCKINGid=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ HID 0566:3108 id=10 [slave keyboard (3)] ↳ C-Media Electronics Inc. USB Multimedia Audio Deviceid=12 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=13 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] output of synclient is: Couldn't find synaptics properties. No synaptics driver loaded? but I'm unsure if the synaptics driver is the right place to look since basic functionality is working and the "ASUS T300CHI DOCKING" is recognized as "pointer" it seems that the device is recognized by the kernel but only used as a pointing device. I've also attached the xorg.log output of uname -a: Linux xxx 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux it's a completely fresh install of xubuntu 15.04 with software-updater run once (so no strange hacks or drivers installed) output of lsb_release -rd: Description: Ubuntu 15.04 Release: 15.04 output of apt-cache policy xinput xinput: Installed: 1.6.1-1 Candidate: 1.6.1-1 Version table: *** 1.6.1-1 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status expected results: - scrolling on touchpad and touchscreen should work with a two-finger gesture - zooming on touchpad and touchscreen should work with a two-finger gesture actual results: two fingers are not recognized on touchscreen or touchpad Any help would be appreciated, if you need more console output or logs, please let me know. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux
[Desktop-packages] [Bug 1572855] Re: libgbm.so.1: cannot open shared object file
I did and upgrade from 14.04 and totem and rhythmbox ask for that lib file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1572855 Title: libgbm.so.1: cannot open shared object file Status in xorg-lts-transitional package in Ubuntu: Fix Released Bug description: After upgrading from 14.04 -> 16.04, there are still some dpkg-diverts left in place. This stops gdm/gnome-shell from booting up at all. Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-shell: error while loading shared libraries: libgbm.so.1: cannot open shared object file: No such file or directory Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-session-binary[1018]: WARNING: App 'gnome-shell-wayland.desktop' exited with code 127 Apr 20 23:22:12 ubuntu gnome-session-binary[1018]: WARNING: App 'gnome-shell-wayland.desktop' exited with code 127 Apr 20 23:22:13 ubuntu gnome-session[1213]: gnome-shell: error while loading shared libraries: libgbm.so.1: cannot open shared $dpkg -L libgbm1 /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0 diverted by libgbm1-lts-wily to: /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1572855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573856] Re: NetworkManager resets spoofed mac address to physical mac
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573856 Title: NetworkManager resets spoofed mac address to physical mac Status in network-manager package in Ubuntu: New Bug description: Ubuntu 16.04 bumped NetworkManager to version 1.1.93. Unlike 15.10 (with v1.0.4) and earlier NetworkManager now resets temporary mac of an interface to actual physical mac effectively disabling typical wifi anonymization technics. Same issue is present in just released NetworkManager 1.2. It appears that sometime between 1.0.10 and 1.1.93 there was a change in src/devices/wifi/nm-device-wifi.c from /* Set spoof MAC to the interface */ cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless); if (cloned_mac) nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI); to /* Set spoof MAC to the interface */ cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless); nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI); cloned_mac is NULL if not specified in NetworkManager GUI. When called with NULL nm_device_set_hw_addr sets the mac to physical mac of the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
I can confirm that ubuntu 16.04 LTS is exhibiting this behavior with three separate bluetooth headsets (JABRA REVO 2.0, Sony MDRXB950BT, and Sennheiser Urbanite XL WIreless). 14.04, 14.10, 15.04, and 15.10 all worked quite well with no additional configuration necessary. By "worked quite well" I mean I could pair all three headsets, they would remain paired through reboots, and I could get A2DP output from each. On 16.04, in both gnome and unity, it is a hit or miss affair of pairing any of these headsets. I have a Dell XPS 15 and had zero problems prior to installing 16.04. I used the procedure in post #5, but that does not persist after reboots. I have to unpair the headset completely and then repair in order to get sound. Even then it's hit or miss, sometimes it doesn't work. I'd be happy to give more details to help resolve this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1433548] Re: missing words in the English dictionary
although i'm not going to carry on this particular bug, this way is a bit more usable. I just checked it against 5.1.2. ** Description changed: - Mozilla Firefox marks the words "anonymised", "constraining", - "forecastable", "hyperlink", "inconstructive", "mandatorily", - "megalomanic", "misconfigured", "oxymoronic", "redistributable", - "refactor", "resizable", "spreadsheet", "unapplied", "unconfirm", - "unconfirming", "unobvious" and "workflow" as spelling errors. + from both en_gb and en_us: - ProblemType: Bug - DistroRelease: Ubuntu 14.04 - Package: myspell-en-gb 1:4.2.1-0ubuntu1.1 - ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 - Uname: Linux 3.13.0-46-generic x86_64 - ApportVersion: 2.14.1-0ubuntu3.7 - Architecture: amd64 - CurrentDesktop: Unity - Date: Wed Mar 18 12:44:59 2015 - InstallationDate: Installed on 2014-08-20 (209 days ago) - InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) - PackageArchitecture: all - SourcePackage: libreoffice-dictionaries - UpgradeStatus: No upgrade log present (probably fresh install) + anonymised + forecastable + hyperlink + inconstructive + mandatorily + megalomanic + misconfigured + oxymoronic + redistributable + refactor + resizable + unapplied + unconfirm + unconfirming + unobvious + workflow + + + only from en_gb: + + constraining + redistributable ** Summary changed: - missing words in the English dictionary + missing words in the English dictionaries -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1433548 Title: missing words in the English dictionaries Status in libreoffice-dictionaries package in Ubuntu: Confirmed Bug description: from both en_gb and en_us: anonymised forecastable hyperlink inconstructive mandatorily megalomanic misconfigured oxymoronic redistributable refactor resizable unapplied unconfirm unconfirming unobvious workflow only from en_gb: constraining redistributable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1433548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573760] Re: screen remains black after hibernation or suspend to RAM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1573760 Title: screen remains black after hibernation or suspend to RAM Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: I just installed XUbuntu 16.06 on my laptop. Suspend to RAM and hibernation seem to work correctly, but resuming from either of it is not actually possible because the screen remains black. Concerning hibernation, this happens with the default hibernation method as well as with TuxOnIce. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-21.37~ppa1-generic-tuxonice 4.4.6 Uname: Linux 4.4.0-21-generic-tuxonice x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 22 21:20:22 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1573760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 105879] Re: please add hyph_en_AU.dic
just did so. I used a provided (so a virtual package), and did the very same thing we did for en-za. committed to git https://anonscm.debian.org/git/pkg-openoffice/libreoffice-dictionaries.git/commit/?id=ffc3fbab81db7194a4f1c5ad754ac3892f17389e ** Changed in: libreoffice-dictionaries (Ubuntu) Status: Triaged => Fix Committed ** Changed in: libreoffice-dictionaries (Ubuntu) Assignee: (unassigned) => Mattia Rizzolo (mapreri) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/105879 Title: please add hyph_en_AU.dic Status in OpenOffice: Fix Released Status in libreoffice-dictionaries package in Ubuntu: Fix Committed Status in openoffice.org package in Ubuntu: Invalid Bug description: Binary package hint: openoffice.org-hyphenation Please add the Australian hyphenation dictionary to the OO.o package, it is found here: http://www.justlocal.com.au/clients/oooau/hyph_en_AU.dic See http://www.justlocal.com.au/clients/oooau/ for more info. To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/105879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573760] Re: screen remains black after hibernation or suspend to RAM
I had the same issue on an E7450 laptop. Linux rune 4.6.0-040600rc4-generic #201604172330 SMP Mon Apr 18 03:32:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I had upgraded the kernel, but this didn't fix the issue. I upgraded the bios to a12, and now I can suspend and my display comes back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1573760 Title: screen remains black after hibernation or suspend to RAM Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: I just installed XUbuntu 16.06 on my laptop. Suspend to RAM and hibernation seem to work correctly, but resuming from either of it is not actually possible because the screen remains black. Concerning hibernation, this happens with the default hibernation method as well as with TuxOnIce. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-21.37~ppa1-generic-tuxonice 4.4.6 Uname: Linux 4.4.0-21-generic-tuxonice x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 22 21:20:22 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1573760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 928255] Re: missing symlinks in /usr/share/hunspell/
starting from 1:5.1.0-1ubuntu1 the files are named with the _ instead of the -, so this is definitely fixed in xenial. ** Changed in: libreoffice-dictionaries (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/928255 Title: missing symlinks in /usr/share/hunspell/ Status in libreoffice-dictionaries package in Ubuntu: Fix Released Bug description: Firefox does not remember en_ZA as a default spellchecker language until I added the two symlinks below: Existing files: 0 root@muizenberg:/usr/share/hunspell#ls -l en_ZA* -rw-r--r-- 1 root root 36223 2011-03-28 18:41 en_ZA.aff -rw-r--r-- 1 root root 595937 2011-03-28 18:41 en_ZA.dic Symlinks needed: 0 root@muizenberg:/usr/share/hunspell#ls -l en-ZA* lrwxrwxrwx 1 root root 9 2012-02-07 15:37 en-ZA.aff -> en_ZA.aff lrwxrwxrwx 1 root root 9 2012-02-07 15:37 en-ZA.dic -> en_ZA.dic 0 root@muizenberg:/usr/share/hunspell# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/928255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573839] Re: please merge gdk-pixbuf from debian
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1573839 Title: please merge gdk-pixbuf from debian Status in gdk-pixbuf package in Ubuntu: New Bug description: debdiff here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1573839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1566836] Re: Suspend on lid close setting in power options does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed -- 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/1566836 Title: Suspend on lid close setting in power options does not work Status in unity-control-center package in Ubuntu: Confirmed Bug description: The Power settings in unity-control-center provide the option to set events for "lid close" triggers. Setting this option to 'suspend' does nothing with an up to date Xenial installation. Running "sudo journalctl -b -u systemd-logind" shows that lid open and close events are properly detected, there is just no action associated with them. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 6 08:48:23 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-25 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1566836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1572938] Re: Connected to wifi, the indicator behaves odly
When the icon is wrong i AM connected, but if i get disconnected at that point, the only way to get back on-line is by using "connect to hidden network" since the indicator will not show any wifi in range. On my laptop, deleting all known networks and rebooting solved my issue. On my desktop, this didn't help and i'm still struggling with the bug. I will try using unity and report back. The attached files to this bug are from my laptop, i will report it from my desktop too. -- 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/1572938 Title: Connected to wifi, the indicator behaves odly Status in network-manager-applet package in Ubuntu: New Bug description: When connecting to wifi the first time after install, the indicator show icon for Ethernet connection. Restarting the networkd-manager auto-connects to the wifi but no list of availble networks and still showing icon for ethernet. (see attached picture) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 21 12:16:49 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-21 (0 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 10.42.0.1 dev wlo1 proto static metric 600 10.42.0.0/24 dev wlo1 proto kernel scope link src 10.42.0.89 metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/0 sakrecoer 2 81d6a098-b98a-4703-9214-72be00384eb8 /org/freedesktop/NetworkManager/ActiveConnection/3 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1572938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573855] [NEW] Ubuntu-gnome can't open terminal
Public bug reported: 1. Refresh install Ubuntu-gnome 16.04 64-bit 2. type terminal from search the terminal menu appeaars on the top left corner right after Activities, the cursor is running. After a while, nothing happened. Terminal doesn't appear at all. I can start xterm, termit without any problem After reinstall ubuntu-gnome 14.04 64-bit, I can open terminal without any issue. This is definitely a bug. ** Affects: nlpsolver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nlpsolver in Ubuntu. https://bugs.launchpad.net/bugs/1573855 Title: Ubuntu-gnome can't open terminal Status in nlpsolver package in Ubuntu: New Bug description: 1. Refresh install Ubuntu-gnome 16.04 64-bit 2. type terminal from search the terminal menu appeaars on the top left corner right after Activities, the cursor is running. After a while, nothing happened. Terminal doesn't appear at all. I can start xterm, termit without any problem After reinstall ubuntu-gnome 14.04 64-bit, I can open terminal without any issue. This is definitely a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nlpsolver/+bug/1573855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573338] Re: can't install google chrome browser on ubuntu gnome 16.04
** Description changed: 1. refresh install ubuntu gnome 16.04 2. download google chrome from google chrome website. The file name is google-chrome-stable_current_amd64.deb 3. double click the file 4. before click install, there is a blue bar said "This software comes from a 3rd party and may contain non-free component - and there are two grey icons above this bar. left grey icon has words "non-free", right grey icon has words "3rd party" + and there are two grey icons above this bar. left grey icon has words "non-free", right grey icon has words "3rd party" 5. click install. - the right grey icon with words "3rd party" has gone. Install button flesh and nothing happened + the right grey icon with words "3rd party" has gone. Install button flesh and nothing happened 6. click install. nothing happened except install button flesh again. + + + After reinstall ubuntu-gnome 14.04. I can install google chrome without any problem. So this is 100% a bug for ubuntu-gnome 16.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nlpsolver in Ubuntu. https://bugs.launchpad.net/bugs/1573338 Title: can't install google chrome browser on ubuntu gnome 16.04 Status in nlpsolver package in Ubuntu: Confirmed Bug description: 1. refresh install ubuntu gnome 16.04 2. download google chrome from google chrome website. The file name is google-chrome-stable_current_amd64.deb 3. double click the file 4. before click install, there is a blue bar said "This software comes from a 3rd party and may contain non-free component and there are two grey icons above this bar. left grey icon has words "non-free", right grey icon has words "3rd party" 5. click install. the right grey icon with words "3rd party" has gone. Install button flesh and nothing happened 6. click install. nothing happened except install button flesh again. After reinstall ubuntu-gnome 14.04. I can install google chrome without any problem. So this is 100% a bug for ubuntu-gnome 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nlpsolver/+bug/1573338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "
Nice solution (workaround?), Sverker. I have called the lightdm developer's attention to it via a merge proposal. ** Changed in: lightdm (Ubuntu) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/1273524 Title: LXDE guest session shows error message "no session for pid " Status in One Hundred Papercuts: Triaged Status in lightdm package in Ubuntu: In Progress Status in lxsession package in Ubuntu: Triaged Bug description: EXPECTED RESULTS: Log into guest session with no error messages. ACTUAL RESULTS: Upon log in to guest session, an error "no session for pid " is printed. STEPS TO REPRODUCE: 1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual hardware, log into guest session. 2. After being logged in, see error message. AFFECTED VERSIONS: lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=Lubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "
** Branch linked: lp:~gunnarhj/lightdm/guest-session-lubuntu -- 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/1273524 Title: LXDE guest session shows error message "no session for pid " Status in One Hundred Papercuts: Triaged Status in lightdm package in Ubuntu: In Progress Status in lxsession package in Ubuntu: Triaged Bug description: EXPECTED RESULTS: Log into guest session with no error messages. ACTUAL RESULTS: Upon log in to guest session, an error "no session for pid " is printed. STEPS TO REPRODUCE: 1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual hardware, log into guest session. 2. After being logged in, see error message. AFFECTED VERSIONS: lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=Lubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573847] [NEW] libgl1-mesa-dri-dbg is missing in Ubuntu 16.04
Public bug reported: `libgl1-mesa-dri-dbg` is missing in Ubuntu 16.04. It's unclear where debugging symbols for `libgl1-mesa-dri` come from. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-dri 11.2.0-1ubuntu2 Uname: Linux 4.5.0-040500-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde kein Wert zugewiesen CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 01:07:11 2016 DistUpgraded: 2016-03-14 15:43:39,246 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2015-12-12 (132 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.5.0-040500-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: mesa UpgradeStatus: Upgraded to xenial on 2016-03-14 (39 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 22 17:49:39 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5557 vendor CMN xserver.version: 2:1.18.3-1ubuntu2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1573847 Title: libgl1-mesa-dri-dbg is missing in Ubuntu 16.04 Status in mesa package in Ubuntu: New Bug description: `libgl1-mesa-dri-dbg` is missing in Ubuntu 16.04. It's unclear where debugging symbols for `libgl1-mesa-dri` come from. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-dri 11.2.0-1ubuntu2 Uname: Linux 4.5.0-040500-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde kein Wert zugewiesen CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 01:07:11 2016 DistUpgraded: 2016-03-14 15:43:39,246 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2015-12-12 (132 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.5.0-040500-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: mesa UpgradeStatus: Upgraded to xenial on 2016-03-14 (39 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled
Yes, Catalyst has been the only driver that has been working for me so far. I don't believe the radeon driver was working before either, I remember having a similar problem when I upgraded to 15.10. Thanks for the debugging tip. However it didn't work. Immediately after running the modprobe command the screens go blank, lose signal input, and then after about 5 seconds the machine reboots. After logging in again, I found that dmesg didn't have a chance to pipe its output to the file either. Definitely seems to be a bug closer to the kernel / drm -- 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/1568429 Title: Radeon won't work with KMS enabled Status in xorg package in Ubuntu: New Bug description: I have a Radeon HD 5770 GPU. After upgrading to Xenial today and ensuring the xorg radeon driver was enabled, my machine will no longer boot to a usable state. After selecting default Ubuntu option from GRUB menu, both monitor lose signal input and the keyboard becomes unresponsive. Sometimes the machine will reboot on its own, most of the time I have to hard reset. If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the machine will boot but the radeon driver will not load. Attempting to load radeon driver with `sudo modprobe radeon modeset=1` after booting with modesetting off results in the same fail state explained above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds] CompositorRunning: None Date: Sat Apr 9 20:02:22 2016 DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990] InstallationDate: Installed on 2013-12-29 (832 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago) dmi.bios.date: 04/29/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0519 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Apr 9 19:49:46 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1573839] [NEW] please merge gdk-pixbuf from debian
Public bug reported: debdiff here ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1573839 Title: please merge gdk-pixbuf from debian Status in gdk-pixbuf package in Ubuntu: New Bug description: debdiff here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1573839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573839] Re: please merge gdk-pixbuf from debian
** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1573839/+attachment/4643567/+files/debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1573839 Title: please merge gdk-pixbuf from debian Status in gdk-pixbuf package in Ubuntu: New Bug description: debdiff here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1573839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573831] [NEW] simple-scan scrambles scanned images
Public bug reported: My configuration: HP MFP477 (printer and scanner). Installed printer using HP device manager (which works fine). Scanning from simple-scan works fine as long as I scan single pages (from the flatbed scanner) If I want to scan from the feeder (and set the scanner to duplex (which it should be able to do), the pages are scanned only patially and parts of the scanned image copied onto one page (typically 1/3rd of page 1 and 2/3rds of page 2 are put underneath each other, then the remaining image of page 2 is sent to second page). Installing the dev libs which hp-doctor suggests does not improve on the result (thus I have removed them again). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 00:25:44 2016 InstallationDate: Installed on 2013-05-17 (1071 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1573831 Title: simple-scan scrambles scanned images Status in simple-scan package in Ubuntu: New Bug description: My configuration: HP MFP477 (printer and scanner). Installed printer using HP device manager (which works fine). Scanning from simple-scan works fine as long as I scan single pages (from the flatbed scanner) If I want to scan from the feeder (and set the scanner to duplex (which it should be able to do), the pages are scanned only patially and parts of the scanned image copied onto one page (typically 1/3rd of page 1 and 2/3rds of page 2 are put underneath each other, then the remaining image of page 2 is sent to second page). Installing the dev libs which hp-doctor suggests does not improve on the result (thus I have removed them again). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 00:25:44 2016 InstallationDate: Installed on 2013-05-17 (1071 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1573831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550292] Re: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shared-mime-info (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/1550292 Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in shared-mime-info package in Ubuntu: Confirmed Bug description: bug report starts after upgrading 15.10 to 16.04 beta1, don't know exactly what's happen ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.5-2 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Feb 26 11:47:52 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-01 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: shared-mime-info Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-02-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1550292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573396] Re: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shared-mime-info (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/1573396 Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in shared-mime-info package in Ubuntu: Confirmed Bug description: 1)Description:Ubuntu 16.04 LTS Release: 16.04 (actually I was upgrading from 15.10 to 16.04 when it appeared) 2)shared-mime-info: Installed: 1.5-2 Candidate: 1.5-2 Version table: *** 1.5-2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) My computer should update without any problems 4) The problem occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 07:05:38 2016 DuplicateSignature: package:shared-mime-info:1.3-1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-02-07 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1573396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051625] Re: nautilus crashed with signal 5 in _XEventsQueued()
** Changed in: nautilus (Ubuntu) Importance: Medium => High -- 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/1051625 Title: nautilus crashed with signal 5 in _XEventsQueued() Status in nautilus package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Bug description: Bug report prompt appeared when printing in Libreoffice Calc. Not sure about the actual cause. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Mon Sep 17 00:02:19 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+478+220'" InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcCmdline: nautilus trash:// ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to quantal on 2012-09-08 (8 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1051625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573499] Re: intermittent dns name resolution errors - network-manager
I spent hours sorting through my system logs to see if I could find out on my own what is causing this issue. I found numerous error messages. that appear to be at least partially a timing issue with systemd. Network-manger was trying to establish a connection prior to reaching the desktop environment, then only starting after Kwallet opened. This would make sense if I was on an always wired machine, not so much on a laptop. I also noticed numerous times where whoopsie is trying to send bug reports prior to achieving the connection, failing, then sending immediately after connecting (hogging all of my limited bandwidth in the process). This could account for some DNS resolution issues if there was not enough bandwidth left for queries. I experimented by purging WICD and its dependencies, then reinstalling Network-manager and its dependencies. I noticed an immediate improvement in dns name resolution from yesterday before I purged it from my system. However, now there is a graphical glitch in Plymouth as X starts, where there are 3 miniature instances still running as SDM launches, which I can deal with, and Kwallet opened upon reaching the desktop prompting for a password before wifi would connect. I resolved that issue by going to the wallet-manager and entering a null password. Now I'm getting consistent dns resolution, and wifi is connected before I reach the desktop. I can live with no wallet password and the graphical glitches. So consider this now partially resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573499 Title: intermittent dns name resolution errors - network-manager Status in network-manager package in Ubuntu: New Bug description: I'm a relative newbie to Ubuntu, but not Linux. I've been using Gentoo as my primary OS for the last 12 years, and other distros for the 6 years prior. I've tried 3 versions of Ubuntu/Kubuntu over the last month (14.04, 15.10, and today 16.04) all have had intermittent issues with dns name resolving. The problem appears to be with the network-manger application. My laptop is a Dell Precision M90 with an Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) WiFi network controller. The drivers are properly configured and I have no issues connecting to wireless networks. The problem is 2/3 of the time when I connect with wifi there is no dns name resolution, so I'm unable to surf the web. Unfortunately, even if dns resolution does work after boot-up, it often fails after long periods of inactivity. I've tried numerous possible workarounds that have been suggested on the net, as this seems to be a frequent problem. Unfortunately, I can't send a bug report while affected. The only 100% effective solution that always gives me a usable internet connection was to remove the offending applications network- manager, network-manager-pptp, and plasma-nm. Then replace them with wicd, wicd-daemon, wicd-gtk, and python-wicd. Using these packages I get a usable connection 100% of the time, no matter how long the connection is inactive. This problem appears to be long standing, as there are hundreds of pages on the net mentioning this and similar issues with network manger. Please resolve, or include a properly functioning equivalent, such as wicd in the default installation. TIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573823] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Happened when purging the tex-gyre (20150923-1) package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 AptOrdering: tex-gyre: Purge fonts-texgyre: Install fonts-texgyre: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 22 23:08:52 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-04-10 (378 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1573823 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Happened when purging the tex-gyre (20150923-1) package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 AptOrdering: tex-gyre: Purge fonts-texgyre: Install fonts-texgyre: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 22 23:08:52 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-04-10 (378 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1573823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454473] Re: In Ubuntu 15.04, simply moving the mouse via touchpad scrolls the window
Just to confirm #25, turning the touchpad on and off addresses the second issue, an alternative command being synclient TouchpadOff=1 and then 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1454473 Title: In Ubuntu 15.04, simply moving the mouse via touchpad scrolls the window Status in Xserver Xorg Input Synaptics: New Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Version: Ubuntu 3.19.0-16.16-generic 3.19.3 (This is mostly a copy paste from here: http://askubuntu.com/questions/617117/in-ubuntu-15-04-simply-moving- the-mouse-via-touchpad-scrolls-the-window) When I first boot everything works fine. But then something happens (not sure what triggers it) and many programs start scrolling just by moving the mouse over the window. So far I see this happens in Nautilus, Document Reader, Archive Manager, Ubuntu Software Center, Meld, and System Monitor (what do they all have in common, GTK?). It does NOT happen in web browsers, thunderbird, programs using Mono, Java, etc, for some reason. To be more specific of the issue: if the mouse starting position is over a document in Document Reader, for example, and then I move the mouse via touchpad, it'll scroll the document like an anchor, where the position of the mouse over the document doesn't change (yet it scrolls). I have already tried disabling "two finger scroll", "disable while typing", and the "tap to click" options, but they made no difference (after the glitchiness starts). The other odd case is that in Nautilus, if the mouse starting position is over a file or directory, it sometimes selects it instead of scrolling. Single-clicking a directory will open the directory (so the initial touch acts like a clicks, and letting go acts as the second click). The only thing I can do to temporarily fix the problem is restart the computer. There are no issues when using a mouse. Update 2015/05/03: I see how to reproduce it now. It appears to be a glitchy two-finger scroll issue. If you scroll any window with two fingers a lot, eventually it'll start causing this problem. Try various actions with two fingers, like "clicking" with two fingers, or scrolling in various directions quickly, etc, and it will start happening. It's interesting that it only happens in certain programs and not in others, which makes me wonder whether it is really a trackpad issue or some framework's issue. I can confirm that this is happening on the 15.04 Live CD, so this happens out of the box. The only work-around for this issue is to disable two-finger scroll (if it's already glitchy you'll need to restart). Not sure if it matters, but I'm using the Dell XPS 13 2015 9343. Update 2015/05/05: Apparently this bug can still happen even with two- finger scroll off, though it's more rare. Again, only certain programs have the issue, so it's hard to tell if it's a touchpad issue or something else. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ephi 1857 F pulseaudio /dev/snd/controlC0: ephi 1857 F pulseaudio CurrentDesktop: Unity Date: Tue May 12 22:06:46 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=270ecec3-b78c-4f85-a337-acd54f5e0b0e InstallationDate: Installed on 2015-05-01 (12 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 003: ID 0a5c:216f Broadcom Corp. Bus 001 Device 010: ID 1d57:ac01 Xenta Wireless Receiver (Keyboard and Mouse) Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=2bf488f3-23aa-4837-8f4d-861be61c94bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1568829] Re: nm-applet icon not showing
"Could not determine request UID" gave me a hint perhaps failing to get correct user from proc :-) This may be a bit more global issue rather than something confined to Network Manager considering gdm3 also fails to boot with this option on. (Haven't really dig deep, but perhaps systemd, polkit, consolekit, who knows...) -- 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/1568829 Title: nm-applet icon not showing Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Since I upgraded to -proposed network-manager and network-manager-gnome versions, nm-applet no longer works. Manually starting it on a console give: $ nm-applet (nm-applet:6250): nm-applet-WARNING **: GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: Unable to determine request sender and UID. (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 'NM_IS_CLIENT (client)' failed What's odd is the NM and NM-gnome base versions are not identical: $ apt-cache policy network-manager network-manager-gnome network-manager: Installed: 1.1.93-0ubuntu1 Candidate: 1.1.93-0ubuntu1 Version table: *** 1.1.93-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu10 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages network-manager-gnome: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 08:16:59 2016 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-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1: (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1: (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1568829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1412239] Re: Full date and time cannot be viewed in "modified" list view column
Quoting from AskUbuntu: So in order to have nautilus display the full date in list view, it is only necessary to change on line of code: in libnautilus-private /nautilus-column-utilities.c, line 78 from "date_modified" to "date_modified_full". -- 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/1412239 Title: Full date and time cannot be viewed in "modified" list view column Status in nautilus package in Ubuntu: Triaged Bug description: Having the full date is a basic function of every file browser but it seems it was completely removed from gnome and nobody cares over there... That is unacceptable und - quite unbelievable ;-) I'm using Ubuntu 14.04.01 LTS 64bit Here's a users's patch which at least adds a custom selectable "full datetime" column, which would be fine as a solution. https://launchpad.net/~mc3man/+archive/ubuntu/nauty-mods References: http://askubuntu.com/questions/285493/how-to-show-full-date-and-time-in-nautilus-files-3-6-list-view https://bugzilla.gnome.org/show_bug.cgi?id=676898 https://bugzilla.gnome.org/show_bug.cgi?id=699055 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1412239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1412239] Re: Full date and time cannot be viewed in "modified" list view column
this bug still exists in 16.04 !! Check this screenshot https://pbs.twimg.com/media/CgrKPuwWkAA_JIo.jpg:large Here is the solution: http://askubuntu.com/a/286141 ** Attachment added: "changing to date_modified_full solves the issue" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1412239/+attachment/4643455/+files/nautilus-bug.png -- 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/1412239 Title: Full date and time cannot be viewed in "modified" list view column Status in nautilus package in Ubuntu: Triaged Bug description: Having the full date is a basic function of every file browser but it seems it was completely removed from gnome and nobody cares over there... That is unacceptable und - quite unbelievable ;-) I'm using Ubuntu 14.04.01 LTS 64bit Here's a users's patch which at least adds a custom selectable "full datetime" column, which would be fine as a solution. https://launchpad.net/~mc3man/+archive/ubuntu/nauty-mods References: http://askubuntu.com/questions/285493/how-to-show-full-date-and-time-in-nautilus-files-3-6-list-view https://bugzilla.gnome.org/show_bug.cgi?id=676898 https://bugzilla.gnome.org/show_bug.cgi?id=699055 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1412239/+subscriptions -- Mailing list: https://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 1568829] Re: nm-applet icon not showing
On 2016-04-22 05:08 PM, Hideki Saito wrote: > I think I see what's going on. This seems to happen when hidepid is > set to anything other than 0. Hmm, I use hidepid=2,gid=27. Where gid 27 is the sudo group which I'm part of. Nice catch. It would be really nice not to have to resort to hidepid=0 to get nm-applet working. The hidepid feature is really nice to have. Thanks, Simon -- 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/1568829 Title: nm-applet icon not showing Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Since I upgraded to -proposed network-manager and network-manager-gnome versions, nm-applet no longer works. Manually starting it on a console give: $ nm-applet (nm-applet:6250): nm-applet-WARNING **: GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: Unable to determine request sender and UID. (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 'NM_IS_CLIENT (client)' failed What's odd is the NM and NM-gnome base versions are not identical: $ apt-cache policy network-manager network-manager-gnome network-manager: Installed: 1.1.93-0ubuntu1 Candidate: 1.1.93-0ubuntu1 Version table: *** 1.1.93-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu10 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages network-manager-gnome: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 08:16:59 2016 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-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1: (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1: (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1568829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568829] Re: nm-applet icon not showing
I think I see what's going on. This seems to happen when hidepid is set to anything other than 0. Remounted /proc with hidepid=0 and this seems to be fixed. Though, it used to work with other hidepid option, and is still an issue, but this may be an workaround for those affected... -- 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/1568829 Title: nm-applet icon not showing Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Since I upgraded to -proposed network-manager and network-manager-gnome versions, nm-applet no longer works. Manually starting it on a console give: $ nm-applet (nm-applet:6250): nm-applet-WARNING **: GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: Unable to determine request sender and UID. (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 'NM_IS_CLIENT (client)' failed What's odd is the NM and NM-gnome base versions are not identical: $ apt-cache policy network-manager network-manager-gnome network-manager: Installed: 1.1.93-0ubuntu1 Candidate: 1.1.93-0ubuntu1 Version table: *** 1.1.93-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu10 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages network-manager-gnome: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 08:16:59 2016 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-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1: (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1: (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1568829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573161] Re: Xorg freeze black screen unable to boot
as a workaround, downgrade to 361.28 and things should be OK until things get fixed in new LTS. I took NVidia package and compiled it instead of using Ubuntu's deb. Hope it helps .. -- 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/1573161 Title: Xorg freeze black screen unable to boot Status in xorg package in Ubuntu: New Bug description: Installing the tested recommended driver and rebooting leaves a black screen. To revert back I have to hard reboot and remove quiet and no splash from grub. From there I had to TTY and sudo purge nvidia* -y to have a bootable system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Apr 21 13:24:33 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0534] NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108GLM [NVS 5200M] [1028:1534] InstallationDate: Installed on 2016-04-19 (2 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) MachineType: Dell Inc. Latitude E6430 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=102550bd-8f7b-4a24-b6aa-16f02944e51c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0H3MT5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/12/2013:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. 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.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1573161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
The issue appeared on UBuntu 16.04 LTS, and getting rid of dnsmasq in Network Manager solved the issue for me as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568829] Re: nm-applet icon not showing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- 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/1568829 Title: nm-applet icon not showing Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Since I upgraded to -proposed network-manager and network-manager-gnome versions, nm-applet no longer works. Manually starting it on a console give: $ nm-applet (nm-applet:6250): nm-applet-WARNING **: GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: Unable to determine request sender and UID. (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 'NM_IS_CLIENT (client)' failed What's odd is the NM and NM-gnome base versions are not identical: $ apt-cache policy network-manager network-manager-gnome network-manager: Installed: 1.1.93-0ubuntu1 Candidate: 1.1.93-0ubuntu1 Version table: *** 1.1.93-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu10 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages network-manager-gnome: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 08:16:59 2016 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-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1: (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1: (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1568829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573773] [NEW] System freezes randomly a few times a day
Public bug reported: ~ % cat /var/log/xdm.log (==) Using system config directory "/usr/share/X11/xorg.conf.d" resize called 1920 1200 Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session /etc/X11/xdm/Xsession resize called 3840 1200 resize called 1920 1200 (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) [0x7f27e538b1f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) [0x7f27e538ba5d] (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248] (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) [0x7f27ee6db4a0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f27efa8adbb] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) [0x7f27ea7d103c] (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839] (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d] (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98] (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c] (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf] (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f27ee6c6830] (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e] (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) [0x7f27e538b1f3] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) [0x7f27e538ba5d] (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248] (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) [0x7f27ee6db4a0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f27efa8adbb] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) [0x7f27ea7d103c] (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839] (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d] (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98] (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c] (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf] (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f27ee6c6830] (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59] (EE) (EE) [mi] EQ overflow continuing. 200 events have been dropped. My system info: ~ % uname -a Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ~ % cat /etc/debian_version stretch/sid ~ % lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Codename: xenial ~ % ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1573773 Title: System freezes randomly a few times a day Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: ~ % cat /var/log/xdm.log (==) Using system config directory "/usr/share/X11/xorg.conf.d" resize called 1920 1200 Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup Fri Apr
[Desktop-packages] [Bug 1573420] Re: 16.04 beta: dns not set automaticly
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573420 Title: 16.04 beta: dns not set automaticly Status in network-manager package in Ubuntu: New Bug description: I just installed ubuntu 16.04 on a laptop, and after this, I had to install b43 firmware to get wifi working (as expected). When this was done - I could not see any available wireless networks in NetworkManager applet, so I had to install wicd-gtk - to be able to choose a wireless network and connect to it. Now it connects fine - but nothing is shown in nm-applet my taskbar, and DNS isn't set correct (it seems it isn't set at all), when it gets a DHCP address. (dhcp and wifi works fine on my ubuntu 14.04 machines). I tried running nmcli dev show - and it does not show any DNS information at all. when I switch resolv.conf to use 8.8.8.8 as nameserver - dns works fine. It feels as if I'm missing something for network-manager, to make it properly handle wireless, and that wicd-gtk doesn't do the job exactly right ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573420] [NEW] 16.04 beta: dns not set automaticly
You have been subscribed to a public bug: I just installed ubuntu 16.04 on a laptop, and after this, I had to install b43 firmware to get wifi working (as expected). When this was done - I could not see any available wireless networks in NetworkManager applet, so I had to install wicd-gtk - to be able to choose a wireless network and connect to it. Now it connects fine - but nothing is shown in nm-applet my taskbar, and DNS isn't set correct (it seems it isn't set at all), when it gets a DHCP address. (dhcp and wifi works fine on my ubuntu 14.04 machines). I tried running nmcli dev show - and it does not show any DNS information at all. when I switch resolv.conf to use 8.8.8.8 as nameserver - dns works fine. It feels as if I'm missing something for network-manager, to make it properly handle wireless, and that wicd-gtk doesn't do the job exactly right ? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 16.04 beta: dns not set automaticly https://bugs.launchpad.net/bugs/1573420 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568829] Re: nm-applet icon not showing
After verifying systemctl status network-manager that it is running, it seems to be every interaction from the user seems to be failing. sudo nmcli g (process:3936): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. sudo nmcli c (process:3943): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. I have verified network connection can't be modified any way from Gnome3, Unity (through system settings) including, changing the network setting (dialog won't even show), connecting to different Wi-Fi access point (never takes effect), turn the wi-fi off (again, nothing happens.) NetworkManager[1174]: [1461354274.8795] audit: op="connection-add-activate" result="fail" reason="Failed to get request UID." NetworkManager[1174]: [1461354295.8910] audit: op="radio-control" arg="wireless-enabled:0" result="fail" reason="Could not determine request UID." NetworkManager[1174]: [1461354296.9988] audit: op="radio-control" arg="wireless-enabled:1" result="fail" reason="Could not determine request UID." -- 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/1568829 Title: nm-applet icon not showing Status in network-manager-applet package in Ubuntu: New Bug description: Since I upgraded to -proposed network-manager and network-manager-gnome versions, nm-applet no longer works. Manually starting it on a console give: $ nm-applet (nm-applet:6250): nm-applet-WARNING **: GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: Unable to determine request sender and UID. (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: assertion 'NM_IS_CLIENT (client)' failed (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 'NM_IS_CLIENT (client)' failed What's odd is the NM and NM-gnome base versions are not identical: $ apt-cache policy network-manager network-manager-gnome network-manager: Installed: 1.1.93-0ubuntu1 Candidate: 1.1.93-0ubuntu1 Version table: *** 1.1.93-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu10 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages network-manager-gnome: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 08:16:59 2016 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-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1: (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1: (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: Unable to authenticate request.. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1568829/+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 1573362] Re: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1573362 Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: This error occured when I tried to upgrade my Ubuntu Kylin from version15.10 to version16.04 this morning. I upgraded my operating system from Ubuntu Kylin 15.04 to 15.10 last night. The sogoupinyin package often has errors. Since it is related to input method, maybe it also has something to do with errors of fontconfig. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 09:33:32 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-07-08 (288 days ago) InstallationMedia: Ubuntu-Kylin 15.04 "Vivid Vervet" - Release amd64 (20150423) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1573362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565508] Re: Update to 2.3.0 as usb-modeswich-data needs it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: usb-modeswitch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1565508 Title: Update to 2.3.0 as usb-modeswich-data needs it Status in usb-modeswitch package in Ubuntu: Confirmed Bug description: xenial has usb-modeswitch 2.2.5 , but 'proposed' archive have loaded usb-modeswitch-data to 20160112 but its changelog shows: - All Option configs updated with new OptionMode parameter from usb-modeswitch 2.3.0 * Bump Recommends/Breaks against usb-modeswitch to 2.3.0 So the upgrade wants to remove usb-modeswitch 2.2.5. So the need of at least 2.3.0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: usb-modeswitch 2.2.5+repack0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 3 18:45:13 2016 SourcePackage: usb-modeswitch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1565508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1566058] Re: usb-modeswitch-data breaking usb-modeswitch install
*** This bug is a duplicate of bug 1565508 ***
https://bugs.launchpad.net/bugs/1565508
** This bug has been marked a duplicate of bug 1565508
Update to 2.3.0 as usb-modeswich-data needs it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1566058
Title:
usb-modeswitch-data breaking usb-modeswitch install
Status in usb-modeswitch package in Ubuntu:
Confirmed
Bug description:
the title says it all, usb-modeswitch refuses to install with usb-
modeswitch-data (20160112-1)
root@hydra:/home/groo# apt install usb-modeswitch
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
usb-modeswitch : Depends: usb-modeswitch-data (>= 20140529) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.
the only way around this is to allow it to install an older version,
in this case 20151101-1.
root@hydra:/home/groo# apt install usb-modeswitch
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
usb-modeswitch : Depends: usb-modeswitch-data (>= 20140529) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.
root@hydra:/home/groo# aptitude install usb-modeswitch
The following NEW packages will be installed:
usb-modeswitch usb-modeswitch-data{ab}
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 83,4 kB of archives. After unpacking 354 kB will be used.
The following packages have unmet dependencies:
usb-modeswitch-data : Breaks: usb-modeswitch (< 2.3.0) but
2.2.5+repack0-1ubuntu1 is to be installed.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) usb-modeswitch [Not Installed]
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Install the following packages:
1) usb-modeswitch-data [20151101-1 (now, xenial)]
Accept this solution? [Y/n/q/?] y
The following NEW packages will be installed:
usb-modeswitch usb-modeswitch-data{a}
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 82,8 kB of archives. After unpacking 351 kB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://us.archive.ubuntu.com/ubuntu xenial/main amd64
usb-modeswitch-data all 20151101-1 [31,4 kB]
Get: 2 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 usb-modeswitch
amd64 2.2.5+repack0-1ubuntu1 [51,5 kB]
Fetched 82,8 kB in 0s (107 kB/s)
Supported
Create a snapshot of '/tmp/apt-btrfs-snapshot-mp-kbekwndd/@' in
'/tmp/apt-btrfs-snapshot-mp-kbekwndd/@apt-snapshot-2016-04-04_20:26:32'
(Reading database ... 434406 files and directories currently installed.)
Preparing to unpack .../usb-modeswitch-data_20151101-1_all.deb ...
Unpacking usb-modeswitch-data (20151101-1) ...
Preparing to unpack .../usb-modeswitch_2.2.5+repack0-1ubuntu1_amd64.deb ...
Unpacking usb-modeswitch (2.2.5+repack0-1ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up usb-modeswitch-data (20151101-1) ...
Setting up usb-modeswitch (2.2.5+repack0-1ubuntu1) ...
still present in xenial with all updates as of 04/04/2016
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1566058/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1572640] Re: cursor invisible after timeout and screen-saving
Same bug on Xubuntu 16.04, see also https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1572640 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1572640 Title: cursor invisible after timeout and screen-saving Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: When installed from the *Lubuntu alternate* ISO files, the default systems are affected by this bug: After time-out the screensaver kicks in and the user is locked out. At the unlock screen the cursor is visible, but after unlock the cursor is invisible. This bug does not affect the corresponding desktop ISO files, neither the live session nor the default installed systems. ISO files: The Lubuntu Xenial final version dated 20160419 xenial-alternate-i386.iso xenial-desktop-i386.iso xenial-alternate-amd64.iso xenial-desktop-amd64.iso Links to the computer specs: http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w https://shop.lenovo.com/ISS_Static/ww/wci/products/us/laptop/thinkpad/x-series/x131e-intel/X131e-Datasheet-Intel.pdf Link to detailed description: http://ubuntuforums.org/showthread.php?t=2321069=13473145#post13473145 The cursor appears again after logout and stays after login. This bug is similar to or the same as Bug #1568604: Mouse cursor lost when unlocking ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Apr 20 17:37:20 2016 InstallationDate: Installed on 2016-04-20 (0 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160419) SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1572640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573760] Re: screen remains black after hibernation or suspend to RAM
I thought apport would add this : the computer is a Dell Latitude E7450. ** Attachment added: "output of lshw" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1573760/+attachment/4643342/+files/lshw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1573760 Title: screen remains black after hibernation or suspend to RAM Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I just installed XUbuntu 16.06 on my laptop. Suspend to RAM and hibernation seem to work correctly, but resuming from either of it is not actually possible because the screen remains black. Concerning hibernation, this happens with the default hibernation method as well as with TuxOnIce. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-21.37~ppa1-generic-tuxonice 4.4.6 Uname: Linux 4.4.0-21-generic-tuxonice x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 22 21:20:22 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1573760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573760] [NEW] screen remains black after hibernation or suspend to RAM
Public bug reported: I just installed XUbuntu 16.06 on my laptop. Suspend to RAM and hibernation seem to work correctly, but resuming from either of it is not actually possible because the screen remains black. Concerning hibernation, this happens with the default hibernation method as well as with TuxOnIce. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-21.37~ppa1-generic-tuxonice 4.4.6 Uname: Linux 4.4.0-21-generic-tuxonice x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 22 21:20:22 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1573760 Title: screen remains black after hibernation or suspend to RAM Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I just installed XUbuntu 16.06 on my laptop. Suspend to RAM and hibernation seem to work correctly, but resuming from either of it is not actually possible because the screen remains black. Concerning hibernation, this happens with the default hibernation method as well as with TuxOnIce. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-21.37~ppa1-generic-tuxonice 4.4.6 Uname: Linux 4.4.0-21-generic-tuxonice x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 22 21:20:22 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1573760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1254946] Re: unable to import p12 files in 64bit 12.04 + 13.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1254946 Title: unable to import p12 files in 64bit 12.04 + 13.04 Status in gnome-keyring package in Ubuntu: Confirmed Bug description: on a fresh install of 64bit 12.04 or 13.04, if you attempt importing a password protected p12 through the command line as such: gnome-keyring import ~/Desktop/client.p12 You will either get the error: gnome-keyring: couldn't find any place to import files or on 12.04: --- amohr@ubuntu:~$ gnome-keyring import ~/Desktop/client.key (gnome-keyring:4195): Gcr-CRITICAL **: gcr_pkcs11_get_modules: assertion `initialized_modules' failed (gnome-keyring:4195): Gcr-CRITICAL **: populate_slots: assertion `modules' failed (gnome-keyring:4195): Gcr-CRITICAL **: state_initialize_pin: assertion `self->pv->slot' failed ** Gcr:ERROR:gcr-importer.c:828:gcr_importer_import: assertion failed: (!self->pv->processing) Aborted (core dumped) --- Furthermore, if you go to seahorse, and attempt to add a "Private key" you'll note the "Stored at" is blank and it won't let you create a new private key. This used to work in 10.04. It appears there's a work-around in 13.04 by first unlocking the "Gnome2 Key Storage" (which incidentally throws an error about you already being logged in, but then unlocks it), and then doing File->Import from seahorse and importing to the Gnome2 key storage area. This trick doesn't work in 12.04 because if you try to import the p12 or they key it says its an invalid format :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1254946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113679] Re: Close session failed when burning 25gb blu-ray disc
** Changed in: dvd+rw-tools (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dvd+rw-tools in Ubuntu. https://bugs.launchpad.net/bugs/1113679 Title: Close session failed when burning 25gb blu-ray disc Status in dvd+rw-tools package in Ubuntu: Fix Released Status in dvd+rw-tools source package in Trusty: Fix Committed Status in dvd+rw-tools source package in Utopic: Won't Fix Status in dvd+rw-tools package in Debian: Fix Released Bug description: [Impact] * All users of growisofs (including users of frontends like k3b) get a spurious IO error at the end of writing a blu-ray BD-R medium * The fix is very simple and just a single line, details in http://lists.alioth.debian.org/pipermail/debburn-devel/2013-June/000924.html [Test Case] * you need a blu-ray BD-R medium and e.g. k3b * create a data project with e.g. 22GB * write using a blank BD-R * observe a IO error at the end of the write (the disc is fine though) * install growisofs from -updates * repeat the test and verify that there is no write error this time * bonus points for checking "verify written data" in the burn dialog of k3b [Regression Potential] * its already showing a IO error at the end, its unlikely that the patch makes it worse I create an image burn and then try to use growisofs to burn it to a 25GB blu-ray recordable disc using Ubuntu 13.04 (64-bit). rick@rick-CT14:~/Downloads$ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 rick@rick-CT14:~/Downloads$ apt-cache policy growisofs growisofs: Installed: 7.1-10build1 Candidate: 7.1-10build1 Version table: *** 7.1-10build1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I expected to burn a blu-ray 25GB disc without error messages and without corrupted files. I get a "close session failed" error message with posssibly corrupted files. Even if the files aren't corrupted, it is disconcerting. I followed the procedure outlined by Steve Litt: http://www.troubleshooters.com/linux/blu-ray-backup.htm # Create empty file truncate --size=24GB mybr2.udf # Create udf file system mkudffs mybr2.udf # Mount file system sudo mount -oloop,rw mybr2.udf /mnt/test # Change ownership sudo chown rick.rick /mnt/test # Copy files into the mounted file system # Unmount file system sudo umount /dev/loop1 Everything above works as expected without problems. # Burn to blank blu ray (25GB) empty disc growisofs -speed=4 -Z /dev/sr0=mybr2.udf Here is the key part at the end: 23549509632/240 (98.1%) @1.7x, remaining 0:55 RBU 100.0% UBU 62.9% 23579131904/240 (98.2%) @2.0x, remaining 0:52 RBU 100.0% UBU 59.7% 23603773440/240 (98.3%) @1.6x, remaining 0:49 RBU 100.0% UBU 60.8% 23631527936/240 (98.5%) @1.9x, remaining 0:45 RBU 100.0% UBU 59.7% 23658037248/240 (98.6%) @1.8x, remaining 0:42 RBU 100.0% UBU 61.8% 23682940928/240 (98.7%) @1.7x, remaining 0:39 RBU 99.9% UBU 57.5% 23712301056/240 (98.8%) @2.0x, remaining 0:35 RBU 100.0% UBU 65.1% 23736418304/240 (98.9%) @1.6x, remaining 0:32 RBU 100.0% UBU 60.8% 23765581824/240 (99.0%) @1.9x, remaining 0:28 RBU 100.0% UBU 60.8% 23790682112/240 (99.1%) @1.7x, remaining 0:25 RBU 100.0% UBU 61.8% 23820435456/240 (99.3%) @2.0x, remaining 0:22 RBU 100.0% UBU 57.5% 23844945920/240 (99.4%) @1.6x, remaining 0:19 RBU 100.0% UBU 59.7% 23872045056/240 (99.5%) @1.8x, remaining 0:15 RBU 100.0% UBU 53.2% 23899209728/240 (99.6%) @1.8x, remaining 0:12 RBU 100.0% UBU 66.1% 23924441088/240 (99.7%) @1.7x, remaining 0:09 RBU 100.0% UBU 43.5% 23953473536/240 (99.8%) @1.9x, remaining 0:05 RBU 100.0% UBU 60.8% 23979655168/240 (99.9%) @1.7x, remaining 0:02 RBU 59.0% UBU 45.7% builtin_dd: 11718752*2KB out @ average 1.8x4390KBps /dev/sr0: flushing cache /dev/sr0: closing track /dev/sr0: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error /dev/sr0: reloading tray rick@rick-CT14:/media/rick/video$ The resulting blu-ray disc has the same total number of bytes as the file system. I haven't found any bad files on the disc. I've tried using k3b which "sort of" works but also has problems closing the disc (and in some cases some files are corrupted or bad). I've used the demo version of Nero for Linux on the same system - it creates a blu- ray disc without reporting any errors or problems. I'd rather not have to depend on proprietary software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "
THANKS! This "gaffer-tape" solution resolved the issue for me in 15.10 and AFAIK caused no adverse effects. -- 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/1273524 Title: LXDE guest session shows error message "no session for pid " Status in One Hundred Papercuts: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxsession package in Ubuntu: Triaged Bug description: EXPECTED RESULTS: Log into guest session with no error messages. ACTUAL RESULTS: Upon log in to guest session, an error "no session for pid " is printed. STEPS TO REPRODUCE: 1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual hardware, log into guest session. 2. After being logged in, see error message. AFFECTED VERSIONS: lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=Lubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881433] Re: Mouse wheel doesn't scroll in 'less' pager in VTE-based terminals
** Summary changed: - Mouse wheel doesn't scroll in 'less' pager in lxterminal + Mouse wheel doesn't scroll in 'less' pager in VTE-based terminals -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/881433 Title: Mouse wheel doesn't scroll in 'less' pager in VTE-based terminals Status in lxterminal package in Ubuntu: Fix Released Status in rxvt-unicode package in Ubuntu: Invalid Status in stjerm package in Ubuntu: Fix Released Status in vte package in Ubuntu: Fix Released Status in xfce4-terminal package in Ubuntu: Fix Released Status in xterm package in Ubuntu: Invalid Bug description: In Lubuntu 11.10, when using the 'less' pager in lxterminal, the mouse scroll wheel has no effect. The expected behaviour is that the mouse wheel would scroll the text up and down. $sudo dpkg -l |grep vte ii gir1.2-vte-2.901:0.28.2-0ubuntu2 ii libvte-2.90-9 1:0.28.2-0ubuntu2 ii libvte-common 1:0.28.2-0ubuntu2 ii libvte91:0.28.2-0ubuntu2 ii lxterminal 0.1.11-0ubuntu1 ii python-vte 1:0.28.2-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lxterminal 0.1.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 07:37:12 2011 InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: lxterminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxterminal/+bug/881433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573720 Title: Unencrypted private keys are insecure error reported even when key is encrypted Status in network-manager package in Ubuntu: Confirmed Bug description: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ed50d4f9-c810-4be0-b06c-8acd58015c50 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881433] Re: Mouse wheel doesn't scroll in 'less' pager in lxterminal
Took me a while to figure out how to launch stjerm, but in the end I've managed to do it and can confirm the issue is fixed for it as well (in Ubuntu 15.10). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/881433 Title: Mouse wheel doesn't scroll in 'less' pager in VTE-based terminals Status in lxterminal package in Ubuntu: Fix Released Status in rxvt-unicode package in Ubuntu: Invalid Status in stjerm package in Ubuntu: Fix Released Status in vte package in Ubuntu: Fix Released Status in xfce4-terminal package in Ubuntu: Fix Released Status in xterm package in Ubuntu: Invalid Bug description: In Lubuntu 11.10, when using the 'less' pager in lxterminal, the mouse scroll wheel has no effect. The expected behaviour is that the mouse wheel would scroll the text up and down. $sudo dpkg -l |grep vte ii gir1.2-vte-2.901:0.28.2-0ubuntu2 ii libvte-2.90-9 1:0.28.2-0ubuntu2 ii libvte-common 1:0.28.2-0ubuntu2 ii libvte91:0.28.2-0ubuntu2 ii lxterminal 0.1.11-0ubuntu1 ii python-vte 1:0.28.2-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lxterminal 0.1.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 07:37:12 2011 InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: lxterminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxterminal/+bug/881433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881433] Re: Mouse wheel doesn't scroll in 'less' pager in lxterminal
Hmm, rxvt-unicode doesn't use vte at all. You should file a new bug report for it. ** Changed in: rxvt-unicode (Ubuntu) Status: Confirmed => Invalid ** Changed in: lxterminal (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xfce4-terminal (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/881433 Title: Mouse wheel doesn't scroll in 'less' pager in VTE-based terminals Status in lxterminal package in Ubuntu: Fix Released Status in rxvt-unicode package in Ubuntu: Invalid Status in stjerm package in Ubuntu: Fix Released Status in vte package in Ubuntu: Fix Released Status in xfce4-terminal package in Ubuntu: Fix Released Status in xterm package in Ubuntu: Invalid Bug description: In Lubuntu 11.10, when using the 'less' pager in lxterminal, the mouse scroll wheel has no effect. The expected behaviour is that the mouse wheel would scroll the text up and down. $sudo dpkg -l |grep vte ii gir1.2-vte-2.901:0.28.2-0ubuntu2 ii libvte-2.90-9 1:0.28.2-0ubuntu2 ii libvte-common 1:0.28.2-0ubuntu2 ii libvte91:0.28.2-0ubuntu2 ii lxterminal 0.1.11-0ubuntu1 ii python-vte 1:0.28.2-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lxterminal 0.1.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 07:37:12 2011 InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: lxterminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxterminal/+bug/881433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1366221] Re: gnome-calculator does not show application menu anywhere
Using Unity on Ubuntu 16.04 freshly installed: jcurl@leon-ubuntu:~/Programming/SerialPortStream/dll/serialunix/build$ gnome-calculator -v gnome-calculator 3.18.3 The "dconf" tool is a workaround, but I cannot enable the menu by default. Not sure why it's "low", it's a problem for a long time (reported in other forums since 13.04). It would sure be nice to have something to make it easy to move from windows ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1366221 Title: gnome-calculator does not show application menu anywhere Status in gnome-calculator package in Ubuntu: Confirmed Bug description: gnome-calculator no longer offers, as of 14.04, an application menu. It used to be there before the upgrade, in 12.04. So switching between scientific and engineering now requires me to use dconf-editor. Note that I did check hovering menu line, application title bar, and thereabouts, to no avail. This application is now useless... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-calculator 1:3.10.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 6 01:12:00 2014 SourcePackage: gnome-calculator UpgradeStatus: Upgraded to trusty on 2014-08-29 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1366221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1322724] Re: Ubuntu One in firefox bookmarks
** Branch linked: lp:~mozillateam/firefox/firefox.xenial -- 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/1322724 Title: Ubuntu One in firefox bookmarks Status in epiphany-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Fix Released Bug description: I'm running firefox 28 which comes with Xubuntu 14.04 and noticed that there is an 'Ubuntu One' bookmark under the 'Ubuntu and Free Software links' bookmark folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1322724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881433] Re: Mouse wheel doesn't scroll in 'less' pager in lxterminal
Scrolling in lxterminal and xfce4-terminal works fine in less (in Ubuntu 15.10). ** Changed in: stjerm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/881433 Title: Mouse wheel doesn't scroll in 'less' pager in VTE-based terminals Status in lxterminal package in Ubuntu: Fix Released Status in rxvt-unicode package in Ubuntu: Invalid Status in stjerm package in Ubuntu: Fix Released Status in vte package in Ubuntu: Fix Released Status in xfce4-terminal package in Ubuntu: Fix Released Status in xterm package in Ubuntu: Invalid Bug description: In Lubuntu 11.10, when using the 'less' pager in lxterminal, the mouse scroll wheel has no effect. The expected behaviour is that the mouse wheel would scroll the text up and down. $sudo dpkg -l |grep vte ii gir1.2-vte-2.901:0.28.2-0ubuntu2 ii libvte-2.90-9 1:0.28.2-0ubuntu2 ii libvte-common 1:0.28.2-0ubuntu2 ii libvte91:0.28.2-0ubuntu2 ii lxterminal 0.1.11-0ubuntu1 ii python-vte 1:0.28.2-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lxterminal 0.1.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 25 07:37:12 2011 InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: lxterminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxterminal/+bug/881433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] [NEW] compose and dead keys stopped working in gnome terminal
Public bug reported: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: compose and dead keys stopped working in gnome terminal Status in gnome-terminal package in Ubuntu: New Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled
I read you Phoronix comment while updating my own copy from 14.04. Personal update went fine while using almost same card (HD 5750.) but was already using radeon driver. >From what I gather you were using catalyst before update. Any idea if radeon driver worked with older version? X with disabled KMS isn't supported. Your X logs essentially are from trying this. Something to try; Add "modprobe.blacklist=radeon" to GRUB command line. >From terminal; sudo modprobe radeon ; sleep 1 ; dmesg > dmesg.log If no errors startx. -- 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/1568429 Title: Radeon won't work with KMS enabled Status in xorg package in Ubuntu: New Bug description: I have a Radeon HD 5770 GPU. After upgrading to Xenial today and ensuring the xorg radeon driver was enabled, my machine will no longer boot to a usable state. After selecting default Ubuntu option from GRUB menu, both monitor lose signal input and the keyboard becomes unresponsive. Sometimes the machine will reboot on its own, most of the time I have to hard reset. If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the machine will boot but the radeon driver will not load. Attempting to load radeon driver with `sudo modprobe radeon modeset=1` after booting with modesetting off results in the same fail state explained above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds] CompositorRunning: None Date: Sat Apr 9 20:02:22 2016 DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990] InstallationDate: Installed on 2013-12-29 (832 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago) dmi.bios.date: 04/29/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0519 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Apr 9 19:49:46 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1565349] Re: No such file or directory while executing existing 64bit binary
Here is a workaround: https://bugs.launchpad.net/bugs/840998 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1565349 Title: No such file or directory while executing existing 64bit binary Status in cups-filters package in Ubuntu: Triaged Bug description: With this error, I can only find references for 32bit executables on 64bit system. This is not the case: the binary is 64bit, the interpreter and every library seems in place. ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ ./epson-escpr-wrapper bash: ./epson-escpr-wrapper: No such file or directory ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ ldd epson-escpr-wrapper linux-vdso.so.1 => (0x7ffdc3f7a000) libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 (0x7f0ce852c000) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7f0ce82ac000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0ce808e000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0ce7d85000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0ce79bb000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7f0ce777) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7f0ce743f000) libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 (0x7f0ce7233000) libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 (0x7f0ce7021000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0ce6e07000) /lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2 (0x55ed62393000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7f0ce6b35000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7f0ce6905000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7f0ce6701000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7f0ce64f6000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7f0ce629) libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 (0x7f0ce605d000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7f0ce5e4a000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7f0ce5c13000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7f0ce59e) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f0ce576) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f0ce5513000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ce530f000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7f0ce510b000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f0ce4eef000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7f0ce4ce7000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7f0ce4c61000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7f0ce4a3f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0ce4837000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0ce4614000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f0ce4333000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f0ce40c3000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7f0ce3eae000) ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ file epson-escpr-wrapper epson-escpr-wrapper: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-lsb-x86-64.so.3, for GNU/Linux 2.6.15, BuildID[sha1]=558bd286d0e69cd3994a848c7c04d09a026cc2c4, stripped ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lsb-base 9.20160110 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 2 22:16:04 2016 Dependencies: InstallationDate: Installed on 2016-03-25 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all SourcePackage: lsb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1565349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562219] Re: xinit will not work as non-root.
«sudo chmod 0660 /dev/tty*» worked for me until reboot. Changing permission in udev rules for tty to 0660 from 0620 could be a temporary fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinit in Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: xinit will not work as non-root. Status in xinit package in Ubuntu: Confirmed Bug description: When attempting to run xinit or startx after upgrading from 14.04 to 16.04 it will not work. There seems to be some sort of permission issue. I have seen another person with this issue as well here: http://askubuntu.com/questions/749370/ubuntu-16-04-xf86openconsole- cannot-open-virtual-console-2?newreg=ba376d7a182d44608ed4675346b1ed74 An example is when attempting to launch kodi, which worked prior to the upgrade: xinit /usr/bin/kodi --standalone -- -nocursor :0 X.Org X Server 1.18.1 Release Date: 2016-02-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.13.0-79-generic x86_64 Ubuntu Current Operating System: Linux hostname 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text Build Date: 11 March 2016 07:43:21AM xorg-server 2:1.18.1-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/arch/.local/share/xorg/Xorg.0.log", Time: Fri Mar 25 20:14:07 2016 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied) (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/arch/.local/share/xorg/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused I have tried numerous workarounds including reinstalling xorg, removing all x-related files in my profile, and creating a new user. Unfortunately none of these worked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xinit 1.3.4-3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 25 20:14:18 2016 DistUpgraded: 2016-03-25 09:16:37,728 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201412181801~ubuntu14.04.1, 3.13.0-83-generic, x86_64: installed EcryptfsInUse: Yes ExecutablePath: /usr/bin/xinit GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0402] InstallationDate: Installed on 2014-12-14 (467 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text SourcePackage: xinit UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H97M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
I have upgraded to Xenial and I can no longer reproduce the original bug. I can only assume it was something in gtk+ this has been fixed in Xenial. The fact that when it happened the jobs stuck in the queue unless deleted with the only evidence that anything was amiss being the lack of print output and a message in the error log that was only available if debug mode was switched on. Running the xenial printer- driver-hpcups source on my Wily system still showed showed the bug. I am happy to run a local patched version on Xenial. So as far as I am concerned you can either let this bug time out or mark it as invalid. If anyone wants to raise an SRU it is up to them. That is a learning curve I do not want to experience. Thanks for your time. Roger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work
[Desktop-packages] [Bug 1573326] Re: package nvidia-340 340.96-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573326 Title: package nvidia-340 340.96-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.96-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Apr 21 20:16:03 2016 DistUpgraded: 2016-04-21 16:52:37,517 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-340, 340.96, 4.4.0-21-generic, x86_64: installed vboxhost, 5.0.16, 3.19.0-58-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-21-generic, x86_64: installed ErrorMessage: subprocess installed post-installation script returned error exit status 30 GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 860M] [17aa:3978] InstallationDate: Installed on 2016-01-21 (91 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO 20349 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/vg.caroline-lv.caroline.root ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.96-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) dmi.bios.date: 01/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN36WW(V2.00) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN36WW(V2.00):bd01/12/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 21 20:05:41 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18514 vendor SDC xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565349] Re: No such file or directory while executing existing 64bit binary
After installing a clean Ubuntu 16.04 and trying to install the deb package and then apt -f install to get the missing dependencies, I cannot install the printer driver or connect to my printer anymore. This does still work in Ubuntu 15.10 though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1565349 Title: No such file or directory while executing existing 64bit binary Status in cups-filters package in Ubuntu: Triaged Bug description: With this error, I can only find references for 32bit executables on 64bit system. This is not the case: the binary is 64bit, the interpreter and every library seems in place. ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ ./epson-escpr-wrapper bash: ./epson-escpr-wrapper: No such file or directory ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ ldd epson-escpr-wrapper linux-vdso.so.1 => (0x7ffdc3f7a000) libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 (0x7f0ce852c000) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7f0ce82ac000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0ce808e000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0ce7d85000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0ce79bb000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7f0ce777) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7f0ce743f000) libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 (0x7f0ce7233000) libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 (0x7f0ce7021000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0ce6e07000) /lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2 (0x55ed62393000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7f0ce6b35000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7f0ce6905000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7f0ce6701000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7f0ce64f6000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7f0ce629) libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 (0x7f0ce605d000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7f0ce5e4a000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7f0ce5c13000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7f0ce59e) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f0ce576) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f0ce5513000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0ce530f000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7f0ce510b000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f0ce4eef000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7f0ce4ce7000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7f0ce4c61000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7f0ce4a3f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0ce4837000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0ce4614000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f0ce4333000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f0ce40c3000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7f0ce3eae000) ignazio@ignazio-HP-ZBook-17:/opt/epson-inkjet-printer-escpr/cups/lib/filter$ file epson-escpr-wrapper epson-escpr-wrapper: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-lsb-x86-64.so.3, for GNU/Linux 2.6.15, BuildID[sha1]=558bd286d0e69cd3994a848c7c04d09a026cc2c4, stripped ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lsb-base 9.20160110 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 2 22:16:04 2016 Dependencies: InstallationDate: Installed on 2016-03-25 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all SourcePackage: lsb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1565349/+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 1559304] Re: nvidia 361 drivers cause unresponsive machine
Same issue on Dell XPS 15-9530 updated from 14.04 to 16.04. -- 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/1559304 Title: nvidia 361 drivers cause unresponsive machine Status in xorg package in Ubuntu: Confirmed Bug description: Running Ubuntu Gnome 16.04 Beta1. Installing the proprietary drivers (either the tested or the updates) one results in: the splash screen goes away, revealing all the console output (with mostly green OKs) and the console log-in. This whole thing then flashes on and off and the system seems a little too upset to receive keyboard input. There is no mouse. The only way out is a hard reset, or if networking got started you can sometimes SSH in and issue a shutdown that way. The Nvidia driver is 361.28-0ubuntu1 It's a Dell xps-15 9550 with the UHD 4k screen. *-display description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:127 memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915_bpo latency=0 resources: irq:126 memory:db00-dbff memory:7000-7fff ioport:f000(size=64) To restore the system I have to boot to root console from the grub menu and then remove the nvidia stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:31:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. 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.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Desktop-packages] [Bug 1573728] [NEW] Files opened with gedit on command line no longer open within the existing gedit session
Public bug reported: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit package in Ubuntu: New Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1559304] Re: nvidia 361 drivers cause unresponsive machine
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1559304 Title: nvidia 361 drivers cause unresponsive machine Status in xorg package in Ubuntu: Confirmed Bug description: Running Ubuntu Gnome 16.04 Beta1. Installing the proprietary drivers (either the tested or the updates) one results in: the splash screen goes away, revealing all the console output (with mostly green OKs) and the console log-in. This whole thing then flashes on and off and the system seems a little too upset to receive keyboard input. There is no mouse. The only way out is a hard reset, or if networking got started you can sometimes SSH in and issue a shutdown that way. The Nvidia driver is 361.28-0ubuntu1 It's a Dell xps-15 9550 with the UHD 4k screen. *-display description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:127 memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915_bpo latency=0 resources: irq:126 memory:db00-dbff memory:7000-7fff ioport:f000(size=64) To restore the system I have to boot to root console from the grub menu and then remove the nvidia stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:31:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. 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.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile:
[Desktop-packages] [Bug 1411728] Re: Growisofs fails to burn DVD+R DL multisesion above 4.5Gb if argument -M /dev/device is before -use-the-force-luke=4gms in argument list.
** Bug watch removed: Debian Bug tracker #713016 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dvd+rw-tools in Ubuntu. https://bugs.launchpad.net/bugs/1411728 Title: Growisofs fails to burn DVD+R DL multisesion above 4.5Gb if argument -M /dev/device is before -use-the-force-luke=4gms in argument list. Status in dvd+rw-tools package in Ubuntu: New Bug description: Growisofs uses no_4gb_check flag before parsing -use-the-force- luke=4gms, if -M /dev/device is before it on argument list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1411728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113679] Re: Close session failed when burning 25gb blu-ray disc
** Bug watch added: Debian Bug tracker #713016 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 ** Also affects: dvd+rw-tools (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dvd+rw-tools in Ubuntu. https://bugs.launchpad.net/bugs/1113679 Title: Close session failed when burning 25gb blu-ray disc Status in dvd+rw-tools package in Ubuntu: Fix Released Status in dvd+rw-tools source package in Trusty: Fix Committed Status in dvd+rw-tools source package in Utopic: Won't Fix Status in dvd+rw-tools package in Debian: Unknown Bug description: [Impact] * All users of growisofs (including users of frontends like k3b) get a spurious IO error at the end of writing a blu-ray BD-R medium * The fix is very simple and just a single line, details in http://lists.alioth.debian.org/pipermail/debburn-devel/2013-June/000924.html [Test Case] * you need a blu-ray BD-R medium and e.g. k3b * create a data project with e.g. 22GB * write using a blank BD-R * observe a IO error at the end of the write (the disc is fine though) * install growisofs from -updates * repeat the test and verify that there is no write error this time * bonus points for checking "verify written data" in the burn dialog of k3b [Regression Potential] * its already showing a IO error at the end, its unlikely that the patch makes it worse I create an image burn and then try to use growisofs to burn it to a 25GB blu-ray recordable disc using Ubuntu 13.04 (64-bit). rick@rick-CT14:~/Downloads$ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 rick@rick-CT14:~/Downloads$ apt-cache policy growisofs growisofs: Installed: 7.1-10build1 Candidate: 7.1-10build1 Version table: *** 7.1-10build1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I expected to burn a blu-ray 25GB disc without error messages and without corrupted files. I get a "close session failed" error message with posssibly corrupted files. Even if the files aren't corrupted, it is disconcerting. I followed the procedure outlined by Steve Litt: http://www.troubleshooters.com/linux/blu-ray-backup.htm # Create empty file truncate --size=24GB mybr2.udf # Create udf file system mkudffs mybr2.udf # Mount file system sudo mount -oloop,rw mybr2.udf /mnt/test # Change ownership sudo chown rick.rick /mnt/test # Copy files into the mounted file system # Unmount file system sudo umount /dev/loop1 Everything above works as expected without problems. # Burn to blank blu ray (25GB) empty disc growisofs -speed=4 -Z /dev/sr0=mybr2.udf Here is the key part at the end: 23549509632/240 (98.1%) @1.7x, remaining 0:55 RBU 100.0% UBU 62.9% 23579131904/240 (98.2%) @2.0x, remaining 0:52 RBU 100.0% UBU 59.7% 23603773440/240 (98.3%) @1.6x, remaining 0:49 RBU 100.0% UBU 60.8% 23631527936/240 (98.5%) @1.9x, remaining 0:45 RBU 100.0% UBU 59.7% 23658037248/240 (98.6%) @1.8x, remaining 0:42 RBU 100.0% UBU 61.8% 23682940928/240 (98.7%) @1.7x, remaining 0:39 RBU 99.9% UBU 57.5% 23712301056/240 (98.8%) @2.0x, remaining 0:35 RBU 100.0% UBU 65.1% 23736418304/240 (98.9%) @1.6x, remaining 0:32 RBU 100.0% UBU 60.8% 23765581824/240 (99.0%) @1.9x, remaining 0:28 RBU 100.0% UBU 60.8% 23790682112/240 (99.1%) @1.7x, remaining 0:25 RBU 100.0% UBU 61.8% 23820435456/240 (99.3%) @2.0x, remaining 0:22 RBU 100.0% UBU 57.5% 23844945920/240 (99.4%) @1.6x, remaining 0:19 RBU 100.0% UBU 59.7% 23872045056/240 (99.5%) @1.8x, remaining 0:15 RBU 100.0% UBU 53.2% 23899209728/240 (99.6%) @1.8x, remaining 0:12 RBU 100.0% UBU 66.1% 23924441088/240 (99.7%) @1.7x, remaining 0:09 RBU 100.0% UBU 43.5% 23953473536/240 (99.8%) @1.9x, remaining 0:05 RBU 100.0% UBU 60.8% 23979655168/240 (99.9%) @1.7x, remaining 0:02 RBU 59.0% UBU 45.7% builtin_dd: 11718752*2KB out @ average 1.8x4390KBps /dev/sr0: flushing cache /dev/sr0: closing track /dev/sr0: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error /dev/sr0: reloading tray rick@rick-CT14:/media/rick/video$ The resulting blu-ray disc has the same total number of bytes as the file system. I haven't found any bad files on the disc. I've tried using k3b which "sort of" works but also has problems closing the disc (and in some cases some files are corrupted or bad). I've used the demo version of Nero for Linux on the same system - it creates a blu- ray disc without reporting any errors or problems. I'd rather not have to depend on
[Desktop-packages] [Bug 1573720] [NEW] Unencrypted private keys are insecure error reported even when key is encrypted
Public bug reported: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ed50d4f9-c810-4be0-b06c-8acd58015c50 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573720 Title: Unencrypted private keys are insecure error reported even when key is encrypted Status in network-manager package in Ubuntu: New Bug description: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1
[Desktop-packages] [Bug 1573338] Re: can't install google chrome browser on ubuntu gnome 16.04
Did a fresh install of Ubuntu 16.04 and now I cant install sublime-text or Ubuntu tweak. I get this message saying "This software comes from a 3rd party and and may contain non-free components" The install button greys out and there is nothing else I can do. Is this a bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nlpsolver in Ubuntu. https://bugs.launchpad.net/bugs/1573338 Title: can't install google chrome browser on ubuntu gnome 16.04 Status in nlpsolver package in Ubuntu: Confirmed Bug description: 1. refresh install ubuntu gnome 16.04 2. download google chrome from google chrome website. The file name is google-chrome-stable_current_amd64.deb 3. double click the file 4. before click install, there is a blue bar said "This software comes from a 3rd party and may contain non-free component and there are two grey icons above this bar. left grey icon has words "non-free", right grey icon has words "3rd party" 5. click install. the right grey icon with words "3rd party" has gone. Install button flesh and nothing happened 6. click install. nothing happened except install button flesh again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nlpsolver/+bug/1573338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294899] Re: Import saved VPN connection has been Recently Broken
This is broken again in Ubuntu 16.04: https://bugs.launchpad.net/network-manager/+bug/1573430 VPNC option is missing too: https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1573424 ** Tags added: xenial -- 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/1294899 Title: Import saved VPN connection has been Recently Broken Status in OpenVPN: Invalid Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-applet source package in Trusty: Fix Released Status in network-manager-openvpn source package in Trusty: Invalid Status in network-manager-applet source package in Utopic: Fix Released Status in network-manager-openvpn source package in Utopic: Invalid Status in network-manager-openvpn package in Debian: Fix Released Bug description: SRU Request: [Impact] Attempting to import a saved VPN connection file results in a segault. This is regression in Ubuntu 14.04 that worked correctly in previous versions. [Test Case] 1- install network-manager-openvpn and network-manager-openvpn-gnome 2- from the network-manager indicator, click on Edit Connections 3- Click on Add 4- Select Import a saved VPN configuration, and open the file in comment #28 Expected results: a window should appear with the imported information Current results: network-manager's connection editor segfaults [Regression potential] This SRU simply adds a couple of missing sections to the 11-user-connections.patch patch that went missing. If the fix is broken, either the vpn files won't import, or creating a new vpn connection could break completely. Original description: I believe recent changes have broken network-manager-openvpn feature that allows you to "Import saved VPN connection". I've tested this feature with bundles that I've definitely imported successfully in the past. Now, not only does it not import, but it gives absolutely no feedback at all; the window just disappears as though I didn't just ask it to import a VPN.conf file. The folder (I'm importing the .conf file from) includes all the necessary supporting files. I'm very sure this is not a user error on my part. I've done this several times in the past and I'm certain that the files (that are currently being ignored without dialog feedback) are exactly the same as they were when I was able to import successfully a few weeks ago. I've tested this on multiple machines that have Ubuntu 14.04 installed and fully updated. And, even if the files were indeed corrupted (which I'm certain they are not), the fact that the UI just disappears, instead of showing an error, is a bug within itself. Also, I'd like to point out, that I was able to set up this VPN bundle manually. The point of this bug is to report that the ability to import via .conf files (so that you don't have to set things manually) has recently became nonfunctional. To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1294899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288182]
So 8 years passed and no fix for this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Confirmed Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562219] Re: xinit will not work as non-root.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xinit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinit in Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: xinit will not work as non-root. Status in xinit package in Ubuntu: Confirmed Bug description: When attempting to run xinit or startx after upgrading from 14.04 to 16.04 it will not work. There seems to be some sort of permission issue. I have seen another person with this issue as well here: http://askubuntu.com/questions/749370/ubuntu-16-04-xf86openconsole- cannot-open-virtual-console-2?newreg=ba376d7a182d44608ed4675346b1ed74 An example is when attempting to launch kodi, which worked prior to the upgrade: xinit /usr/bin/kodi --standalone -- -nocursor :0 X.Org X Server 1.18.1 Release Date: 2016-02-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.13.0-79-generic x86_64 Ubuntu Current Operating System: Linux hostname 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text Build Date: 11 March 2016 07:43:21AM xorg-server 2:1.18.1-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/arch/.local/share/xorg/Xorg.0.log", Time: Fri Mar 25 20:14:07 2016 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied) (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/arch/.local/share/xorg/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused I have tried numerous workarounds including reinstalling xorg, removing all x-related files in my profile, and creating a new user. Unfortunately none of these worked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xinit 1.3.4-3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 25 20:14:18 2016 DistUpgraded: 2016-03-25 09:16:37,728 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201412181801~ubuntu14.04.1, 3.13.0-83-generic, x86_64: installed EcryptfsInUse: Yes ExecutablePath: /usr/bin/xinit GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0402] InstallationDate: Installed on 2014-12-14 (467 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text SourcePackage: xinit UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H97M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1537913] Re: Active APN is not selected
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
** Tags added: system-apps-11
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1537913
Title:
Active APN is not selected
Status in Canonical System Image:
In Progress
Status in network-manager package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
In Progress
Bug description:
The APN panel shows 3 APNs but the active APN is not selected in the UI
MX4 running rc-proposed 230
A krillin running ota 8.5 shows a selected APN
The settings log contains this when viewing the page
2016-01-25 16:06:34,484 - WARNING -
file:///usr/share/ubuntu/settings/system/qml-plugins/cellular/apn_manager.js:50:
Error: Unknown context type
You can see ATT Phone should be selected
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
IPv6.Settings = { }
Settings = { }
Protocol = ip
AccessPointName = nxtgenphone
Type = internet
AuthenticationMethod = chap
MessageProxy = proxy.mobile.att.net:80
Name = ATT Nextgenphone
Username =
Active = 0
Preferred = 0
MessageCenter = http://mmsc.mobile.att.net
[ /ril_0/context2 ]
Password =
IPv6.Settings = { }
Settings = { Gateway=10.244.204.71 Method=static
Address=10.244.204.71 Proxy=172.26.39.1 Interface=ccmni0 ProxyPort=80
DomainNameServers=172.26.38.1,172.26.38.2, Netmask=255.255.255.0 }
Protocol = ip
AccessPointName = phone
Type = internet
AuthenticationMethod = chap
MessageProxy = proxy.mobile.att.net:80
Name = ATT Phone
Username =
Active = 1
Preferred = 0
MessageCenter = http://mmsc.mobile.att.net
[ /ril_0/context3 ]
Password =
IPv6.Settings = { }
Settings = { }
Protocol = ip
AccessPointName = wap.cingular
Type = internet
AuthenticationMethod = chap
MessageProxy = wireless.cingular.com
Name = ATT WAP
Username =
Active = 0
Preferred = 0
MessageCenter = http://mmsc.cingular.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537913/+subscriptions
--
Mailing list: https://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 1573338] Re: can't install google chrome browser on ubuntu gnome 16.04
Here might be the reason even through I'm not sure. My PC has been upgraded with new motherboard two years ago to replace the motherboard before 2010 which doesn't have UEFI. But the only system on HD was Ubuntu 14.04.When I try to boot my PC on Thursday with Ubuntu 16.04, I can't boot it. I finally found out that the BIOS doesn't set to boot in UEFI CD mode. After put UEFI CD boot mode on the top option, I can boot Ubuntu 16.04 from CD. Now here is the question:1. I don't want to wipe out all HD. I still like to install new system in prepartition / with 20GB, still like to keep my /home directory. I've been installed like this for several times. If my bios is boot from UEFI mode, i need to do some extra works to set UEFI partition. Should I do it?2. If I turn off UEFI secure boot, can I boot my CD from legacy bios mode? Thanks,Hong From: Benjamin <1573...@bugs.launchpad.net> To: hank...@yahoo.com Sent: Friday, April 22, 2016 6:09 AM Subject: [Bug 1573338] Re: can't install google chrome browser on ubuntu gnome 16.04 Did a fresh install of Ubuntu 16.04 and tried to install the usual apps, i.a. Chrome. Installation via Software failed without any message. However, dpkg -i complained about libindicator1 being missing. apt-get revealed that libindicator1 is not in the repos, only libindicator3 and libindicator7. This is a severe regression, since Chrome is currently the only way of using (paid-for!) services like Netflix. Is there a way around this? Who is responsible for a solution? Canonical or Google? btw, Chrome works fine on another of my machines running 16.04 RC. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1573338 Title: can't install google chrome browser on ubuntu gnome 16.04 Status in nlpsolver package in Ubuntu: Confirmed Bug description: 1. refresh install ubuntu gnome 16.04 2. download google chrome from google chrome website. The file name is google-chrome-stable_current_amd64.deb 3. double click the file 4. before click install, there is a blue bar said "This software comes from a 3rd party and may contain non-free component and there are two grey icons above this bar. left grey icon has words "non-free", right grey icon has words "3rd party" 5. click install. the right grey icon with words "3rd party" has gone. Install button flesh and nothing happened 6. click install. nothing happened except install button flesh again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nlpsolver/+bug/1573338/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nlpsolver in Ubuntu. https://bugs.launchpad.net/bugs/1573338 Title: can't install google chrome browser on ubuntu gnome 16.04 Status in nlpsolver package in Ubuntu: Confirmed Bug description: 1. refresh install ubuntu gnome 16.04 2. download google chrome from google chrome website. The file name is google-chrome-stable_current_amd64.deb 3. double click the file 4. before click install, there is a blue bar said "This software comes from a 3rd party and may contain non-free component and there are two grey icons above this bar. left grey icon has words "non-free", right grey icon has words "3rd party" 5. click install. the right grey icon with words "3rd party" has gone. Install button flesh and nothing happened 6. click install. nothing happened except install button flesh again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nlpsolver/+bug/1573338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573699] [NEW] Select region during install process cause crash
Public bug reported: When install the system, on the step which system asks me to select a region (default is Los Angeles for me). And I tried to change to San Francisco, but when I type "San", the installer freezes and cannot click anywhere. I waited for a long time but doesn't work either so has to re- install. I can change region with no problem after installation is completed. But I guess many users are trying to change region while install but most of them don't know how to file a bug (which takes me 30 minutes to find the correct way!!! Got to be easier if Ubuntu wants to replace Windows) Please make the fix. Thanks. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573699 Title: Select region during install process cause crash Status in gnome-terminal package in Ubuntu: New Bug description: When install the system, on the step which system asks me to select a region (default is Los Angeles for me). And I tried to change to San Francisco, but when I type "San", the installer freezes and cannot click anywhere. I waited for a long time but doesn't work either so has to re-install. I can change region with no problem after installation is completed. But I guess many users are trying to change region while install but most of them don't know how to file a bug (which takes me 30 minutes to find the correct way!!! Got to be easier if Ubuntu wants to replace Windows) Please make the fix. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573695] [NEW] System update broken
Public bug reported: System update easily broken. Here is the procedure. And I believe this may happen to many Chinese users I downloaded Sougou Pinyin (the most popular Chinese input app) from official website which is released the same date 16.04 is released and claims it supports 16.04. I downloaded the file sogoupinyin_2.0.0.0072_amd64.deb, and double click to install. Then Ubuntu Software window pops up. And I click "install", then no response. And I clicked again, this time a "Waiting to install" icon appears on the sidebar but never finishes. Then I turned off my PC and turn it back on again, now I see a red icon appears on top of top sidebar near time which indicates "An error occurred. Please run Package Manager ..." And since then I am not able to install any update. I believe this is a blocker bug. And I have to re-install the system again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 08:56:19 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573695 Title: System update broken Status in gnome-terminal package in Ubuntu: New Bug description: System update easily broken. Here is the procedure. And I believe this may happen to many Chinese users I downloaded Sougou Pinyin (the most popular Chinese input app) from official website which is released the same date 16.04 is released and claims it supports 16.04. I downloaded the file sogoupinyin_2.0.0.0072_amd64.deb, and double click to install. Then Ubuntu Software window pops up. And I click "install", then no response. And I clicked again, this time a "Waiting to install" icon appears on the sidebar but never finishes. Then I turned off my PC and turn it back on again, now I see a red icon appears on top of top sidebar near time which indicates "An error occurred. Please run Package Manager ..." And since then I am not able to install any update. I believe this is a blocker bug. And I have to re-install the system again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 08:56:19 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
