[Desktop-packages] [Bug 2019016] Re: nvidia_desktop_pre_installation_hook raises on package names with suffixes
Hi Alberto, That seems to have worked for me. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2019016 Title: nvidia_desktop_pre_installation_hook raises on package names with suffixes Status in ubuntu-drivers-common package in Ubuntu: New Bug description: The function nvidia_desktop_pre_installation_hook in /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py on Ubuntu 22.04.2 LTS assumes that the driver package name ends with the driver version as the suffix. However this does not account for the '-open' drivers. The following code from that function is at fault: ``` # Enable KMS if nvidia >= 470 for package_name in to_install: if package_name.startswith('nvidia-driver-'): try: version = int(package_name.split('-')[-1]) # <--- This here with_nvidia_kms = version >= 470 except ValueError: pass finally: with_nvidia_kms = version >= 470 # <-- And this here, too, which will never succeed. ``` The line `version = int(package_name.split('-')[-1])` assumes a package name like `nvidia-driver-530` rather than `nvidia- driver-530-open`, however `nvidia-driver-530-open` is the autoselected package for my install. This code could be fixed by switching to a regex, or else retrying with index -2 rather than index -1. Also, the `finally` clause will always fail-- there should only ever be one matching `nvidia-driver-` prefixed package, and if that raises a ValueError, then `version` will not be set, raising an UnboundLocalError. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-drivers-common 1:0.9.6.1 [modified: usr/lib/python3/dist-packages/UbuntuDrivers/detect.py] ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 9 10:47:07 2023 InstallationDate: Installed on 2022-08-20 (261 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2019016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019016] [NEW] nvidia_desktop_pre_installation_hook raises on package names with suffixes
Public bug reported: The function nvidia_desktop_pre_installation_hook in /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py on Ubuntu 22.04.2 LTS assumes that the driver package name ends with the driver version as the suffix. However this does not account for the '-open' drivers. The following code from that function is at fault: ``` # Enable KMS if nvidia >= 470 for package_name in to_install: if package_name.startswith('nvidia-driver-'): try: version = int(package_name.split('-')[-1]) # <--- This here with_nvidia_kms = version >= 470 except ValueError: pass finally: with_nvidia_kms = version >= 470 # <-- And this here, too, which will never succeed. ``` The line `version = int(package_name.split('-')[-1])` assumes a package name like `nvidia-driver-530` rather than `nvidia-driver-530-open`, however `nvidia-driver-530-open` is the autoselected package for my install. This code could be fixed by switching to a regex, or else retrying with index -2 rather than index -1. Also, the `finally` clause will always fail-- there should only ever be one matching `nvidia-driver-` prefixed package, and if that raises a ValueError, then `version` will not be set, raising an UnboundLocalError. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-drivers-common 1:0.9.6.1 [modified: usr/lib/python3/dist-packages/UbuntuDrivers/detect.py] ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 9 10:47:07 2023 InstallationDate: Installed on 2022-08-20 (261 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2019016 Title: nvidia_desktop_pre_installation_hook raises on package names with suffixes Status in ubuntu-drivers-common package in Ubuntu: New Bug description: The function nvidia_desktop_pre_installation_hook in /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py on Ubuntu 22.04.2 LTS assumes that the driver package name ends with the driver version as the suffix. However this does not account for the '-open' drivers. The following code from that function is at fault: ``` # Enable KMS if nvidia >= 470 for package_name in to_install: if package_name.startswith('nvidia-driver-'): try: version = int(package_name.split('-')[-1]) # <--- This here with_nvidia_kms = version >= 470 except ValueError: pass finally: with_nvidia_kms = version >= 470 # <-- And this here, too, which will never succeed. ``` The line `version = int(package_name.split('-')[-1])` assumes a package name like `nvidia-driver-530` rather than `nvidia- driver-530-open`, however `nvidia-driver-530-open` is the autoselected package for my install. This code could be fixed by switching to a regex, or else retrying with index -2 rather than index -1. Also, the `finally` clause will always fail-- there should only ever be one matching `nvidia-driver-` prefixed package, and if that raises a ValueError, then `version` will not be set, raising an UnboundLocalError. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-drivers-common 1:0.9.6.1 [modified: usr/lib/python3/dist-packages/UbuntuDrivers/detect.py] ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 9 10:47:07 2023 InstallationDate: Installed on 2022-08-20 (261 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2019016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Same for me. I try to add workaroung in #22 but May 2 15:02:12 KLINGON wpa_supplicant[10086]: SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error May 2 15:02:12 KLINGON wpa_supplicant[10086]: OpenSSL: openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 90851]
it is no longer in right-click menu. bug is fixed for good. -- 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/90851 Title: Firefox does not set KDE wallpaper Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Using firefox in KDE right click on an image and choose set as background, nothing happens for kde but the gconf setting is done. The same goes for changing the desktop background color. Need to change ~/.kde/share/config/kdesktoprc from setDesktopWallpaper.xul/js. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/90851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866070] Re: extension not compatible with gnome-shell 3.36 (Focal Fossa)
Is it intentional, that package "gnome-shell-extension-prefs" package is no longer being installed automatically in 20.04/Gnome Shell 3.36? ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866070 Title: extension not compatible with gnome-shell 3.36 (Focal Fossa) Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-dash-to-panel source package in Focal: Confirmed Bug description: This extension is not working anymore with the latest version of gnome-shell available in Focal. Fixed upstream by: https://github.com/home-sweet-gnome/dash-to- panel/commit/32410a7e4178d871d6c799ad9da71d3614bdb9e9 Error log: JS ERROR: Extension dash-to-pa...@jderose9.github.com: Error: second argument to Lang.bind() must be a function, not undefined bind@resource:///org/gnome/gjs/modules/lang.js:75:15 _init@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/appIcons.js:1593:43 C@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/utils.js line 76 > eval:1:52 _init@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/taskbar.js:195:37 C@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/utils.js line 76 > eval:1:52 enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panel.js:260:24 _createPanel@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:290:9 enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:74:29 _enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:94:5 enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:62:5 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:161:13 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:312:21 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:545:13 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:520:9 _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:554:13 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:585:13 init@resource:///org/gnome/shell/ui/extensionSystem.js:55:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:245:5 start@resource:///org/gnome/shell/ui/main.js:141:5 @:1:31 Usage of indicator.indicators is deprecated for Indicator get indicators@resource:///org/gnome/shell/ui/panelMenu.js:213:25 enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panel.js:208:13 _createPanel@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:290:9 enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:74:29 _enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:94:5 enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:62:5 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:161:13 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:312:21 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:545:13 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:520:9 _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:554:13 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:585:13 init@resource:///org/gnome/shell/ui/extensionSystem.js:55:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:245:5 start@resource:///org/gnome/shell/ui/main.js:141:5 @:1:31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site
I realize the issue reported was related to 18.04, but I am also having this same issue on 18.10. -- 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/1760349 Title: Cannot log in to public open Wifi connection because not being redirected to login site Status in network-manager package in Ubuntu: Confirmed Bug description: I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to public Wifi hotspots without wifi security, that require login through a web page. I don't know if this is reproducible on arbitrary public networks, or only on the few I tried. The solution was as follows: - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll need root or sudo). - Add the following lines as recommended by Guruprasad (https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/): [connectivity] uri=http://network-test.debian.org/nm response=NetworkManager is online interval=300 - Restart the network manager with service network-manager restart (will need sudo or root again). This is a very annoying and unnecessary default behavior it seems. Maybe a good idea to fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Mar 31 22:48:21 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-18 (41 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218) IpRoute: default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 SuedtirolSpot_1 c4464785-b548-4655-b06b-48a0aec06a87 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1760349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
@cjjefcoat Thanks for your advice,I have meet the same issue in virtualbox after the ubuntu 14.04 kernel update to 116. After downgrade the gcc to 4.8.4, and reinstall the 116 kernel and virtualbox 5.2,it work! ** Attachment added: "Virtualbox errror info" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750937/+attachment/5064244/+files/some_info -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567427] Re: gnome-shell crashes when touchscreen is touched
Anytime I have a video playing, or my laptop has been on a while, if I touch the screen all my programs close and I get logged out. Trying to turn off the screen via XINPUT does not work, disabling the touchscreen does NOTHING now that ubuntu runs on wayland. Running Ubuntu 17 right now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1567427 Title: gnome-shell crashes when touchscreen is touched Status in gnome-shell package in Ubuntu: Confirmed Bug description: In Ubuntu 16.04 with gnome-shell, the gnome-shell would crash every time I touch the touchscreen of my laptop (ASUS-S400CA). Sometimes the session would just restart, but when I touch again the whole session would just crash and drive me back to gdm. There are related log line in journald says: 4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (II) XKB: generating xkmfile /tmp/server-3D32AD876081C702D9B5501C336C5CB154F5C8D2.xkm 4月 07 20:38:14 ubuntu-s400ca kernel: gnome-shell[15211]: segfault at c ip 7f2ad1ae9f87 sp 7ffc96f9e6b0 error 4 in libcaribou.so.0.0.0[7f2ad1ae+1e000] 4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: syntax error: line 1 of stdin 4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: Errors encountered in stdin; not compiled. 4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) Error compiling keymap (server-3D32AD876081C702D9B5501C336C5CB154F5C8D2) 4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) XKB: Couldn't compile keymap 4月 07 20:38:15 ubuntu-s400ca polkitd(authority=local)[874]: Unregistered Authentication Agent for unix-session:6 (system bus name :1.360, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale zh_CN.UTF-8) (disconnected from bus) 4月 07 20:38:15 ubuntu-s400ca gnome-session[15129]: gnome-session-binary[15129]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 You may find the full log in the attached files generated by ubuntu- bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 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: Thu Apr 7 20:41:10 2016 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1567427/+subscriptions -- Mailing list: https://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 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n trusty/xenial/yakkety
I tried this so as to be ready for the next problem, but install does not like the armhf bit - wants amd64. -- Original Message -- From: Olivier TilloyTo: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety Date: Fri, 07 Jul 2017 15:18:35 - @David: please continue this discussion on bug #1702633. If you don't manage to install the dbgsym package, you can still download it manually and install it (with `sudo dpkg -i`) from there: https://launchpad.net/~canonical-chromium- builds/+archive/ubuntu/stage/+build/12789789 -- You received this bug notification because you are subscribed to a duplicate bug report (1702501). https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions Police Urge Americans to Carry This With Them at All Times The Observer http://thirdpartyoffers.juno.com/TGL3131/595fd5e12543d55e13807st02vuc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser package in Debian: Fix Released Bug description: $ apt-cache policy chromium-browser chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 0010 #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() #1 0x7f8cc1af580b #2 0x7f8cc1e20390 #3 0x5619ce286dc8 #4 0x5619ce289656 #5 0x5619ce289df9 #6 0x5619ce28a143 #7 0x7f8cc1b70821 #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f8cc1b2283d #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() #14 0x7f8cc1b49628 base::RunLoop::Run() #15 0x7f8cc1b75e36 base::Thread::ThreadMain() #16 0x7f8cc1b70726 #17 0x7f8cc1e166ba start_thread #18 0x7f8cab4c53dd clone r8: 002e r9: 5619cfcdd6ec r10: r11: 7f8cab552f50 r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 7f8c1b0d1eb0 di: si: 7f8c1b0d1eb0 bp: 7f8c1b0d1f00 bx: 7f8c1b0d1eb0 dx: 0061 ax: cx: 7f8bf0047070 sp: 7f8c1b0d1e60 ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Quits <1s after starting on desktop. Output from terminal-based launch is above. Worked earlier today before updating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- Mailing list: https://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 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial
That seems to have fixed the problem - Chromium is running as before the update. -- Original Message -- From: Olivier TilloyTo: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul 2017 20:48:42 - Thanks for the quick feedback Trent! To everyone affected by the crash, could you please try the packages in that PPA, and see if the crash goes away? sudo add-apt-repository -y ppa:osomon/chromium-fix-1702407 sudo apt update sudo apt dist-upgrade Note that packages for trusty haven't finished building yet, but should be done soon. -- You received this bug notification because you are subscribed to a duplicate bug report (1702501). https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions Police Urge Americans to Carry This With Them at All Times The Observer http://thirdpartyoffers.juno.com/TGL3131/595ea8dd137d28dc70eest03vuc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial Status in chromium-browser package in Ubuntu: In Progress Bug description: $ apt-cache policy chromium-browser chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 0010 #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() #1 0x7f8cc1af580b #2 0x7f8cc1e20390 #3 0x5619ce286dc8 #4 0x5619ce289656 #5 0x5619ce289df9 #6 0x5619ce28a143 #7 0x7f8cc1b70821 #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f8cc1b2283d #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() #14 0x7f8cc1b49628 base::RunLoop::Run() #15 0x7f8cc1b75e36 base::Thread::ThreadMain() #16 0x7f8cc1b70726 #17 0x7f8cc1e166ba start_thread #18 0x7f8cab4c53dd clone r8: 002e r9: 5619cfcdd6ec r10: r11: 7f8cab552f50 r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 7f8c1b0d1eb0 di: si: 7f8c1b0d1eb0 bp: 7f8c1b0d1f00 bx: 7f8c1b0d1eb0 dx: 0061 ax: cx: 7f8bf0047070 sp: 7f8c1b0d1e60 ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Quits <1s after starting on desktop. Output from terminal-based launch is above. Worked earlier today before updating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- Mailing list: https://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 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial
Turned off WiFi, Chromium browser comes up with home page (google). Seems OK. Turn on WiFi, and it crashes. -- Original Message -- From: Olivier TilloyTo: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul 2017 09:30:50 - To everyone affected by the crash (I haven't managed to reproduce it locally yet): can you please disable networking on your computer (turn off wifi) and check whether that makes chromium start normally? -- You received this bug notification because you are subscribed to a duplicate bug report (1702501). https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions How To Lose Weight Fast (Drink This Daily) Celebrity Local http://thirdpartyoffers.juno.com/TGL3131/595e29a1d367629a10cd6st04vuc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ apt-cache policy chromium-browser chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 0010 #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() #1 0x7f8cc1af580b #2 0x7f8cc1e20390 #3 0x5619ce286dc8 #4 0x5619ce289656 #5 0x5619ce289df9 #6 0x5619ce28a143 #7 0x7f8cc1b70821 #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f8cc1b2283d #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() #14 0x7f8cc1b49628 base::RunLoop::Run() #15 0x7f8cc1b75e36 base::Thread::ThreadMain() #16 0x7f8cc1b70726 #17 0x7f8cc1e166ba start_thread #18 0x7f8cab4c53dd clone r8: 002e r9: 5619cfcdd6ec r10: r11: 7f8cab552f50 r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 7f8c1b0d1eb0 di: si: 7f8c1b0d1eb0 bp: 7f8c1b0d1f00 bx: 7f8c1b0d1eb0 dx: 0061 ax: cx: 7f8bf0047070 sp: 7f8c1b0d1e60 ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Quits <1s after starting on desktop. Output from terminal-based launch is above. Worked earlier today before updating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- Mailing list: https://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 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename:xenial Linux rohan-T500 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages -- Original Message -- From: actionparsnipTo: rbayer...@juno.com Subject: [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 Date: Wed, 05 Jul 2017 15:47:39 - What is the output of: lsb_release -a; uname -a; apt-cache policy chromium-browser Thanks -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501/+subscriptions Actress Reveals Hollywood Secret “Flattening� Bloated Belly ActivatedYou http://thirdpartyoffers.juno.com/TGL3131/595d29a22fbfc29a23cbest02vuc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 Status in chromium-browser package in Ubuntu: Invalid Bug description: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3 0x55ae23b43dc8 #4 0x55ae23b46656 #5 0x55ae23b46df9 #6 0x55ae23b47143 #7 0x7f5c4b9a8821 #8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask() #9 0x7f5c4b957e90 base::MessageLoop::RunTask() #10 0x7f5c4b95997d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f5c4b95a83d #12 0x7f5c4b95b300 base::MessagePumpLibevent::Run() #13 0x7f5c4b956f15 base::MessageLoop::RunHandler() #14 0x7f5c4b981628 base::RunLoop::Run() #15 0x7f5c4b9ade36 base::Thread::ThreadMain() #16 0x7f5c4b9a8726 #17 0x7f5c4bc4e6ba start_thread #18 0x7f5c352fd3dd clone r8: 002e r9: 55ae2559a6ec r10: r11: 7f5c3538af50 r12: 7f5bc6b2aff0 r13: 0008 r14: 0008 r15: 7f5bc6b2aeb0 di: si: 7f5bc6b2aeb0 bp: 7f5bc6b2af00 bx: 7f5bc6b2aeb0 dx: 0067 ax: cx: 7f5bdc1079c0 sp: 7f5bc6b2ae60 ip: 55ae23b43dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. I tried complete reinstallation, purged and removed .config/chromium. Same problem. When I restored .config/chromium from an earlier working version, it crashed with: [8159:8202:0705/102433.905625:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. Received signal 11 SEGV_MAPERR 0010 #0 0x7f3a02096425 base::debug::StackTrace::StackTrace() #1 0x7f3a0209680b #2 0x7f3a023c1390 #3 0x5604c6bcadc8 #4 0x5604c6bcd656 #5 0x5604c6bcddf9 #6 0x5604c6bce143 #7
[Desktop-packages] [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
I cannot believe I am the only one to experience this bug. Is there anything I should try which I have not yet tried? ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 Status in chromium-browser package in Ubuntu: Invalid Bug description: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3 0x55ae23b43dc8 #4 0x55ae23b46656 #5 0x55ae23b46df9 #6 0x55ae23b47143 #7 0x7f5c4b9a8821 #8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask() #9 0x7f5c4b957e90 base::MessageLoop::RunTask() #10 0x7f5c4b95997d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f5c4b95a83d #12 0x7f5c4b95b300 base::MessagePumpLibevent::Run() #13 0x7f5c4b956f15 base::MessageLoop::RunHandler() #14 0x7f5c4b981628 base::RunLoop::Run() #15 0x7f5c4b9ade36 base::Thread::ThreadMain() #16 0x7f5c4b9a8726 #17 0x7f5c4bc4e6ba start_thread #18 0x7f5c352fd3dd clone r8: 002e r9: 55ae2559a6ec r10: r11: 7f5c3538af50 r12: 7f5bc6b2aff0 r13: 0008 r14: 0008 r15: 7f5bc6b2aeb0 di: si: 7f5bc6b2aeb0 bp: 7f5bc6b2af00 bx: 7f5bc6b2aeb0 dx: 0067 ax: cx: 7f5bdc1079c0 sp: 7f5bc6b2ae60 ip: 55ae23b43dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. I tried complete reinstallation, purged and removed .config/chromium. Same problem. When I restored .config/chromium from an earlier working version, it crashed with: [8159:8202:0705/102433.905625:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. Received signal 11 SEGV_MAPERR 0010 #0 0x7f3a02096425 base::debug::StackTrace::StackTrace() #1 0x7f3a0209680b #2 0x7f3a023c1390 #3 0x5604c6bcadc8 #4 0x5604c6bcd656 #5 0x5604c6bcddf9 #6 0x5604c6bce143 #7 0x7f3a02111821 #8 0x7f3a02097eea base::debug::TaskAnnotator::RunTask() #9 0x7f3a020c0e90 base::MessageLoop::RunTask() #10 0x7f3a020c297d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f3a020c383d #12 0x7f3a020c4300 base::MessagePumpLibevent::Run() #13 0x7f3a020bff15 base::MessageLoop::RunHandler() #14 0x7f3a020ea628 base::RunLoop::Run() #15 0x7f3a02116e36 base::Thread::ThreadMain() #16 0x7f3a02111726 #17 0x7f3a023b76ba start_thread #18 0x7f39eba663dd clone r8: 002e r9: 5604c86216ec r10: r11: 7f39ebaf3f50 r12: 7f39748cbff0 r13: 0008 r14: 0008 r15: 7f39748cbeb0 di: si: 7f39748cbeb0 bp: 7f39748cbf00 bx: 7f39748cbeb0 dx: 0067 ax: cx: 7f39d003a050 sp: 7f39748cbe60 ip: 5604c6bcadc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. When I open Chromium with a temporary profile, the window opens, but as soon as I enter "No thanks" to the option of signing in with Google, it crashes as above. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1702501] [NEW] chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Public bug reported: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3 0x55ae23b43dc8 #4 0x55ae23b46656 #5 0x55ae23b46df9 #6 0x55ae23b47143 #7 0x7f5c4b9a8821 #8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask() #9 0x7f5c4b957e90 base::MessageLoop::RunTask() #10 0x7f5c4b95997d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f5c4b95a83d #12 0x7f5c4b95b300 base::MessagePumpLibevent::Run() #13 0x7f5c4b956f15 base::MessageLoop::RunHandler() #14 0x7f5c4b981628 base::RunLoop::Run() #15 0x7f5c4b9ade36 base::Thread::ThreadMain() #16 0x7f5c4b9a8726 #17 0x7f5c4bc4e6ba start_thread #18 0x7f5c352fd3dd clone r8: 002e r9: 55ae2559a6ec r10: r11: 7f5c3538af50 r12: 7f5bc6b2aff0 r13: 0008 r14: 0008 r15: 7f5bc6b2aeb0 di: si: 7f5bc6b2aeb0 bp: 7f5bc6b2af00 bx: 7f5bc6b2aeb0 dx: 0067 ax: cx: 7f5bdc1079c0 sp: 7f5bc6b2ae60 ip: 55ae23b43dc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. I tried complete reinstallation, purged and removed .config/chromium. Same problem. When I restored .config/chromium from an earlier working version, it crashed with: [8159:8202:0705/102433.905625:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details. Received signal 11 SEGV_MAPERR 0010 #0 0x7f3a02096425 base::debug::StackTrace::StackTrace() #1 0x7f3a0209680b #2 0x7f3a023c1390 #3 0x5604c6bcadc8 #4 0x5604c6bcd656 #5 0x5604c6bcddf9 #6 0x5604c6bce143 #7 0x7f3a02111821 #8 0x7f3a02097eea base::debug::TaskAnnotator::RunTask() #9 0x7f3a020c0e90 base::MessageLoop::RunTask() #10 0x7f3a020c297d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f3a020c383d #12 0x7f3a020c4300 base::MessagePumpLibevent::Run() #13 0x7f3a020bff15 base::MessageLoop::RunHandler() #14 0x7f3a020ea628 base::RunLoop::Run() #15 0x7f3a02116e36 base::Thread::ThreadMain() #16 0x7f3a02111726 #17 0x7f3a023b76ba start_thread #18 0x7f39eba663dd clone r8: 002e r9: 5604c86216ec r10: r11: 7f39ebaf3f50 r12: 7f39748cbff0 r13: 0008 r14: 0008 r15: 7f39748cbeb0 di: si: 7f39748cbeb0 bp: 7f39748cbf00 bx: 7f39748cbeb0 dx: 0067 ax: cx: 7f39d003a050 sp: 7f39748cbe60 ip: 5604c6bcadc8 efl: 00010206 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. When I open Chromium with a temporary profile, the window opens, but as soon as I enter "No thanks" to the option of signing in with Google, it crashes as above. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702501 Title: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 0010 Status in chromium-browser package in Ubuntu: New Bug description: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3 0x55ae23b43dc8 #4 0x55ae23b46656 #5 0x55ae23b46df9 #6 0x55ae23b47143 #7 0x7f5c4b9a8821 #8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask() #9
[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running
I am running Ubuntu 17.04 Unity, and I get "unknown application" in Writer regardless of whether I start it up from the dock or from a document. With Calc, I only get it when starting up from a document. Not sure it matters, but my 17.04 is an upgrade from 16.10, not a fresh install. I have a laptop with 16.04 installed, and I don't get the "unknown application" bug in either Writer or Calc regardless of how I start them up. -- 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/1589215 Title: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running Status in libreoffice package in Ubuntu: Confirmed Bug description: Sometimes I get the issue of a menu having the name of a different application and being unusable, or being an application menu for the focused window but being titled 'Unknown Application Name', with LibreOffice. I also get this with GNOME apps but was told that this is a separate issue to the one I reported here: https://bugs.launchpad.net/ubuntu/+source/gnome- calculator/+bug/1584720 (see comment #5). The issue is with using Indicator Applet Appmenu in the panel on gnome-flashback installed on standard Ubuntu (which I call Ubuntu (GNOME) Flashback). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.1.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Jun 5 10:32:35 2016 InstallationDate: Installed on 2016-04-26 (39 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426) 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/1589215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1527590] Re: Menu isn't shown in gedit when run with sudo
Same problem. New install of 16.04.1. $ gedit --> shows menu $ sudo gedit --> does NOT show menu $ gksudo gedit --> does NOT show menu $ sudo -i ... # gedit --> does NOT show menu This happens whether the menus are set for the title bar OR for the top of the screen. Tried reinstalling gedit. No difference. -- 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/1527590 Title: Menu isn't shown in gedit when run with sudo Status in gedit package in Ubuntu: Confirmed Bug description: There are multiple ways to use gedit where the menu is not being shown, rendering it unusable. 1- use it over ssh 2- do "sudo gedit" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.2-1ubuntu4 ProcVersionSignature: User Name 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 18 07:16:30 2015 InstallationDate: Installed on 2015-10-23 (55 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) 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/1527590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1596192] Re: ubuntu org.gnome.Nautilus[1336]: (soffice:3712): Gdk-WARNING **: gdk_window_set_icon_list: icons too large
I have a similar bug using LibreOffice Write, which is now occurring regularly. In my case, the computer freezes and I have to hard-restart it. I am also using 16.04, on an iMac with a second monitor attached. ** Attachment added: "Syslog crash 15072016 16.05hr.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1596192/+attachment/4701979/+files/Syslog%20crash%2015072016%2016.05hr.txt -- 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/1596192 Title: ubuntu org.gnome.Nautilus[1336]: (soffice:3712): Gdk-WARNING **: gdk_window_set_icon_list: icons too large Status in libreoffice package in Ubuntu: New Bug description: get this logged into journalctl when using Calc: ubuntu org.gnome.Nautilus[1336]: ** (soffice:3712): WARNING **: Unknown event notification 37 ubuntu org.gnome.Nautilus[1336]: (soffice:3712): Gdk-WARNING **: gdk_window_set_icon_list: icons too large there is also : Unknown event notification 34 Unknown event notification 35 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-27.46-generic 4.4.13 Uname: Linux 4.4.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 25 15:56:36 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin 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/1596192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets
The instructions I found that worked and were these easiest to follow were at http://askubuntu.com/questions/727127/last-upgrade-crashes- network-manager-no-internet-connection-no-applet specifically the very first answer. I tried step 1 but that did not work, so I did step 2 and then rebooted and then my network connections worked again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Fix Committed Status in libnl3 package in Debian: Fix Released Bug description: [Triage Notes] The proposed fix for this bug in libnl3 caused a regression in trusty- proposed, tracked in bug 1539634. The regression is caused by a latent bug in Network Manager. We expect to fix this by landing a fix for the bug in Network Manager in trusty-updates at the same time as this fix. [Impact] * Applications in Trusty using libnl-3-200 which frequently open and close netlink sockets can easily fail when attempting to bind the local socket. The problem happens when libnl choose a port id already used by another application and subsequently libnl fails instead of trying another port id. The original bug was discovered when attempting to start a virtual machine under libvirt, which is a user of this library. * Backporting fixes from upstream release fixes a real bug in the current version of the library in Trusty. The alternative is for all applications to manually manage their local port allocation, or as upstream has accepted allowing libnl to attempt to try for other local ports. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. [Test Case] * On a Trusty 14.04 system 1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \ libnl-genl-3-dev libnl-route-3-200 \ make gcc build-essential libnl1 2. download and unpack attachment: lp_1511735_test.tar 3. Run testcases: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 6975 (pid: 6974) local port has been set by the libnl to 6975 (pid: 6975) ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975) libnl FAILED % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=6978 TEST (a)... Traceback (most recent call last): File "libnl3-test-rh1249158.py", line 226, in locals()["TEST_" + arg]() File "libnl3-test-rh1249158.py", line 140, in TEST_a sk = nl_get_socket() File "libnl3-test-rh1249158.py", line 115, in nl_get_socket raise IOError(-err, _nl_geterror()) OSError: [Errno 6] b'Unspecific failure' 4. After applying the updated packages: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 11295 (pid: 11294) local port has been set by the libnl to 2894081055 (pid: 11295) libnl OK % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=11296 TEST (a)... ...done TEST (b)... ...done TEST (c)... ...done TEST (d)... ...done [Regression Potential] * There are quite a few high profile packages that depend on this package, notably libvirt and network-manager. The complete list is here: # on Trusty % apt-rdepends -r libnl-3-200 | head -n 33 libnl-3-200 Reverse Depends: batctl (>= 2013.4.0-2) Reverse Depends: bmon (>= 1:3.1-1) Reverse Depends: crda (>= 1.1.2-1ubuntu2) Reverse Depends: hostapd (>= 1:2.1-0ubuntu1) Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1) Reverse Depends: iw (>= 3.4-1) Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1) Reverse Depends: kismet (>= 2013.03.R1b-3) Reverse Depends: knemo (>= 0.7.6-2) Reverse Depends: libfsobasics3 (>= 0.12.0-4) Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1) Reverse Depends: libnl-3-200-dbg (= 3.2.21-1) Reverse Depends: libnl-3-dev (= 3.2.21-1) Reverse Depends: libnl-cli-3-200 (= 3.2.21-1) Reverse Depends: libnl-genl-3-200 (= 3.2.21-1) Reverse Depends: libnl-nf-3-200 (= 3.2.21-1) Reverse Depends: libnl-route-3-200 (= 3.2.21-1) Reverse Depends: libnl-utils (>= 3.2.21-1) Reverse Depends: libnss-gw-name (>= 0.3-2) Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13) Reverse
[Desktop-packages] [Bug 1581535] Re: libnl upgrade breaks Network Manager
*** This bug is a duplicate of bug 1511735 *** https://bugs.launchpad.net/bugs/1511735 The instructions I found that worked and were these easiest to follow were at http://askubuntu.com/questions/727127/last-upgrade-crashes- network-manager-no-internet-connection-no-applet specifically the very first answer. I tried step 1 but that did not work, so I did step 2 and then rebooted and then my network connections worked again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1581535 Title: libnl upgrade breaks Network Manager Status in libnl3 package in Ubuntu: Invalid Status in libnl3 source package in Trusty: Confirmed Bug description: I appear to have been hit by a regression problem in the libnl update described here: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735 After running a regular software update this morning and rebooting, I've completely lost networking access. Network Manager is down. I'm running Trusty 14.04. I tried this workaround: http://askubuntu.com/questions/727127/last-upgrade-crashes-network- manager-no-internet-connection-no-applet ... and step 1 didn't work. I'll be trying step 2 tonight when I've got more time. I'm filing this as a new bug with a regression-update, as indicated in the above-linked bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1437862] Re: pg_upgradecluster fails: "could not get cluster locales"
FWIW, I'm also running into this, but found a work-around. It was suggested at http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1172657 to edit the pg_upgradecluster script and increase the timeout from 5 seconds to 30. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1437862 Title: pg_upgradecluster fails: "could not get cluster locales" Status in postgresql-common package in Ubuntu: Confirmed Bug description: We upgrade a 12.04 LTS to 14.04 LTS and use the pg_upgradecluster command(usage as described in /usr/share/doc/README.Debian.gz). But we get a failure an no upgrade is done: pg_dropcluster 9.3 main --stop pg_upgradecluster 9.1 main psql: FATAL: the database system is shutting down psql: FATAL: the database system is shutting down Use of uninitialized value $out in pattern match (m//) at /usr/share/postgresql-common/PgCommon.pm line 883. psql: FATAL: the database system is shutting down Use of uninitialized value $out in pattern match (m//) at /usr/share/postgresql-common/PgCommon.pm line 889. Use of uninitialized value $ctype in scalar chomp at /usr/share/postgresql-common/PgCommon.pm line 892. Use of uninitialized value $collate in scalar chomp at /usr/share/postgresql-common/PgCommon.pm line 893. Error: could not get cluster localesapt-get install postgresql-9.3 apt-get install postgresql-9.3 postgresql-common postgresql-client-9.3 postgresql-contrib-9.3 said, that all packages are in their newest version and dpkg said: iU postgresql 9.3+154 all object-relational SQL database (supported version) ii postgresql-9.1 9.1.15-0ubuntu0.12.04 amd64object-relational SQL database, version 9.1 server iU postgresql-9.3 9.3.6-0ubuntu0.14.04 amd64object-relational SQL database, version 9.3 server iU postgresql-client 9.3+154 all front-end programs for PostgreSQL (supported version) ii postgresql-client-9.1 9.1.15-0ubuntu0.12.04 amd64front-end programs for PostgreSQL 9.1 iF postgresql-client-9.3 9.3.6-0ubuntu0.14.04 amd64front-end programs for PostgreSQL 9.3 ii postgresql-client-common154 all manager for multiple PostgreSQL client versions ii postgresql-common 154 all PostgreSQL database-cluster manager iU postgresql-contrib 9.3+154 all additional facilities for PostgreSQL (supported version) ii postgresql-contrib-9.1 9.1.15-0ubuntu0.12.04 amd64additional facilities for PostgreSQL iU postgresql-contrib-9.3 9.3.6-0ubuntu0.14.04 amd64additional facilities for PostgreSQL ii postgresql-doc 9.3+154 all documentation for the PostgreSQL database management system ii postgresql-doc-9.1 9.1.15-0ubuntu0.12.04all documentation for the PostgreSQL database management system ii postgresql-doc-9.3 9.3.6-0ubuntu0.14.04 all documentation for the PostgreSQL database management system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1437862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1492582] [NEW] bug
Public bug reported: boot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 5 12:30:16 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1854] InstallationDate: Installed on 2015-05-16 (111 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 003: ID 064e:e263 Suyin Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: LANGUAGE=fr PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-43-generic.efi.signed root=UUID=2b26c1f3-70d3-483f-9ec7-69a50d7375bb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG34124WJ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd10/09/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr08891330591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 2000 Notebook PC dmi.product.version: 08891330591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Sep 5 12:29:02 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 900 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1492582 Title: bug Status in xorg package in Ubuntu: New Bug description: boot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 5 12:30:16 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1854] InstallationDate: Installed on 2015-05-16 (111 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 003: ID 064e:e263 Suyin Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: LANGUAGE=fr
[Desktop-packages] [Bug 1373452] [NEW] nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: Crashed for no apparent reason. Currently had Google Chrome open and Blender 2.71 w/ CUDA rendering enabled. lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-lowlatency 3.13.11.6 Uname: Linux 3.13.0-35-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 DKMSKernelVersion: 3.13.0-36-lowlatency Date: Wed Sep 24 07:13:56 2014 InstallationDate: Installed on 2014-09-02 (22 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package gnome3-ppa third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1373452 Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Crashed for no apparent reason. Currently had Google Chrome open and Blender 2.71 w/ CUDA rendering enabled. lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-lowlatency 3.13.11.6 Uname: Linux 3.13.0-35-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 DKMSKernelVersion: 3.13.0-36-lowlatency Date: Wed Sep 24 07:13:56 2014 InstallationDate: Installed on 2014-09-02 (22 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1373452/+subscriptions -- Mailing list: https://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 1210906] Re: Graphic fail on first update
Thanks for the reply. I have given up on Ubuntu for now and will continue with Windows 7 until you next release 14 03. On Sun, Jan 5, 2014 at 12:00 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Ray Fox, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg REPLACE-WITH-BUG-NUMBER Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Tags added: latest-bios-5.09 ** Changed in: xorg (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1210906 Title: Graphic fail on first update Status in “xorg” package in Ubuntu: Incomplete Bug description: Loaded fresh Ubuntu 13.04 and after first update the graphics did not work. Had to reboot fail-safe graphics. Not sure which video driver Ubuntu attempted to install. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Aug 10 21:20:54 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6199] InstallationDate: Installed on 2013-08-10 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: HP-Pavilion GC674AA-ABA m8120n MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=761ec824-cb49-4cbc-b4d9-68f2e57322c0 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.09 dmi.board.name: Basswood3G dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.05 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd06/08/2007:svnHP-Pavilion:pnGC674AA-ABAm8120n:pvr:rvnASUSTekComputerINC.:rnBasswood3G:rvr1.05:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC674AA-ABA m8120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Aug 10 20:57:38 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 8 inputLogitech Unifying Device. Wireless PID:2008 KEYBOARD, id 9 inputVF0700 Live! Cam Chat HD KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1210906/+subscriptions -- 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/1210906 Title: Graphic fail on first update Status in “xorg” package
[Desktop-packages] [Bug 1228570] Re: Login often fails
I've got the same problem in Ubuntu 13.04. After login, I get a blank screen for about a second, then it goes back to lightdm. Removing either .ICEauthority or .Xauthority solves the problem. The problem reappears (to me) seemingly random, so not necessarily after each successful login. -- 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/1228570 Title: Login often fails Status in “lightdm” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I am using the Lenovo Thinkpad Twist with Saucy and the standard Unity desktop. Often when I log in, after entering the password the screen gets black and within one second I am back in LightDM. I have to enter my password three or four times until getting a successful login. Logging in right after reboot works more often. Logging into the guest account always works. There are no messages in .xsession-errors. /var/log/syslog adds the following lines after pressing Enter after entering the password until LightDM re-appearing: First failed attempt: Sep 21 13:28:05 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:28:05 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:28:05 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:28:05 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:28:05 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.139': no such name Sep 21 13:28:05 till-twist acpid: client 7242[0:0] has disconnected Sep 21 13:28:05 till-twist acpid: client connected from 7493[0:0] Sep 21 13:28:05 till-twist acpid: 1 client rule loaded Sep 21 13:28:05 till-twist dbus[574]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Sep 21 13:28:05 till-twist dbus[574]: [system] Successfully activated service 'org.freedesktop.systemd1' Sep 21 13:28:06 till-twist colord: Device added: xrandr-LVDS1 Sep 21 13:28:06 till-twist colord: Profile added: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:28:06 till-twist colord: Automatic metadata add icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1 Sep 21 13:28:06 till-twist colord: Profile added: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:28:06 till-twist colord: Profile added: icc-42cf0f25cbd914f2177438317b72f222 Second failed attempt: Sep 21 13:34:42 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:34:42 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:34:42 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:34:42 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.160': no such name Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.160': no such name Sep 21 13:34:43 till-twist acpid: client 7493[0:0] has disconnected Sep 21 13:34:43 till-twist acpid: client connected from 7737[0:0] Sep 21 13:34:43 till-twist acpid: 1 client rule loaded Sep 21 13:34:43 till-twist dbus[574]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Sep 21 13:34:43 till-twist dbus[574]: [system] Successfully activated service 'org.freedesktop.systemd1' Sep 21 13:34:43 till-twist colord: Device added: xrandr-LVDS1 Sep 21 13:34:43 till-twist colord: Profile added: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:34:43 till-twist colord: Automatic metadata add icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1 Sep 21 13:34:43 till-twist colord: Profile added: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:34:43 till-twist colord: Profile added: icc-42cf0f25cbd914f2177438317b72f222 Third failed attempt: Sep 21 13:34:53 till-twist whoopsie[1969]: online Sep 21 13:35:43 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:35:43 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:35:43 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:35:43 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:35:43 till-twist
[Desktop-packages] [Bug 1210906] [NEW] Graphic fail on first update
Public bug reported: Loaded fresh Ubuntu 13.04 and after first update the graphics did not work. Had to reboot fail-safe graphics. Not sure which video driver Ubuntu attempted to install. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Aug 10 21:20:54 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6199] InstallationDate: Installed on 2013-08-10 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: HP-Pavilion GC674AA-ABA m8120n MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=761ec824-cb49-4cbc-b4d9-68f2e57322c0 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.09 dmi.board.name: Basswood3G dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.05 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd06/08/2007:svnHP-Pavilion:pnGC674AA-ABAm8120n:pvr:rvnASUSTekComputerINC.:rnBasswood3G:rvr1.05:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC674AA-ABA m8120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Aug 10 20:57:38 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 8 inputLogitech Unifying Device. Wireless PID:2008 KEYBOARD, id 9 inputVF0700 Live! Cam Chat HD KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 raring ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1210906 Title: Graphic fail on first update Status in “xorg” package in Ubuntu: New Bug description: Loaded fresh Ubuntu 13.04 and after first update the graphics did not work. Had to reboot fail-safe graphics. Not sure which video driver Ubuntu attempted to install. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Aug 10 21:20:54 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6199] InstallationDate: Installed on 2013-08-10 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: HP-Pavilion GC674AA-ABA m8120n MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=761ec824-cb49-4cbc-b4d9-68f2e57322c0 ro recovery nomodeset SourcePackage: xorg
[Desktop-packages] [Bug 1204378] [NEW] Copy files from mounted cpio does not work
Public bug reported: I double click on a cpio files, causing it to be mounted? on the files app, so I can click on it and view the files inside. However, when I copy a folder inside it and to paste it into normal folder, the copy process doesn't work at all. It says 0 byte of 600 mb 0 byte per second. If I click on big X (to the right) the button goes dark but it wasn't cancelled (the window still there). Clicking on the tiny x (upper left) doesn't close (just hide / minimize) or cancel it either, and can still be accessed by right clicking on the Files icon and select show copy dialog. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Jul 24 14:56:20 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x499+232+95' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-06-15 (38 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1204378 Title: Copy files from mounted cpio does not work Status in “nautilus” package in Ubuntu: New Bug description: I double click on a cpio files, causing it to be mounted? on the files app, so I can click on it and view the files inside. However, when I copy a folder inside it and to paste it into normal folder, the copy process doesn't work at all. It says 0 byte of 600 mb 0 byte per second. If I click on big X (to the right) the button goes dark but it wasn't cancelled (the window still there). Clicking on the tiny x (upper left) doesn't close (just hide / minimize) or cancel it either, and can still be accessed by right clicking on the Files icon and select show copy dialog. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Jul 24 14:56:20 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x499+232+95' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-06-15 (38 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1204378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1204378] Re: Copy files from mounted cpio does not work
I would like to add, I've tried to cancel it using the right click -- Cancel All in Progress Action but it doesn't work either (the not working cpio copy dialog still there). -- 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/1204378 Title: Copy files from mounted cpio does not work Status in “nautilus” package in Ubuntu: New Bug description: I double click on a cpio files, causing it to be mounted? on the files app, so I can click on it and view the files inside. However, when I copy a folder inside it and to paste it into normal folder, the copy process doesn't work at all. It says 0 byte of 600 mb 0 byte per second. If I click on big X (to the right) the button goes dark but it wasn't cancelled (the window still there). Clicking on the tiny x (upper left) doesn't close (just hide / minimize) or cancel it either, and can still be accessed by right clicking on the Files icon and select show copy dialog. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Jul 24 14:56:20 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x499+232+95' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-06-15 (38 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1204378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 424956] Re: nautilus crashed with SIGABRT in raise()
I'm with Bernadette Addison. But I've updated my Ubuntu 64, so its no longer fresh. -- 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/424956 Title: nautilus crashed with SIGABRT in raise() Status in Nautilus: New Status in “nautilus” package in Ubuntu: Confirmed Status in “nautilus” package in Unity Linux: New Bug description: Binary package hint: nautilus changed settings in nautilus. activated the feature open file with one click. Then nautilus crashed and apport started. ProblemType: Crash Architecture: amd64 CheckboxSubmission: d68af718cfa52b0ffd90b28d0c3f3daa CheckboxSystem: 7fe50468a9edf69a38c2a5a0c6c8ec60 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/nautilus Package: nautilus 1:2.27.91-0ubuntu3 ProcCmdline: nautilus ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-9.29-generic Signal: 6 SourcePackage: nautilus StacktraceTop: raise () from /lib/libc.so.6 abort () from /lib/libc.so.6 g_assertion_message () g_assertion_message_expr () ?? () Title: nautilus crashed with SIGABRT in raise() Uname: Linux 2.6.31-9-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/424956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 285104] Re: Keyboard shortcut raise obscured window, otherwise lower doesn't work
This bug is actually in compiz - if you switch to the 2-D mode you get metacity, and in that mode it is possible to get raise/lower to work. In 3-D mode (which is really necessary to get decent performance these days) it is not possible to bind the raise/lower operation. ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/285104 Title: Keyboard shortcut raise obscured window, otherwise lower doesn't work Status in The Metacity Window Manager: New Status in “compiz” package in Ubuntu: New Status in “metacity” package in Ubuntu: Triaged Bug description: Binary package hint: metacity I bound F4 to this shortcut, but it has no effect. The related shortcuts Raise window above other windows and Lower window below other windows work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/285104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 922968] Re: computer suspends again after resume
@jsalisbury: You are correct in that the system is simply doing what it is told, but it's still a bug in the user experience. The question is what the user is intending to do. Is the user intentionally telling the system to suspend twice? There's no use case in which that's useful. Then we have to consider the user experience. When the user opens the lid, they are telling the system to wake up because they intend to use it. They aren't expecting the system to put itself back to sleep, so this violates the principle of least surprise. -- 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/922968 Title: shouldn't queue a second suspend if the machine is already suspending Status in Gnome Powermanager: New Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: New Status in “linux” package in Ubuntu: Invalid Status in “gnome-settings-daemon” source package in Precise: Confirmed Status in “linux” source package in Precise: Invalid Bug description: Reproduce: This only triggers when you suspend with (Fn-F4) then quickly close the laptop lid. The power settings are setup such that the laptop lid close will suspend the laptop as well. So we're getting two suspend events in a row. Workaround: Either close the lid to suspend and not use Fn-F4. Or suspend using Fn-F4 then wait a few seconds before closing the lid. Version: Ubuntu 3.2.0-11.19-generic 3.2.1 After suspending the computer using Fn-F4, and for an extended period of time, I then wake the computer up by opening the lid and pressing the 'Fn' key. The computer starts to resume, and I am prompted for my password. Then the computer suspends again, and I have to wake it up again to resume the computer. This is with the computer charged sufficiently, but not plugged into an AC source. In addition I've also confirmed that using pm-suspend and resuming by pressing 'Fn' will still cause the machine to suspend again after resume. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-11-generic 3.2.0-11.19 ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1 Uname: Linux 3.2.0-11-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arges 2127 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf262 irq 46' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21ce,0012 HDA:80862805,80860101,0010' Controls : 26 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Jan 27 23:00:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MachineType: LENOVO 4177CTO ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic root=UUID=0f84abde-0eb0-405f-a8c6-b09dd4c4dae9 ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-11-generic N/A linux-backports-modules-3.2.0-11-generic N/A linux-firmware1.68 SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2011-12-21 (37 days ago) dmi.bios.date: 07/29/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET63WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1099447] [NEW] Flashplugin freezing in Firefox playing youtube videos 480p 12.10 x86
Public bug reported: I've always had problems in Linux running 720p+ video in Firefox with the flashplugin but just accepted it and watched 480p videos. I've just installed 12.10, updated and installed ubuntu-restricted- extras. Youtube videos at 480p are freezing after a couple of minutes. I cant alt-tab and have to ctrl+alt+F2, ps awx, kill to get back into unity. I'm using the radeon drivers as neither of the fglrx packages in 12.10 are compatible with unity. Please let me know what other info I can provide soon as I'm going to have to wipe 12.10 too many problems. ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1099447 Title: Flashplugin freezing in Firefox playing youtube videos 480p 12.10 x86 Status in “flashplugin-nonfree” package in Ubuntu: New Bug description: I've always had problems in Linux running 720p+ video in Firefox with the flashplugin but just accepted it and watched 480p videos. I've just installed 12.10, updated and installed ubuntu-restricted- extras. Youtube videos at 480p are freezing after a couple of minutes. I cant alt-tab and have to ctrl+alt+F2, ps awx, kill to get back into unity. I'm using the radeon drivers as neither of the fglrx packages in 12.10 are compatible with unity. Please let me know what other info I can provide soon as I'm going to have to wipe 12.10 too many problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1099447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically
So how do we begin the SRU process? -- 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/280571 Title: NetworkManager does not auto-connect to VPNs marked Connect Automatically Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: Triaged Status in “network-manager” package in Debian: New Bug description: VPN connections marked Connect Automatically are not activated when a wired or wireless network becomes available. Fixed upstream in commit: commit ece5e209cdc409a21e249dacbdbc953a1db4c6b7 Author: Jiří Klimeš jkli...@redhat.com Date: Tue Aug 21 17:49:41 2012 +0200 core: VPN autoconnect feature (bgo #560471) (rh #483120) We go through the SECONDARIES state where we check if there are some secondary (VPN or other) UUIDs that are to be activated before progressing to ACTIVATED. In case of an error with a secondary UUID or its activation, the base connection can't activate successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/280571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
NVidia GEForce 610M and additional integrated Intel video card. Intermittent hard freezes on Ubuntu and Mint - no traces as to why in any log file anywhere. Tried fresh install of 12.04 with different hard drive. Worked perfectly until I installed nvidia-stable drivers from Ubuntu repository - hard froze within minutes. Installed nouveau drivers and removed all traces of nvidia drivers. NOTE: I had to remove the nvidia drivers in order to make my system stable. Other posts had said that was not necessary - for me it was. One nouveau drivers were active. I issued the following: ~$ sudo apt-get --purge remove nvidia-common nvidia-current nvidia-settings ~$ sudo apt-get install ubuntu-desktop ubuntu-desktop was a dependency of nvidia-common and therefore removed with the purge - that's why the install of ubuntu-desktop afterwards. My system has been rock solid since. -- 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/993187 Title: ubuntu 12.04 completely freezes frequently. Status in “linux” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Won't Fix Status in “linux” source package in Precise: Won't Fix Status in “xserver-xorg-video-intel” source package in Precise: Won't Fix Bug description: Update: 6/12/2012 This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset. Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics. If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug. Thx. Joris V. (brains). Update: 5/21/2012 Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs. Original description: I recently installed newly released ubuntu 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly. I have to use hard restart every time. Initially it was only during videos but now even during normal browsing it is freezing. I am using on board graphics and do not have any graphics card installed. Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use :( Below is my hardware configuration: Processor: Intel CORE i3 processor (2nd generation) Board: Intel® Desktop Board DH67BL Ram: 4GB Graphics: On board HDD: 500 GB Please let me know if you need more information, or any specific logs I can capture (and how). Thanks, Ketan Patil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically
This really shouldn't be downgraded to wishlist. Auto-connecting to a VPN is a standard and I dare-say critical feature for many VPN users. If upstream isn't willing to fix the issue, then the community should take it up. I mean...my god, this bug has been around since the Hardy area. That's 9 release cycles ago. -- 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/280571 Title: NetworkManager does not auto-connect to VPNs marked Connect Automatically Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Triaged Status in “network-manager” package in Debian: New Bug description: VPN connections marked Connect Automatically are not activated when a wired or wireless network becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/280571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 942530] Re: on-screen keyboard always displays once enabled
This bug is terribly annoying. -- 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/942530 Title: on-screen keyboard always displays once enabled Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Whilst investigating bug 937611, I enabled the on-screen keyboard. However, I subsequently switched if off via System Settings - Universal Access - Typing tab - Typing Assistant. As expected, the keyboard no longer displays on the desktop but when the screen locks automatically or is locked manually, the on-screen keyboard is displayed again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screensaver 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.93-0ubuntu2 Architecture: i386 Date: Tue Feb 28 10:28:11 2012 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to precise on 2012-01-12 (46 days ago) WindowManager: No value set for `/desktop/gnome/session/required_components/windowmanager' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/942530/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938905] [NEW] Needs more commandline options
Public bug reported: Description:Ubuntu precise (development branch) Release:12.04 rhythmbox: Installed: 2.95-0ubuntu2 In my attempt to create a Unity quicklist for rhythmbox, I found that it has very few useful options available. It should have basic abilities such as play, pause, next, back, etc. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: commandline quicklists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/938905 Title: Needs more commandline options Status in “rhythmbox” package in Ubuntu: New Bug description: Description: Ubuntu precise (development branch) Release: 12.04 rhythmbox: Installed: 2.95-0ubuntu2 In my attempt to create a Unity quicklist for rhythmbox, I found that it has very few useful options available. It should have basic abilities such as play, pause, next, back, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/938905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938905] Re: Needs more commandline options
Figured it out. rythembox-client has the control commands. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/938905 Title: Needs more commandline options Status in “rhythmbox” package in Ubuntu: New Bug description: Description: Ubuntu precise (development branch) Release: 12.04 rhythmbox: Installed: 2.95-0ubuntu2 In my attempt to create a Unity quicklist for rhythmbox, I found that it has very few useful options available. It should have basic abilities such as play, pause, next, back, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/938905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938905] Re: Needs more commandline options
** Changed in: rhythmbox (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/938905 Title: Needs more commandline options Status in “rhythmbox” package in Ubuntu: Invalid Bug description: Description: Ubuntu precise (development branch) Release: 12.04 rhythmbox: Installed: 2.95-0ubuntu2 In my attempt to create a Unity quicklist for rhythmbox, I found that it has very few useful options available. It should have basic abilities such as play, pause, next, back, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/938905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938372] Re: Add Unity Launcher Quicklist
** Branch linked: lp:~tcfox54-gmail/ubuntu/precise/gimp/add_quicklist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/938372 Title: Add Unity Launcher Quicklist Status in “gimp” package in Ubuntu: New Bug description: Add action items for display in the Unity Launcher's Quicklist https://wiki.ubuntu.com/Unity/LauncherAPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/938372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 937998] Re: Add Unity Launcher Quicklist
There aren't really very many useful command line options available. I added the ability to open Empathy in the background due to it being a useful feature. However, I do not remember if the options for preferences or accounts are available at the command line. Cheers! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/937998 Title: Add Unity Launcher Quicklist Status in “empathy” package in Ubuntu: Confirmed Bug description: Add action items for display in the Unity Launcher's Quicklist https://wiki.ubuntu.com/Unity/LauncherAPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/937998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 937999] Re: Add Unity Launcher Quicklist
** Branch linked: lp:~tcfox54-gmail/ubuntu/precise/rhythmbox/add_quicklist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/937999 Title: Add Unity Launcher Quicklist Status in “rhythmbox” package in Ubuntu: New Bug description: Add action items for display in the Unity Launcher's Quicklist https://wiki.ubuntu.com/Unity/LauncherAPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/937999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp