[Desktop-packages] [Bug 1873295] [NEW] Updated 04-16-2000 and system-monitor shell extension broke
Public bug reported: I updated my 20.04 beta box to on 16 Apr 2020 and the system-monitor applet stopped working. Going to https://extensions.gnome.org/extension/120/system-monitor/ shows error. I removed and tried readding with same result. When adding back the /var/log/syslog shows: Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet init from /home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet enabling Apr 16 11:07:58 x1 gnome-shell[1892]: JS ERROR: Extension system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?#012SystemMonitor_TipItem@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9#012tip_format@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27#012SystemMonitor_Cpu@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:14#012createCpus@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20#012enable@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:166:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:336:26#012callback@resource:///org/gnome/shell/ui/extensionDownloader.js:232:39#012gotExtensionZipFile/<@resource:///org/gnome/shell/ui/extensionDownloader.js:115:13 Apr 16 11:08:00 x1 gnome-shell[1892]: JS ERROR: TypeError: this.tip_labels[i] is undefined#012update@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:925:56 Nothing I've done can get it working. Googleing hasn't revealed anything useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:11:22 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-25 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873295 Title: Updated 04-16-2000 and system-monitor shell extension broke Status in gnome-shell package in Ubuntu: New Bug description: I updated my 20.04 beta box to on 16 Apr 2020 and the system-monitor applet stopped working. Going to https://extensions.gnome.org/extension/120/system-monitor/ shows error. I removed and tried readding with same result. When adding back the /var/log/syslog shows: Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet init from /home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet enabling Apr 16 11:07:58 x1 gnome-shell[1892]: JS ERROR: Extension system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?#012SystemMonitor_TipItem@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9#012tip_format@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27#012SystemMonitor_Cpu@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:14#012createCpus@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20#012enable@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:166:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:336:26#012callback@resource:///org/gnome/shell/ui/extensionDownloader.js:232:39#012gotExtensionZipFile/<@resource:///org/gnome/shell/ui/extensionDownloader.js:115:13 Apr 16 11:08:00 x1 gnome-shell[1892]: JS ERROR: TypeError: this.tip_labels[i] is undefined#012update@/home/pgraner/.local/share/gnome-shell/extensions/sy
[Desktop-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Tested with network-manager 1.20.4-2ubuntu2.2 from proposed on eoan. Result: VPN passwords are saved correctly again! Thank you so much! I built a vpn benchmark script that relies on the password being able to be saved. It uses the nmcli tool to add new connections and set the password. It can now run again. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Is there a rough timeline when this will be available in eoan? I can confirm the bug on all my ubuntu 19.10 installs and I have to switch vpns frequently. Thanks for the great work! -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835605] Re: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0
** Package changed: ubuntu => gvfs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1835605 Title: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0 Status in gvfs package in Ubuntu: New Bug description: When I upgraded to Disco, I got the following error: gvfs-afc-volume-monitor[6816]: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg --list gvfs** Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ NameVersion Architektur Beschreibung +++-===--- ii gvfs:amd64 1.40.1-1 amd64userspace virtual filesystem - GIO module ii gvfs-backends 1.40.1-1 amd64userspace virtual filesystem - backends ii gvfs-bin1.40.1-1 amd64userspace virtual filesystem - deprecated command-line tools ii gvfs-common 1.40.1-1 all userspace virtual filesystem - common data files ii gvfs-daemons1.40.1-1 amd64userspace virtual filesystem - servers ii gvfs-fuse 1.40.1-1 amd64userspace virtual filesystem - fuse server ii gvfs-libs:amd64 1.40.1-1 amd64userspace virtual filesystem - private libraries ldd -r /usr/lib/gvfs/gvfs-afc-volume-monitor linux-vdso.so.1 (0x7ffcd31f7000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7fb3eb9bb000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7fb3eb95f000) libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 (0x7fb3eb73c000) libplist.so.3 => /usr/local/lib/libplist.so.3 (0x7fb3eb52d000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7fb3eb364000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb3eb179000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fb3eb103000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb3eb0e2000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7fb3eb0d8000) libssl.so.1.0.0 => not found libcrypto.so.1.0.0 => not found libusbmuxd.so.4 => /usr/local/lib/libusbmuxd.so.4 (0x7fb3eaed) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7fb3eaec8000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fb3eaeac000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb3eaea6000) libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x7fb3eae4a000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7fb3eae2) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fb3eae05000) /lib64/ld-linux-x86-64.so.2 (0x7fb3ebb27000) libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x7fb3eadae000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fb3eada3000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fb3ead9a000) undefined symbol: ERR_remove_thread_state, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_CTX_use_RSAPrivateKey, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: CRYPTO_cleanup_all_ex_data, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: EVP_PKEY_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: PEM_write_bio_X509, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_set_notAfter, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: ASN1_INTEGER_set, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_set_notBefore, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: RSA_new, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: BIO_s_mem, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: RSA_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_set_bio, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_COMP_get_compression_methods, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_read, version OPENSSL_1.0.0
[Desktop-packages] [Bug 1801494] Re: dock missing
I had this problem with a fresh install of Ubuntu Mate 18.10 on a 2008 white Macbook, 2.4 GHz. dual-booting with MacOS 10.6.8, using rEFInd. I have never seen the menu bar of Ubuntu Mate on this install, it was absent on the first boot. I've tried many of the solutions suggested here and in other threads, to no avail. I was able to sort of "fix" it by switching from gdm to lightdm, which gives me a minimal but functional window manager, allowing me (among other things) to connect to a WiFi network. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 Version table: *** 0.9.1ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 4) dock is there 5) dock is not there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]
Forgot to mention, you may need to use the hotkey twice to lock from desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1804008 Title: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated from ubuntu-d...@ubuntu.com/theming.js:416] Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: All my gnome-shell extensions randomly (apparently) crash. This behavior began when i upgraded to cosmic. Here's a excerpt of my logs: Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor (0x55669ffd87a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1 5566ae293bb8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3 5566ae293b00 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fc9f03d7790 @ 172) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5 5566ae293a80 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7fc9f03d78b0 @ 17) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7 5566ae293a00 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7fc9f03d2f70 @ 42) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9 5566ae293978 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7fc9f03c2dc0 @ 82) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11 5566ae2938e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7fc9f03cf1f0 @ 116) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13 5566ae293860 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7fc9f03cf5e0 @ 37) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15 5566ae2937e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7fc9f03c2550 @ 12) Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618328' Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618329' Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1 5566b0c47bf0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3 5566b0c47b38 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fc9f03d7790 @ 172) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5 5566b0c47ab8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7fc9f03d78b0 @ 17) Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor (0x55669ffd87a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7 5566b0c47a38 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7fc9f03d2f70 @ 42) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9 5566b0c479b0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7fc9f03c2dc0 @ 82) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11 5566b0c47918 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7fc9f03cf1f0 @ 116) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13 5566b0c47898 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7fc9f03cf5e0 @ 37) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15 5566b0c47818 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7fc9f03c2550 @ 12) Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined") Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618328' Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618329' Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #1 5566a7f84270 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20)
[Desktop-packages] [Bug 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]
I have found a work-around to get back to desktop. If you have locked the screen and it has hung you can lock/unlock by using the SUPER + L hotkey (Or whatever your shortcut key is). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1804008 Title: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated from ubuntu-d...@ubuntu.com/theming.js:416] Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: All my gnome-shell extensions randomly (apparently) crash. This behavior began when i upgraded to cosmic. Here's a excerpt of my logs: Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor (0x55669ffd87a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1 5566ae293bb8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3 5566ae293b00 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fc9f03d7790 @ 172) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5 5566ae293a80 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7fc9f03d78b0 @ 17) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7 5566ae293a00 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7fc9f03d2f70 @ 42) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9 5566ae293978 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7fc9f03c2dc0 @ 82) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11 5566ae2938e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7fc9f03cf1f0 @ 116) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13 5566ae293860 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7fc9f03cf5e0 @ 37) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15 5566ae2937e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7fc9f03c2550 @ 12) Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618328' Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618329' Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1 5566b0c47bf0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3 5566b0c47b38 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fc9f03d7790 @ 172) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5 5566b0c47ab8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7fc9f03d78b0 @ 17) Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor (0x55669ffd87a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7 5566b0c47a38 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7fc9f03d2f70 @ 42) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9 5566b0c479b0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7fc9f03c2dc0 @ 82) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11 5566b0c47918 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7fc9f03cf1f0 @ 116) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13 5566b0c47898 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7fc9f03cf5e0 @ 37) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15 5566b0c47818 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7fc9f03c2550 @ 12) Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined") Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618328' Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618329' Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #1 5566a7
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
I am still seeing this with Mint 18.3 and 19 on at least 4 different PCs but with nvidia graphics. Is there a fix somewhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796537] [NEW] package sgml-base 1.29 failed to install/upgrade: installed sgml-base package post-installation script subprocess returned error exit status 1
Public bug reported: Error message displayed after running routine upgrade process ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sgml-base 1.29 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: initramfs-tools:amd64: Install initramfs-tools-core:amd64: Install initramfs-tools-bin:amd64: Install metacity-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Oct 7 01:13:45 2018 DuplicateSignature: package:sgml-base:1.29 Processing triggers for sgml-base (1.29) ... cannot rename /var/lib/sgml-base/supercatalog to /var/lib/sgml-base/supercatalog.old: Operation not permitted at /usr/sbin/update-catalog line 322. dpkg: error processing package sgml-base (--configure): installed sgml-base package post-installation script subprocess returned error exit status 1 ErrorMessage: installed sgml-base package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-27 (163 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.29 failed to install/upgrade: installed sgml-base package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sgml-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/1796537 Title: package sgml-base 1.29 failed to install/upgrade: installed sgml-base package post-installation script subprocess returned error exit status 1 Status in sgml-base package in Ubuntu: New Bug description: Error message displayed after running routine upgrade process ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sgml-base 1.29 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: initramfs-tools:amd64: Install initramfs-tools-core:amd64: Install initramfs-tools-bin:amd64: Install metacity-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Oct 7 01:13:45 2018 DuplicateSignature: package:sgml-base:1.29 Processing triggers for sgml-base (1.29) ... cannot rename /var/lib/sgml-base/supercatalog to /var/lib/sgml-base/supercatalog.old: Operation not permitted at /usr/sbin/update-catalog line 322. dpkg: error processing package sgml-base (--configure): installed sgml-base package post-installation script subprocess returned error exit status 1 ErrorMessage: installed sgml-base package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-27 (163 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.29 failed to install/upgrade: installed sgml-base package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1796537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Worked for me thanx :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were encountered while processing: /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` ProblemType: Package DistroRe
[Desktop-packages] [Bug 1260405] Re: Keyboard input not working in Reply To Message dialog
I can no longer reproduce this in the version of Thunderbird I currently have installed: 52.8.0 (64-bit) I think you can close it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1260405 Title: Keyboard input not working in Reply To Message dialog Status in thunderbird package in Ubuntu: Incomplete Bug description: Description:Ubuntu 12.04.3 LTS Release:12.04 thunderbird: Installed: 1:24.2.0+build1-0ubuntu0.12.04.1 Note: KDE desktop (kubuntu)! kde-runtime: Installed: 4:4.8.5-0ubuntu0.2 For the first time I attempt to reply to a message after starting thunderbird, everything seems fine. When I attept to reply to any further message the dialog pane will not accept keyboard input, or even display a caret, in the message text area or even any of the header input fields. Restarting thunderbird appears to clear the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1260405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown
Problem occurs 100% of the time on two Mint Cinnamon 64 bit machines after the latest round of updates when shutting down or restarting from whisker menu. 'shutdown (-r) now' works without an error. The most commonly reported 'fix' for this problem is purging old kernels. I just reinstalled 18.3 Cinnamon 64 from scratch on one and then installed all the updates. There were only 2 kernels. I removed 4.10 4.13.0-36 is the only one installed. It did not fix the problem. I did not have the problem before the last round of updates. Also on another computer with 18.2 which has not been turned on for a while I never had the problem until I just installed updates. It is using 4.10.0-33 kernel. 4.8.0.53, 4.10.0-33, and 4.13.0-36 are installed. I had no problem with on two 18.3 XFCE 64 bit machines. One I last used/updated Sunday 3/4 or another I just updated (including latest kernel) as of 3/8/18 0245Z. All computers are set for autologin. I tried turning autologin off on one Cinnamon but that had no effect. It appears there is something in the recent updates for Cinnamon that is causing this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/608162 Title: GNOME Keyring Daemon stops panel's shutdown Status in gnome-keyring package in Ubuntu: Invalid Bug description: Binary package hint: gnome-keyring Almost every time I click "Shut Down" from the panel's menu for it, I get an error that says: "GNOME-Keyring-Daemon is not responding." Then I can choose "Shut Down anyway" and the computer usually turns off after that, but sometimes I need to use a sudo shutdown command. Also, sometimes when I select "Shut Down" from the panel, nothing happens at all. Again, I need to use a sudo shutdown command to turn off the computer. This happens for all of the users on this computer (a Thinkpad laptop). This issue is particularly annoying for non-administrator users, because if selecting "Shut Down" from the panel doesn't work they cannot issue a sudo shutdown command - which means I need to assist them in changing to a tty terminal, logging in as me, and then giving the sudo shutdown command. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Wed Jul 21 20:17:15 2010 ExecutablePath: /usr/bin/gnome-keyring-daemon InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
I can confirm that #19 works, as well. Also applied the suggestions in #24. Ubuntu 17.10 on a Lenovo Ideapad Y910-17ISK with a GTX 1070. I don't notice any flicker or any problem. The audio device has just appeared, and everything works fine now :-) Thanks a lot!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710382] Re: Wireless network frequently drops in 17.10
I am also having the same problem w/ 17.10. Maybe be a duplicate of bug 1726187 and 1736690. I am also having issues with my WiFi connection dropping out, freezing, etc. I see other bugs reported as well for 17.10 / 18.04 Ubunutu. I am using latest 17.10 build, clean install. Laptop: Yoga 11e Kernel: 4.13.0-21-generic WiFi: Network controller: Intel Corporation Wireless 7265 (rev 61) Occasionally it works when connecting, then stops. What I find most peculiar is that I discovered the DNS appears to intermittently stop 'while' I am using the computer online. If I manually edit "/etc/resolv.conf" (which you shouldn't have to do), and change "nameserver 127.0.0.53" to "nameserver 8.8.8.8". Then save, everything works fine and is stable until the next reboot! I don't think this is a driver/kernel issue, its almost like resolv.conf is broken. -- 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/1710382 Title: Wireless network frequently drops in 17.10 Status in network-manager package in Ubuntu: Confirmed Bug description: On a fairly clean 17.10 install, on a Thinkpad T450, the wireless connection keeps dropping. Other devices nearby do not suffer the same way. I can turn the wifi off and on again to get reconnected. It happens multiple times over a short period of an hour or so. So quite irritating. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Aug 12 15:52:20 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-02 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.124.121.0/24 dev lxdbr0 proto kernel scope link src 10.124.121.1 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxdbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/27 lxdbr0 9e57f30a-21b5-4f87-aa76-06a328c24462 /org/freedesktop/NetworkManager/ActiveConnection/10 wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 popey b83cf629-38b9-47dc-8916-3aaa2868e90a /org/freedesktop/NetworkManager/ActiveConnection/6 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1710382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726187] Re: After 17.04 -> 17.10 upgrade, wifi often freezes
I am also having issues with my WiFi connection dropping out, freezing, etc. I see other bugs reported as well for 17.10 / 18.04 Ubunutu. I am using latest 17.10 build, clean install. Laptop: Yoga 11e Kernel: 4.13.0-21-generic WiFi: Network controller: Intel Corporation Wireless 7265 (rev 61) Occasionally it works when connecting, then stops. What I find most peculiar is that I discovered the DNS appears to intermittently stop while I am using the computer. If I manually edit "/etc/resolv.conf" (which you shouldn't have to do), and change "nameserver 127.0.0.53" to "nameserver 8.8.8.8". Once saved everything works fine and is stable until the next reboot. I don't think this is a driver/kernel issue, its almost like resolv.conf is broken. -- 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/1726187 Title: After 17.04 -> 17.10 upgrade, wifi often freezes Status in network-manager package in Ubuntu: New Bug description: (might be incorrect package) About once every few hours, my wifi locks up until I use "turn off + turn on" in the network control - upper right corner drop down. This has started happening after the upgrade from 17.04 to 17.10. The wireless signal is very strong, and it remains strong even after lock up. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 20:41:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-13 (192 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.2.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.2.0/24 dev wlp58s0 proto kernel scope link src 192.168.2.131 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 c1be4834-7fc1-4167-8509-90e5d1946c14 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 pups4bf35394-3e64-4dbe-b1b2-5d1953df7058 /org/freedesktop/NetworkManager/ActiveConnection/14 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work
Looks like this may be the same issue as this bug still not resolved. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1704765 -- 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/1741777 Title: drag and drop between desktop and nautilus doesn't work Status in nautilus package in Ubuntu: Confirmed Bug description: I open a nautilus window and try to drag a file from the desktop to this window. It's not done and the arrow pointer of the mouse become a close hand and you cannot use it anymore to click anywhere. Session Wayland ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 7 19:19:23 2018 InstallationDate: Installed on 2016-04-30 (617 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-23 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704765] Re: can't drag file from desktop to folder window on Artful
I confirm this issue as well. Using latest build of 17.10 and updated. It requires me to log off/on to get things working again. I found multiple duplicate bugs on this issue, and yes...wonder why its not fixed? -- 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/1704765 Title: can't drag file from desktop to folder window on Artful Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I'm running Ubuntu 17.10 (Artful). If I create a text file on my desktop and then attempt to drag it into a Nautilus folder window, it fails: when I release the mouse cursor over the folder window nothing happens and the file is not moved. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work
I confirm I have this exact problem. Using latest build of Ubuntu 17.10 (Wayland)from Jan 2018. Note: This bug also seems very similar to this one. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729887 -- 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/1741777 Title: drag and drop between desktop and nautilus doesn't work Status in nautilus package in Ubuntu: Confirmed Bug description: I open a nautilus window and try to drag a file from the desktop to this window. It's not done and the arrow pointer of the mouse become a close hand and you cannot use it anymore to click anywhere. Session Wayland ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 7 19:19:23 2018 InstallationDate: Installed on 2016-04-30 (617 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-23 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Ubuntu: 17.10 Mainline Kernel: 4.14.7 Still not working :( anti-egos fix didn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
@zmoazeni: Stopping the service does indeed stop the log spam on my machine. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Xenial: Confirmed Bug description: Since updating to 16.04 from 14.04, I have the syslog spammed by: SEC: May 22 13:26:43 samsung-romano pkexec[21248]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 1766] SEC: May 22 13:26:43 samsung-romano pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1153) SEC: May 22 13:26:43 samsung-romano pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session SEC: May 22 13:26:43 samsung-romano pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device SEC: May 22 13:26:43 samsung-romano pkexec[21249]: romano: Executing command [USER=root] [TTY=unknown] [CWD=/home/romano] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 4322] SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: Error executing command as another user: Not authorized SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: This incident has been reported. every couple of seconds or so. There is no really need to change brightness... how can I stop it? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Changed in: indicator-network (Ubuntu) Status: Incomplete => Invalid -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in Canonical System Image: Fix Released Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Fix Released Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567250] Re: ssh signin problem since OTA-10
** Changed in: gnome-keyring (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1567250 Title: ssh signin problem since OTA-10 Status in Canonical System Image: Confirmed Status in Ubuntu Terminal App: Incomplete Status in gnome-keyring package in Ubuntu: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Bug description: Not sure if this is a terminal or image issue, but here goes. Since the update last night to OTA-10 I cannot ssh to a server anymore. Error message: "Agent Admitted Failure To Sign Using The Key" On server side and client side nothing changed to the user settings or keys. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1018361] Re: unity-greeter crashed with SIGSEGV in gtk_widget_translate_coordinates()
** Changed in: unity-greeter (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/unity-greeter/+question/658602 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1018361 Title: unity-greeter crashed with SIGSEGV in gtk_widget_translate_coordinates() Status in unity-greeter package in Ubuntu: Invalid Bug description: Not sure when exactly this happened. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity-greeter 12.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4 Uname: Linux 3.5.0-2-generic i686 ApportVersion: 2.2.5-0ubuntu1 Architecture: i386 Date: Tue Jun 26 23:18:05 2012 ExecutablePath: /usr/sbin/unity-greeter InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110422) ProcCmdline: /usr/sbin/unity-greeter ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb74fd8b3 : mov0xc(%esi),%ebp PC (0xb74fd8b3) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%ebp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-greeter Title: unity-greeter crashed with SIGSEGV in gtk_widget_translate_coordinates() UpgradeStatus: Upgraded to quantal on 2012-06-15 (11 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1018361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
This affects linux-aws 4.4.0-1020-aws as well. I ran into this issue on that kernel. https://github.com/collectd/collectd/issues/2321#issuecomment-311634825 Seems maybe fixed in 4.4.0-1022-aws ** Bug watch added: github.com/collectd/collectd/issues #2321 https://github.com/collectd/collectd/issues/2321 -- 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/1699772 Title: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux- image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in commons-daemon package in Ubuntu: Confirmed Status in eclipse package in Ubuntu: Confirmed Status in imagej package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in octave package in Ubuntu: Confirmed Status in python-jpype package in Ubuntu: Confirmed Status in rustc package in Ubuntu: Confirmed Status in scilab package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support
** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- 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/1597681 Title: [CTA] Enable WAPI support Status in Canonical System Image: In Progress Status in indicator-network package in Ubuntu: In Progress Status in network-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: The phone does not currently support WAPI [1] It should do so. As part of this, support for the SMS4 [2] cipher is also required. [1] https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure [2]: https://en.wikipedia.org/wiki/SMS4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1560498 Title: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_mir.c:138] Status in Mir: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.04.20160310.4-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670717] [NEW] Unity8/mir working on VMware due to bypass not working
Public bug reported: Related to this bug (bug #1480755) - this is the issue preventing unity8/mir working in VMware. Bringing it out into its own issue to improve visibility. Choice quotes from previous bug: The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell) returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them have EGL_ALPHA_SIZE == 8 set. Added a Mesa task. RAOF has suggested we should just fix Mesa. When asking for RGBA of 8880 it should provide at least one EGLConfig that is 8880 instead of always . This should be possible. It's not entirely clear why we're not getting XRGB visuals currently, but it's fixable. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: Related to this bug (#1480755) - this is the issue preventing unity8/mir working in VMware. Bringing it out into its own issue to improve visibility. + + Choice quotes from previous bug: The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell) returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them have EGL_ALPHA_SIZE == 8 set. Added a Mesa task. RAOF has suggested we should just fix Mesa. When asking for RGBA of 8880 it should provide at least one EGLConfig that is 8880 instead of always . This should be possible. It's not entirely clear why we're not getting XRGB visuals currently, but it's fixable. ** Summary changed: - Mesa returning incorrect EGLConfigs preventing unity8/mir working on VMware + Unity8/mir working on VMware due to bypass not working ** Description changed: - Related to this bug (#1480755) - this is the issue preventing unity8/mir - working in VMware. + Related to this bug (bug #1480755) - this is the issue preventing + unity8/mir working in VMware. Bringing it out into its own issue to improve visibility. Choice quotes from previous bug: The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell) returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them have EGL_ALPHA_SIZE == 8 set. Added a Mesa task. RAOF has suggested we should just fix Mesa. When asking for RGBA of 8880 it should provide at least one EGLConfig that is 8880 instead of always . This should be possible. It's not entirely clear why we're not getting XRGB visuals currently, but it's fixable. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1670717 Title: Unity8/mir working on VMware due to bypass not working Status in mesa package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Related to this bug (bug #1480755) - this is the issue preventing unity8/mir working in VMware. Bringing it out into its own issue to improve visibility. Choice quotes from previous bug: The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell) returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them have EGL_ALPHA_SIZE == 8 set. Added a Mesa task. RAOF has suggested we should just fix Mesa. When asking for RGBA of 8880 it should provide at least one EGLConfig that is 8880 instead of always . This should be possible. It's not entirely clear why we're not getting XRGB visuals currently, but it's fixable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1670717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
Or if not (I'm no graphics programmer), that's at least the comparable snippet, I think? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1560498 Title: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_mir.c:138] Status in Mir: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.04.20160310.4-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
I *think* it looks like there's something similar going on inside QtMir
(http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/screen.cpp#L60):
enum QImage::Format qImageFormatFromMirPixelFormat(MirPixelFormat
mirPixelFormat) {
switch (mirPixelFormat) {
case mir_pixel_format_abgr_:
if (isLittleEndian()) {
// 0xRR,0xGG,0xBB,0xAA
return QImage::Format_RGBA;
} else {
// 0xAA,0xBB,0xGG,0xRR
qFatal("[mirserver QPA] "
"Qt doesn't support mir_pixel_format_abgr_ in a big
endian architecture");
}
break;
case mir_pixel_format_xbgr_:
if (isLittleEndian()) {
// 0xRR,0xGG,0xBB,0xXX
return QImage::Format_RGBX;
} else {
// 0xXX,0xBB,0xGG,0xRR
qFatal("[mirserver QPA] "
"Qt doesn't support mir_pixel_format_xbgr_ in a big
endian architecture");
}
break;
break;
case mir_pixel_format_argb_:
// 0xAARRGGBB
return QImage::Format_ARGB32;
break;
case mir_pixel_format_xrgb_:
// 0xffRRGGBB
return QImage::Format_RGB32;
break;
case mir_pixel_format_bgr_888:
qFatal("[mirserver QPA] Qt doesn't support mir_pixel_format_bgr_888");
break;
default:
qFatal("[mirserver QPA] Unknown mir pixel format");
break;
}
return QImage::Format_Invalid;
}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
mir::graphics::nested::detail::DisplayBuffer::make_current() ->
eglMakeCurrent() -> ... -> dri2_image_get_buffers()
[platform_mir.c:138]
Status in Mir:
Triaged
Status in mesa package in Ubuntu:
Triaged
Status in mir package in Ubuntu:
Triaged
Status in unity8 package in Ubuntu:
Invalid
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8. This problem was most recently seen with version
8.11+16.04.20160310.4-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
Guys, is it worth looping in Thomas Hellstrom and/or Jakob Bornecrantz to this bug? IIRC they were interested in getting the VMware driving working with Mir a while ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1560498 Title: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_mir.c:138] Status in Mir: New Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.04.20160310.4-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642454] Re: Installing Network Printer via Add Printer wizard creates incorrect Device URI (Ubuntu 16.04)
Sorry, attachment had duplicate screenshots, I have attached a corrected version. ** Attachment added: "Ubuntu_Printing-16.04_Brother_Test_UPDATED.pdf" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1642454/+attachment/4780619/+files/Ubuntu_Printing-16.04_Brother_Test_UPDATED.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1642454 Title: Installing Network Printer via Add Printer wizard creates incorrect Device URI (Ubuntu 16.04) Status in system-config-printer package in Ubuntu: New Bug description: Hello, Installing a network printer in Ubuntu 16.04 appears to install the incorrect Device URI. Summary: I am not sure how the Device URI is supposed to work in Ubuntu, but installing the printer using the Ubuntu Add Printer wizard (GUI) a string of alpha characters is entered. Users are unable to print. However, manually changing this to the Printer IP address does allow printing to work. I confirmed this issue with four separate machines all running clean installations of Ubuntu 16.04 with no modifications, and updates applied. *Please see attached PDF with installation procedure and screenshots for details. -- Installation Example: Example network printer: Brother DCP-L2540DW (Static IP: 192.168.1.20) Procedure: *Adding the printer: "Settings > Printer > Add" *Select printer under "Network Printer", Host Name shows "BRN30055C829554". *Complete installation after selecting an acceptable driver. *Printer does NOT print. Printer Properties shows "Device URI": "lpd://BRN30055C829554/BINARY_P1" *Changing Device URI to printer IP (using "Change" option) corrects Device URI to IP address "lpd://192.168.1.20/BINARY_P1" *Printing is now successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1642454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642454] Re: Installing Network Printer via Add Printer wizard creates incorrect Device URI (Ubuntu 16.04)
Completed some further testing on a network with Brother Printer. I confirmed the following results on two seperate Linux machines (laptop over WiFi and Ethernet) and Desktop machine. Both had the same results. Example network printer: Brother DCP-L2540DW (Static IP: 192.168.1.20) There are two options to select when the Brother network printer is detected (see my attached screenshots for examples). The first option: Shows HOST field “BRN30055C829554” and Queue: “BINARY_P1”. This option STILL does not work for me, however if I change the Device URI to the printer IP I can print successfully (as mentioned earlier). However, the second option did not used to work either for me, but now appears to work correctly! This method uses “IPP network printer via DNS-SD” option does now appear to work (see screenshot below). I still think the default selection (first option) needs resolved. See below and attachment for details: The first option: Shows HOST field “BRN30055C829554” and Queue: “BINARY_P1”. My printer driver (Brother DCP-L2540DW) is not shown. Driver chosen is DCP-7045N driver (which also works) and click “Forward”. (See below) Auto created Device URI: “lpd://BRN30055C829554/BINARY_P1” Second Option: Using “IPP network printer via DNS-SD” option does now appear to work (see below)! Auto created Device URI: "dnssd://Brother%20DCP-L2540DW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c829554" ** Attachment added: "Ubuntu_Printing-16.04_Brother_Test_UPDATED.pdf" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1642454/+attachment/4780618/+files/Ubuntu_Printing-16.04_Brother_Test_UPDATED.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1642454 Title: Installing Network Printer via Add Printer wizard creates incorrect Device URI (Ubuntu 16.04) Status in system-config-printer package in Ubuntu: New Bug description: Hello, Installing a network printer in Ubuntu 16.04 appears to install the incorrect Device URI. Summary: I am not sure how the Device URI is supposed to work in Ubuntu, but installing the printer using the Ubuntu Add Printer wizard (GUI) a string of alpha characters is entered. Users are unable to print. However, manually changing this to the Printer IP address does allow printing to work. I confirmed this issue with four separate machines all running clean installations of Ubuntu 16.04 with no modifications, and updates applied. *Please see attached PDF with installation procedure and screenshots for details. -- Installation Example: Example network printer: Brother DCP-L2540DW (Static IP: 192.168.1.20) Procedure: *Adding the printer: "Settings > Printer > Add" *Select printer under "Network Printer", Host Name shows "BRN30055C829554". *Complete installation after selecting an acceptable driver. *Printer does NOT print. Printer Properties shows "Device URI": "lpd://BRN30055C829554/BINARY_P1" *Changing Device URI to printer IP (using "Change" option) corrects Device URI to IP address "lpd://192.168.1.20/BINARY_P1" *Printing is now successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1642454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642454] Re: Installing Network Printer via Add Printer wizard creates incorrect Device URI (Ubuntu 16.04)
Hello, I have completed additional testing at an office. I wanted to test the Ubuntu printer installation wizard on various printers. I completed testing on three printer. All printed successfully. So I am thinking this is an issue with Brother printers only. I have attached a PDF with screenshots and details on the three printers below. Each creates different Device URI's that don't appear related. However they all seem to work just fine! Printers Tested: Dell S2815dn0 Lexmark C540CMD Lexmark X658de - MY TEST RESULTS - Printer: Dell S2815dn IP: 192.168.1.22 Driver chosen during installation wizard (actual printer not listed): Dell 3000cn Auto created Device URI: "dnssd://Dell%20MFP%20S2815dn%20(EE%3A3D%3A78)._pdl-datastream._tcp.local/?uuid=f436bd00-1dd2-11b2-99d2-080037ee3d78" - Printer: Lexmark C540CMD IP: 192.168.1.203 Driver chosen during installation wizard: C540 Auto created Device URI: “dnssd://Lexmark%20C540._pdl-datastream._tcp.local/” --- Note: The Lexmark X658de shows two options when installing the printer over the network (see details below). Both options print successfully! Printer: Lexmark X658de IP: 192.168.1.201 This shows two printers (can choose either to install). --- First HOST field is the IP address (see screenshot below). Correct Driver successfully found and installed automatically! This prints successfully. Auto created Device URI: “socket://192.168.1.201:9100” --- The second HOST field shows “IPP Network Printer via DNS-SD” (see below). Driver chosen during installation wizard: “X658de” Auto created Device URI: “dnssd://Lexmark%20X658de._ipp._tcp.local/?uuid=b16c08c8-ad54-4196-82b5-6033f05f1a45” ** Attachment added: "Ubuntu-16.04_Network_Printing_Test_Results.pdf" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1642454/+attachment/4780558/+files/Ubuntu-16.04_Network_Printing_Test_Results.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1642454 Title: Installing Network Printer via Add Printer wizard creates incorrect Device URI (Ubuntu 16.04) Status in system-config-printer package in Ubuntu: New Bug description: Hello, Installing a network printer in Ubuntu 16.04 appears to install the incorrect Device URI. Summary: I am not sure how the Device URI is supposed to work in Ubuntu, but installing the printer using the Ubuntu Add Printer wizard (GUI) a string of alpha characters is entered. Users are unable to print. However, manually changing this to the Printer IP address does allow printing to work. I confirmed this issue with four separate machines all running clean installations of Ubuntu 16.04 with no modifications, and updates applied. *Please see attached PDF with installation procedure and screenshots for details. -- Installation Example: Example network printer: Brother DCP-L2540DW (Static IP: 192.168.1.20) Procedure: *Adding the printer: "Settings > Printer > Add" *Select printer under "Network Printer", Host Name shows "BRN30055C829554". *Complete installation after selecting an acceptable driver. *Printer does NOT print. Printer Properties shows "Device URI": "lpd://BRN30055C829554/BINARY_P1" *Changing Device URI to printer IP (using "Change" option) corrects Device URI to IP address "lpd://192.168.1.20/BINARY_P1" *Printing is now successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1642454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588126] Re: [regression] Adding new wifi networks (with long passwords) never connect at all in OTA-11 and OTA-12
** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) => Pete Woods (pete-woods) -- 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/1588126 Title: [regression] Adding new wifi networks (with long passwords) never connect at all in OTA-11 and OTA-12 Status in Canonical System Image: Fix Committed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Fix Committed Bug description: I've just flashed clean images of OTA-11 from the stable channel onto a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the phones can see the wifi networks but can't connect to any of them any more. The wifi networks continue to work for non-Ubuntu devices. Also, forcefully flashing a device with OTA-10 fixes the problem. The regression began in OTA-11. Explanation: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567250] Re: ssh signin problem since OTA-10
** Changed in: indicator-network (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1567250 Title: ssh signin problem since OTA-10 Status in Canonical System Image: Confirmed Status in Ubuntu Terminal App: Incomplete Status in gnome-keyring package in Ubuntu: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Bug description: Not sure if this is a terminal or image issue, but here goes. Since the update last night to OTA-10 I cannot ssh to a server anymore. Error message: "Agent Admitted Failure To Sign Using The Key" On server side and client side nothing changed to the user settings or keys. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support
FYI, that indiactor-network branch requires the upcoming changes from Tony's network-manager branch to build successfully (depends on a new enum value). -- 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/1597681 Title: [CTA] Enable WAPI support Status in Canonical System Image: In Progress Status in indicator-network package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: The phone does not currently support WAPI [1] It should do so. As part of this, support for the SMS4 [2] cipher is also required. [1] https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure [2]: https://en.wikipedia.org/wiki/SMS4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support
** Changed in: indicator-network (Ubuntu) Status: Confirmed => In Progress -- 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/1597681 Title: [CTA] Enable WAPI support Status in Canonical System Image: In Progress Status in indicator-network package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: The phone does not currently support WAPI [1] It should do so. As part of this, support for the SMS4 [2] cipher is also required. [1] https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure [2]: https://en.wikipedia.org/wiki/SMS4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11
Tony, if I remember correctly, gdbus proxies all inherit from the GDBusProxy class. I *think* you should be able to use the method g_dbus_proxy_set_default_timeout(...) on the proxy instance you use to talk to the secret agent, so that all subsequent IPC method calls use the larger timeout. I would also suggest a much larger timeout than 2 minutes. -- 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/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS 12.4-25d.JA2) stopped working, possibly due to the length of the WPA pass-phrase, which was 29 characters long. The pass-phrase requirement is from 8 to 63 characters. After reducing the pass- phrase to 14 (and sometimes 15) characters connectivity is restored. Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both 802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot connect. The pass-phrase length requirement on both radios is 18 to 128 characters. In both cases the Cisco APs do not log any event. Prior to OTA 11 connectivity worked normally on OTA 10.1 OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11
My hypothesis is that the upgrade of network-manager to 1.2, which included a port from dbus-glib to gdbus, could have accidentally introduced timeouts to the method invokations from network-manager to the secret agent. Someone probably needs to check out that bit of code and see if a longer timeout can be set. -- 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/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS 12.4-25d.JA2) stopped working, possibly due to the length of the WPA pass-phrase, which was 29 characters long. The pass-phrase requirement is from 8 to 63 characters. After reducing the pass- phrase to 14 (and sometimes 15) characters connectivity is restored. Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both 802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot connect. The pass-phrase length requirement on both radios is 18 to 128 characters. In both cases the Cisco APs do not log any event. Prior to OTA 11 connectivity worked normally on OTA 10.1 OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11
This sounds like a timeout issue in the comms between the secret agent (the program that presents the dialog to the user) and indicator- network. -- 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/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS 12.4-25d.JA2) stopped working, possibly due to the length of the WPA pass-phrase, which was 29 characters long. The pass-phrase requirement is from 8 to 63 characters. After reducing the pass- phrase to 14 (and sometimes 15) characters connectivity is restored. Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both 802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot connect. The pass-phrase length requirement on both radios is 18 to 128 characters. In both cases the Cisco APs do not log any event. Prior to OTA 11 connectivity worked normally on OTA 10.1 OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1324722] Re: SWF files are not open in a web browser
** Changed in: adobe-flash-plugin-tools Status: Confirmed => Fix Committed -- 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/1324722 Title: SWF files are not open in a web browser Status in Adobe Flash Plugin Tools: Fix Committed Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: Since the update to Ubuntu 14.04 Trusty Tahr, ShockWave Flash files are not open in a web browser anymore. Indeed, when I clicking on it or when I use the Open with > "Name_of_one_brother" entry of the contextual menu, the browser open a download dialogue box instead of opening the file. The only way to launch the animation is to include it in a HTML file using an EMBED element. I actually have flasplugin-installer 11.2.202.291ubuntu0.13.04.1 installed on my computer and I use Mozilla Firefox 29.0. According to http://forum.ubuntu-fr.org/viewtopic.php?id=1531681 , it seems that problem affect several users. To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1324722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588533] Re: Mobile Data Network not working after screen is off for more then 2 min
** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- 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/1588533 Title: Mobile Data Network not working after screen is off for more then 2 min Status in Canonical System Image: New Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in ofono package in Ubuntu: New Bug description: With OTA-11 the Mobile Network 3G and H do not come back into working mode after MX4 comes back from turning off the screen. Example: I reboot the MX4 and when it powers up all is working I get WiFi and Mobile Network 3G working great. I press the button to turn off the screen and leave it off for 2 or more minutes, when I turn it back on and unlock the device the Data network is not working. I can make calls and SMS but MMS and Data has no connection, at this point i can toggle the Data switch in the mobile configuration or put the phone into airplane mode and back into active and it works until next time. Thank You To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1581070] Re: Data connection drops after x time
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu) Status: Confirmed => New -- 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/1581070 Title: Data connection drops after x time Status in Canonical System Image: New Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in ofono package in Ubuntu: New Bug description: Device: Meizu MX4 Ubuntu Edition (ARALE-MEIZU) OS: Ubuntu 15.04 (r323) Ubuntu Image 20160512 armhf (20160512-020304) Device Image 20160331-e14fc2 Adaptation Image 20160504-975-19-6 (above Image descriptions may be wrong, i'm working from Dutch Locale) problem exists since estimated sunday, May 8 2016 expected behavior: - Data connection remains up until manually specified otherwise - when connection is lost due to external causes (such as bad signal), data connection is automatically restored when available - same for Wifi. encoutered behavior: - after x amount of time (x varies between 1 and 4 hours so far) data and wifi connection is lost, and neither data or wifi will reconnect until I manually switch to flight-mode and back. - may also affect SIM status see also https://plus.google.com/106203549473766388410/posts/GFJAcs32kKa I am willing to supply log files or enter terminal commands, but need to be instructed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579825] Re: IP Address not displayed for wifi access points
indicator-network is not involved in reading the IP address of connections. ** Changed in: indicator-network (Ubuntu) Status: New => Invalid -- 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/1579825 Title: IP Address not displayed for wifi access points Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: latest rc-proposed build 319 Open system settings expand the connected access point by pressing right arrow expected results: ip address is displayed actual results: ip address is not displayed, just a label "IP Address" with no value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1579825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565308] [NEW] gst-plugin-scanner crashed with signal 5 in _XReply()
Public bug reported: Occurred during startup. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 2 12:38:31 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner InstallationDate: Installed on 2016-03-23 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcCmdline: /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 5 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: gst-plugin-scanner crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1565308 Title: gst-plugin-scanner crashed with signal 5 in _XReply() Status in gstreamer1.0 package in Ubuntu: New Bug description: Occurred during startup. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Sat Apr 2 12:38:31 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner InstallationDate: Installed on 2016-03-23 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcCmdline: /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 5 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: gst-plugin-scanner crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1565308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551823] Re: PPTP connection does not work and dies after 2 minutes (on the phone)
** Changed in: indicator-network (Ubuntu) Status: Confirmed => Invalid -- 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/1551823 Title: PPTP connection does not work and dies after 2 minutes (on the phone) Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: $ system-image-cli -i current build number: 378 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-03-01 15:10:52 version version: 378 version ubuntu: 20160301 version device: 20160112 version custom: 20160301 Also confirmed for krillin. Reproduce: 1. Create PPTP connection that you know works (my PPTP connection works on the desktop) 2. Enable it Logs from enabling to “ppp up”: http://pastebin.ubuntu.com/15260269/ What happens: No data flow, can't load anything inside/outside the domain (?) What should happen: Expected this to work, I see a pptp connection in ifconfig [1] Error log from death of pptp connection: http://pastebin.ubuntu.com/15259871/ [1] ppp0 Link encap:Point-to-Point Protocol inet addr:xxx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xxx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:30658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1024 (1.0 KB) TX bytes:13791931 (13.7 MB) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551823] Re: PPTP connection does not work and dies after 2 minutes (on the phone)
** Summary changed: - [vpn] PPTP connection does not work and dies after 2 minutes + PPTP connection does not work and dies after 2 minutes (on the phone) -- 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/1551823 Title: PPTP connection does not work and dies after 2 minutes (on the phone) Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 378 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-03-01 15:10:52 version version: 378 version ubuntu: 20160301 version device: 20160112 version custom: 20160301 Also confirmed for krillin. Reproduce: 1. Install silo 38 on a very recent phone image (built after 28th of February 2016) 2. Create PPTP connection that you know works (my PPTP connection works on the desktop) 3. Enable it Logs from enabling to “ppp up”: http://pastebin.ubuntu.com/15260269/ What happens: No data flow, can't load anything inside/outside the domain (?) What should happen: Expected this to work, I see a pptp connection in ifconfig [1] Error log from death of pptp connection: http://pastebin.ubuntu.com/15259871/ [1] ppp0 Link encap:Point-to-Point Protocol inet addr:xxx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xxx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:30658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1024 (1.0 KB) TX bytes:13791931 (13.7 MB) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551823] Re: PPTP connection does not work and dies after 2 minutes
Sorry, but I don't know how to fix this. We need someone who actually understands network manager internals, and the PPTP plugin. -- 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/1551823 Title: PPTP connection does not work and dies after 2 minutes Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 378 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-03-01 15:10:52 version version: 378 version ubuntu: 20160301 version device: 20160112 version custom: 20160301 Also confirmed for krillin. Reproduce: 1. Install silo 38 on a very recent phone image (built after 28th of February 2016) 2. Create PPTP connection that you know works (my PPTP connection works on the desktop) 3. Enable it Logs from enabling to “ppp up”: http://pastebin.ubuntu.com/15260269/ What happens: No data flow, can't load anything inside/outside the domain (?) What should happen: Expected this to work, I see a pptp connection in ifconfig [1] Error log from death of pptp connection: http://pastebin.ubuntu.com/15259871/ [1] ppp0 Link encap:Point-to-Point Protocol inet addr:xxx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xxx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:30658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1024 (1.0 KB) TX bytes:13791931 (13.7 MB) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551823] Re: PPTP connection does not work and dies after 2 minutes
I can confirm this works correctly on a desktop machine. So it's some kind of ARM / phone platform related incompatibility. -- 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/1551823 Title: PPTP connection does not work and dies after 2 minutes Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 378 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-03-01 15:10:52 version version: 378 version ubuntu: 20160301 version device: 20160112 version custom: 20160301 Also confirmed for krillin. Reproduce: 1. Install silo 38 on a very recent phone image (built after 28th of February 2016) 2. Create PPTP connection that you know works (my PPTP connection works on the desktop) 3. Enable it Logs from enabling to “ppp up”: http://pastebin.ubuntu.com/15260269/ What happens: No data flow, can't load anything inside/outside the domain (?) What should happen: Expected this to work, I see a pptp connection in ifconfig [1] Error log from death of pptp connection: http://pastebin.ubuntu.com/15259871/ [1] ppp0 Link encap:Point-to-Point Protocol inet addr:xxx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xxx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:30658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1024 (1.0 KB) TX bytes:13791931 (13.7 MB) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
You are correct, Pat. There is no scanning that is activated when you pull down the networking indicator like in OSX. So this is more likely to be related to waking up. Sounds like the passive network scanning (driver / wpa supplicant?) isn't working when the phone goes into power save mode to me. -- 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/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543030] Re: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM
** No longer affects: gnome-keyring (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1543030 Title: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM Status in libgcrypt20 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-keyring. This problem was most recently seen with version 3.16.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b9e06f40b09d062f6d8ddeccd7df9f305f9dfc9 contains more details. See the upstream bug here: https://bugs.gnupg.org/gnupg/issue2242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt20/+bug/1543030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543030] Re: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM
** Branch unlinked: lp:~pete-woods/ubuntu/wily/libgcrypt20/disable-arm- asm-rijndael ** Branch linked: lp:~pete-woods/ubuntu/xenial/libgcrypt20/disable-arm- asm-rijndael ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-keyring. This problem was most recently seen with version 3.16.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b9e06f40b09d062f6d8ddeccd7df9f305f9dfc9 contains more details. + + See the upstream bug here: https://bugs.gnupg.org/gnupg/issue2242 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1543030 Title: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM Status in gnome-keyring package in Ubuntu: Invalid Status in libgcrypt20 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-keyring. This problem was most recently seen with version 3.16.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b9e06f40b09d062f6d8ddeccd7df9f305f9dfc9 contains more details. See the upstream bug here: https://bugs.gnupg.org/gnupg/issue2242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1543030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543030] Re: /usr/bin/gnome-keyring-daemon:7:_gcry_aes_arm_encrypt_block:do_encrypt_aligned:do_encrypt:_gcry_aes_cbc_enc:_gcry_cipher_cbc_encrypt
** Also affects: libgcrypt20 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-keyring (Ubuntu) Status: New => Invalid ** Changed in: libgcrypt20 (Ubuntu) Status: New => In Progress ** Changed in: libgcrypt20 (Ubuntu) Assignee: (unassigned) => Pete Woods (pete-woods) ** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) => Pete Woods (pete-woods) ** Summary changed: - /usr/bin/gnome-keyring-daemon:7:_gcry_aes_arm_encrypt_block:do_encrypt_aligned:do_encrypt:_gcry_aes_cbc_enc:_gcry_cipher_cbc_encrypt + Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM ** Branch linked: lp:~pete-woods/ubuntu/wily/libgcrypt20/disable-arm- asm-rijndael -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1543030 Title: Crash in gnome-keyring (in libgcrypt AES assembler) when used on ARM Status in gnome-keyring package in Ubuntu: Invalid Status in libgcrypt20 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-keyring. This problem was most recently seen with version 3.16.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b9e06f40b09d062f6d8ddeccd7df9f305f9dfc9 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1543030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1482636] Re: Ubuntu Touch on MX4 doesn't connect to WLAN with WEP
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1482636 Title: Ubuntu Touch on MX4 doesn't connect to WLAN with WEP Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hi, while it is no problme to connect to a WLAN with WPA2 it is impossible to connect with a WLAN with WEP. Given that I'm the admin of the WLAN I changed to WPA temporarily and then it was no problem to connect. Thus it is not a hardware problem. Regards Ubuntu Touch Ver. 15.04 (r3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1482636/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while Hotspot is active
I think it's fair to say the issue is likely to be in ofono / somewhere down from there? ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1536195 Title: Can't receive calls and sms while Hotspot is active Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in ofono package in Ubuntu: New Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512831] Re: Flight mode: Wi-Fi re-enabled upon reboot
Pretty sure the permanent state for this (if desired) would live inside
network-manager.
** Changed in: indicator-network (Ubuntu)
Status: New => Confirmed
** Changed in: indicator-network (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: indicator-network (Ubuntu)
Status: Confirmed => Invalid
--
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/1512831
Title:
Flight mode: Wi-Fi re-enabled upon reboot
Status in indicator-network package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
One arale r152 rc-proposed, finding that under flight mode Wi-Fi can
be re-enabled upon reboot, will attach a screenie ("boite_LeSage" is
my home router access point).
TEST CASE:
1. Enable flight mode, verify that flight mode is indicated, Wi-Fi switch is
off.
2. Reboot phone.
EXPECTED:
Flight mode engaged, Wi-Fi disabled.
ACTUAL:
Flight mode engaged, Wi-Fi enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1512831/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532697] Re: No animation for VPN connection with Xenial
Assigning to correct project (network indicator is provided by nm-applet in Unity7 desktop) ** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1532697 Title: No animation for VPN connection with Xenial Status in indicator-network package in Ubuntu: Invalid Status in network-manager-applet package in Ubuntu: New Bug description: Previously, when establishing a VPN connection, the "up-down arrow" icon in the panel displayed a nice animation while connection establishment was in progress. In Xenial, I no longer see that animation. Is this intentional? (The VPN connection still is established just fine, it's just that the animation is missing.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1532697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
Shutting down the thumbnail and nuking the thumbnailer cache didn't help. Following that I restarted unity8-dash, and it started behaving again. Therefore I would surmise that the problem is either in the actual thumbnailer QML plugin, or perhaps in the built-in QML image cache (not really sure how they both interact). I'm about to try restoring the thumbnailer cache to see if it causes the trouble again. -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
Closing network-manager and indicator-network, as I'm pretty sure they aren't the culprit here. ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
Okay, so the thumbnailer is obviously not involved here, as the cache hasn't been re-created and the thumbnailer doesn't get restarted when loading up the store scope. Seems like my research is a red-herring then. ** Changed in: thumbnailer (Ubuntu) Status: New => Invalid ** Changed in: indicator-network (Ubuntu) Status: New => Invalid -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
The phone definitely knows it's connected to the internet, as all the metadata, reviews, etc for apps load in correctly. It's only images that fail. Could this be some kind of problem with the thumbnailer? -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
The fact that all the caches are empty seems pretty strange to me. Maybe I'm misinterpreting that information, though.. ** Also affects: thumbnailer (Ubuntu) Importance: Undecided Status: New -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
$ thumbnailer-admin stats Image cache: Path: /home/phablet/.cache/unity-thumbnailer/images Policy:lru_ttl Size: 0 Size in bytes: 0 Max size in bytes: 52428800 Hits: 0 Misses:0 Hits since last miss: 0 Misses_since_last_hit: 0 Longest hit run: 0 Longest miss run: 0 Avg hit run length:0.00 Avg miss run length: 0.00 TTL evictions: 0 LRU evictions: 0 Most-recent hit time: never Most-recent miss time: never Longest hit-run time: never Longest miss-run time: never Thumbnail cache: Path: /home/phablet/.cache/unity-thumbnailer/thumbnails Policy:lru_ttl Size: 0 Size in bytes: 0 Max size in bytes: 104857600 Hits: 0 Misses:0 Hits since last miss: 0 Misses_since_last_hit: 0 Longest hit run: 0 Longest miss run: 0 Avg hit run length:0.00 Avg miss run length: 0.00 TTL evictions: 0 LRU evictions: 0 Most-recent hit time: never Most-recent miss time: never Longest hit-run time: never Longest miss-run time: never Failure cache: Path: /home/phablet/.cache/unity-thumbnailer/failures Policy:lru_only Size: 0 Size in bytes: 0 Max size in bytes: 2097152 Hits: 0 Misses:0 Hits since last miss: 0 Misses_since_last_hit: 0 Longest hit run: 0 Longest miss run: 0 Avg hit run length:0.00 Avg miss run length: 0.00 TTL evictions: 0 LRU evictions: 0 Most-recent hit time: never Most-recent miss time: never Longest hit-run time: never Longest miss-run time: never -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
I've managed to reproduce this issue on image 153 on my Arale. I had adb connected for the duration and polled the value of the online status, and it was consistently set to "online". Strangely I even get this behaviour after refreshing the store scope. It's as if the failed image requests are cached somehow. -- 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/1507769 Title: App store does not display images Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388201] Re: Toggling wifi on/off causes media playback to hiccup
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: network-manager (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1388201 Title: Toggling wifi on/off causes media playback to hiccup Status in Canonical System Image: Confirmed Status in Network Menu: Invalid Status in network-manager package in Ubuntu: New Bug description: 1. Play a song with music-app 2. Switch wifi off, notice that music-app playback pauses for a moment 3. Switch wifi on, notice that music-app playback pauses for a moment 4. Watch the CPU usage with top while toggling wifi and notice that the usage spikes to 100% Expected results: Music or video keeps playing without pausing while toggling wifi on/off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388201] Re: Toggling wifi on/off causes media playback to hiccup
Worth looking at: https://bugs.launchpad.net/barajas/+bug/1383236 ** This bug is no longer a duplicate of bug 1382283 wifi toggle interrupts sound playback ** Changed in: indicator-network Importance: Undecided => High ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1388201 Title: Toggling wifi on/off causes media playback to hiccup Status in Network Menu: Invalid Status in network-manager package in Ubuntu: New Bug description: 1. Play a song with music-app 2. Switch wifi off, notice that music-app playback pauses for a moment 3. Switch wifi on, notice that music-app playback pauses for a moment 4. Watch the CPU usage with top while toggling wifi and notice that the usage spikes to 100% Expected results: Music or video keeps playing without pausing while toggling wifi on/off To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1388201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback
*** This bug is a duplicate of bug 1388201 *** https://bugs.launchpad.net/bugs/1388201 ** This bug has been marked a duplicate of bug 1388201 Toggling wifi on/off causes media playback to hiccup -- 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/1382283 Title: wifi toggle interrupts sound playback Status in network-manager package in Ubuntu: Invalid Bug description: Not really sure where this bug should go, but on recent rtm krillin images (such as 112), turning wifi on/off in the network indicator causes a brief interruption in music playback. Steps to reproduce the issue: 1. Start playing a song in the music app. 2. Pull down the network indicator. 3. Toggle wi-fi on or off. For some reason, this makes the sound pause for a moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1382283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458046] Re: [touch] NetworkManager needs to inhibit sleep if hotspot is active
** Branch linked: lp:~pete-woods/indicator-network/wakelock-on-hotspot- active ** Changed in: indicator-network (Ubuntu) Importance: Undecided => High ** Changed in: indicator-network (Ubuntu) Status: New => In Progress -- 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/1458046 Title: [touch] NetworkManager needs to inhibit sleep if hotspot is active Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: New Status in network-manager package in Ubuntu RTM: Confirmed Bug description: As Ubuntu touch uses an auto-suspend model, it's possible for the system to be suspended while a user has a hotspot active and in use. In order to prevent such behavior, we should modify NetworkManager to inhibit suspend via powerd's DBus interface when hotspot is active and one or more clients are connected to the hotspot. As a first pass, inhibiting suspend when hotspot is active would probably be sufficient. This could probably be implemented via a NM dispatcher script, which would run when the hotspot is activated. <https://wiki.ubuntu.com/Networking#hotspot-power>: "* Whenever at least one person is using your hotspot, the device should not sleep automatically. * The indicator icon should be different when anyone is connected than when no-one is. * If a hotspot is set up, there should be a “Hotspot” item in the “Ways to reduce battery use” list in “Power” settings." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404783] Re: warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core'
Had this today. I upgraded from 14.04 to 14.10 to 15.04 and somewhere along the line I started getting messages such as Errors were encountered while processing: cups-client printer-driver-postscript-hp printer-driver-foo2zjs cups-bsd cups and W: Unknown Multi-Arch type 'no' for package 'compiz-core' W: Unknown Multi-Arch type 'no' for package 'compiz-gnome' W: Unknown Multi-Arch type 'no' for package 'compiz-core' W: Unknown Multi-Arch type 'no' for package 'compiz-gnome' W: You may want to run apt-get update to correct these problems Unfortunately I didn't document the exact steps I took to resolve the issue, but it was a combination of dpkg --configure -a and apt-get install -f and then going into synaptic and upgrading 'apt' and 'apt-utils' I then used synaptic (as I was in there) to mark all upgrades, and it wen through (with a fair smattering of warnings) to completion. I had an error message at the end: zram-config there is no script in the new version of the package but closed that and then re-ran apt-get update, apt-get upgrade - nothing else to install, so rebooted and everything came up OK. Clearly the apt-get issue identified above was causing a conflict, but a combination of the above sorted it for me. Vivid now running nicely! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1404783 Title: warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core' Status in APT: New Status in Compiz: Invalid Status in compiz package in Ubuntu: Confirmed Bug description: When running apt-get update on Ubuntu vivid I get these warnings: W: Unknown Multi-Arch type 'no' for package 'compiz-core' W: Unknown Multi-Arch type 'no' for package 'compiz-gnome' affects ubuntu/compiz -- bye, pabs https://wiki.debian.org/PaulWise To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1404783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1416424] Re: Wifi list is empty
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Fix Released ** Changed in: indicator-network (Ubuntu) Status: Incomplete => Invalid -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 Systems Effected: Mako Flo Manta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438094] Re: indicator-network aborts when trying to run unexistant dbus method
No-longer applies as we moved to use QDBus ** Changed in: dbus-cpp (Ubuntu) Status: New => Confirmed ** Changed in: indicator-network (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1438094 Title: indicator-network aborts when trying to run unexistant dbus method Status in dbus-cpp package in Ubuntu: Confirmed Status in indicator-network package in Ubuntu: Fix Released Bug description: Run qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus Status in the phone, indicator-network will crash. Attaching backtrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1438094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1452279] [NEW] ubuntu 15-04 dns config not picked up
Public bug reported: I did a clean install of ubuntu 15-04. I have set up a network connection which is working. Nothing on my computer can pick up the DNS server. So I have no DNS name resolution on the machine. Also auto mode will not connect. if i do not put a fixed IP address in my network setup if also won't connect. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1452279 Title: ubuntu 15-04 dns config not picked up Status in network-manager package in Ubuntu: New Bug description: I did a clean install of ubuntu 15-04. I have set up a network connection which is working. Nothing on my computer can pick up the DNS server. So I have no DNS name resolution on the machine. Also auto mode will not connect. if i do not put a fixed IP address in my network setup if also won't connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
I would propose a strategy of having the indicator starting a scan each time it is opened (it doesn't do that now). Then having network manager be responsible for the actual aging, possibly through a new property on the main object called "recent access points" or similar, or by reducing the main list of access points. -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
The hardest part of this for the indicator is knowing exactly when to start doing extra scans. The indicator-network service has no idea when the indicator menu itself is actually opened. For this to work both unity8 and qmenumodel would need to be modified to support the "submenu-action" convention. (https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/139) Adding a filtered model between the raw APs and the current APs based on the last-seen property would be reasonably straight-forward. My main objection would really be that there should really be a consistent strategy for AP aging across all clients. So, e.g. unity7 and unity8 will have the same behaviour. -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1427205] Re: indicator shows (dozens of) out of range access points
** Changed in: indicator-network (Ubuntu) Status: Incomplete => Invalid -- 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/1427205 Title: indicator shows (dozens of) out of range access points Status in the base for Ubuntu mobile products: In Progress Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: In Progress Bug description: current build number: 129 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-03-02 07:41:43 version version: 129 version ubuntu: 20150302 version device: 20150210-95b6a9f version custom: 20150302 TEST CASE: 1. Enable Wifi 2. Have a walk with the DUT outside in an area with lot of visible access points. 3. Walk in and out of range of these access points. EXPECTED RESULT: After the walk only the access points that are in range are visible in the indicator ACTUAL RESULT: All the access points the device saw are listed in the indicator (up to several dozens) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20150217.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Mon Mar 2 14:02:40 2015 InstallationDate: Installed on 2015-03-02 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150302-020203) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1427205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1418143] [NEW] package nvidia-304-updates 304.125-0ubuntu0.0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Driver Update failed on my Intel NUC ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-304-updates 304.125-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: unity-webapps-googledocs: Install nvidia-304-updates: Configure nvidia-current-updates: Configure unity-webapps-googledocs: Configure Architecture: amd64 Date: Thu Jan 29 19:16:05 2015 DpkgHistoryLog: Start-Date: 2015-01-29 19:15:49 Commandline: aptdaemon role='role-install-packages' sender=':1.153' Install: unity-webapps-googledocs:amd64 (2.4.16+14.04.20140411-0ubuntu1.1) DuplicateSignature: package:nvidia-304-updates:304.125-0ubuntu0.0.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-22 (105 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: nvidia-graphics-drivers-304-updates Title: package nvidia-304-updates 304.125-0ubuntu0.0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1418143 Title: package nvidia-304-updates 304.125-0ubuntu0.0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in nvidia-graphics-drivers-304-updates package in Ubuntu: New Bug description: Driver Update failed on my Intel NUC ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-304-updates 304.125-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: unity-webapps-googledocs: Install nvidia-304-updates: Configure nvidia-current-updates: Configure unity-webapps-googledocs: Configure Architecture: amd64 Date: Thu Jan 29 19:16:05 2015 DpkgHistoryLog: Start-Date: 2015-01-29 19:15:49 Commandline: aptdaemon role='role-install-packages' sender=':1.153' Install: unity-webapps-googledocs:amd64 (2.4.16+14.04.20140411-0ubuntu1.1) DuplicateSignature: package:nvidia-304-updates:304.125-0ubuntu0.0.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-22 (105 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: nvidia-graphics-drivers-304-updates Title: package nvidia-304-updates 304.125-0ubuntu0.0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 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-304-updates/+bug/1418143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108064] Re: HUD messes up application's Alt key bindings
HUD itself has nothing to do with keyboard shortcuts. All the user interaction is part of the unity project. ** Changed in: hud (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1108064 Title: HUD messes up application's Alt key bindings Status in Unity: New Status in blender package in Ubuntu: Confirmed Status in emacs23 package in Ubuntu: Confirmed Status in fcitx package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in hud package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Bug description: If Alt-key is assigned to HUD, Alt key doesn't work correctly in some applications. For example, Blender doesn't accept Alt key press at all. See a bug report in Blender bug tracker for detail: http://projects.blender.org/tracker/?func=detail&atid=498&aid=33831&group_id=9 When pressing Alt key, Blender receives unnecessary FocusOut and FocusIn events, so Blender immediately forgets the Alt key is pressed down. Blender developer was very angry with Unity's such strange behavior. In Emacs, after select a region, Alt key press sometimes cancels the selection unexpectedly, so I can do nothing in the region. Unity 6.12.0-0ubuntu0.2 Ubuntu 12.10 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1108064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1393088] Re: Pressing Alt+ in a single cycle triggers HUD, Holding Alt then Pressing does not.
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: hud (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1393088 Title: Pressing Alt+ in a single cycle triggers HUD, Holding Alt then Pressing does not. Status in “hud” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Bug description: This is triggered mostly for me in Firefox, where I use Alt+D to switch to the address bar, however, if I do this in the same "cycle" or period of time I'd usually press a single key, then it triggers the HUD, but if I consiously press and hold Alt, then press D and release both at the same time, it doesn't. I've worked around this for now by remapping the HUD (following http://ubuntuguide.net/disable-unitys-hud-head-up-display-or-change- keyboard-shortcut) however, it would appear that there's no check for another key being pressed in the same time window. Aside from re-mapping, is there anything else I could be doing here? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 14.04+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 15 22:10:36 2014 InstallationDate: Installed on 2014-02-18 (270 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140217) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1393088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1358918] Re: ubuntu-location-serviced cpu usage spikes to 100% occasionally
Core file from indicator-network
** Attachment added: "core."
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+attachment/4214812/+files/core.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1358918
Title:
ubuntu-location-serviced cpu usage spikes to 100% occasionally
Status in “dbus-cpp” package in Ubuntu:
Confirmed
Status in “location-service” package in Ubuntu:
Confirmed
Bug description:
Occasionally, users report the location service daemon CPU usage to
spike and occupy an entire core of the system. Up until now, we have
no way of reliably reproducing the issue. If you encounter it, please
do the following:
* Report the output of /system/bin/logcat on this bug
* If possible, attach to the location service daemon process with:
* sudo gdb -p ${PID_OF_LOCATION_SERVICE_DAEMON}
* Call generate-core-file inside gdb
* Attach the resuling core.${PID_OF_LOCATION_SERVICE_DAEMON} to this
bug report
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1358918] Re: ubuntu-location-serviced cpu usage spikes to 100% occasionally
Copying this backtrace from duplicate bug:
http://paste.ubuntu.com/8425087/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1358918
Title:
ubuntu-location-serviced cpu usage spikes to 100% occasionally
Status in “dbus-cpp” package in Ubuntu:
Confirmed
Status in “location-service” package in Ubuntu:
Confirmed
Bug description:
Occasionally, users report the location service daemon CPU usage to
spike and occupy an entire core of the system. Up until now, we have
no way of reliably reproducing the issue. If you encounter it, please
do the following:
* Report the output of /system/bin/logcat on this bug
* If possible, attach to the location service daemon process with:
* sudo gdb -p ${PID_OF_LOCATION_SERVICE_DAEMON}
* Call generate-core-file inside gdb
* Attach the resuling core.${PID_OF_LOCATION_SERVICE_DAEMON} to this
bug report
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334722] Re: Add an accounts click hook
** Changed in: signon (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1334722
Title:
Add an accounts click hook
Status in “signon” package in Ubuntu:
Invalid
Bug description:
Click packages need to be able to add new account types just as debian
packages can. I would suggest a click manifest definition similar to
below.
manifest.json:
{
"description": "My Description",
"framework": "ubuntu-sdk-14.10-dev2",
"architecture": "all",
"hooks": {
"my-application": {
"accounts": "my-accounts" <-- this refers to the name of a dir in
your click package
}
},
"icon": "icon",
"maintainer": "Ubuntu Developers ",
"name": "com.package.name",
"title": "A click package providing account types",
"version": "1.0.0"
}
And then in your click package provide the directory "my-accounts", following
the same structure as in /usr/share/accounts:
my-accounts:
├── applications
│ └── something.application
├── providers
│ └── something.provider
├── qml-plugins
│ ├── something
│ └ Main.qml
├── services
│ └── yahoo-mail.service
└── service_types
└── ubuntuone.service-type
Your actual click hook file could be something like this:
Pattern: ${home}/.local/share/accounts/${id}
User-Level: yes
Hook-Name: accounts
You'd obviously need to monitor "~/.local/share/accounts/". In there
the click machinery will create symlinks to the directories specified
above.
Any click packaging would satisfy the requirements really, but I think
what I have specified above is pretty simple to both use and
implement.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1334722/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334722] Re: Add an accounts click hook
As far as I'm aware, the use case is for vendor/OEM provided scopes - so
they can add their own account types.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1334722
Title:
Add an accounts click hook
Status in “signon” package in Ubuntu:
New
Bug description:
Click packages need to be able to add new account types just as debian
packages can. I would suggest a click manifest definition similar to
below.
manifest.json:
{
"description": "My Description",
"framework": "ubuntu-sdk-14.10-dev2",
"architecture": "all",
"hooks": {
"my-application": {
"accounts": "my-accounts" <-- this refers to the name of a dir in
your click package
}
},
"icon": "icon",
"maintainer": "Ubuntu Developers ",
"name": "com.package.name",
"title": "A click package providing account types",
"version": "1.0.0"
}
And then in your click package provide the directory "my-accounts", following
the same structure as in /usr/share/accounts:
my-accounts:
├── applications
│ └── something.application
├── providers
│ └── something.provider
├── qml-plugins
│ ├── something
│ └ Main.qml
├── services
│ └── yahoo-mail.service
└── service_types
└── ubuntuone.service-type
Your actual click hook file could be something like this:
Pattern: ${home}/.local/share/accounts/${id}
User-Level: yes
Hook-Name: accounts
You'd obviously need to monitor "~/.local/share/accounts/". In there
the click machinery will create symlinks to the directories specified
above.
Any click packaging would satisfy the requirements really, but I think
what I have specified above is pretty simple to both use and
implement.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1334722/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334722] [NEW] Add an accounts click hook
Public bug reported:
Click packages need to be able to add new account types just as debian
packages can. I would suggest a click manifest definition similar to
below.
manifest.json:
{
"description": "My Description",
"framework": "ubuntu-sdk-14.10-dev2",
"architecture": "all",
"hooks": {
"my-application": {
"accounts": "my-accounts" <-- this refers to the name of a dir in
your click package
}
},
"icon": "icon",
"maintainer": "Ubuntu Developers ",
"name": "com.package.name",
"title": "A click package providing account types",
"version": "1.0.0"
}
And then in your click package provide the directory "my-accounts", following
the same structure as in /usr/share/accounts:
my-accounts:
├── applications
│ └── something.application
├── providers
│ └── something.provider
├── qml-plugins
│ ├── something
│ └ Main.qml
├── services
│ └── yahoo-mail.service
└── service_types
└── ubuntuone.service-type
Your actual click hook file could be something like this:
Pattern: ${home}/.local/share/accounts/${id}
User-Level: yes
Hook-Name: accounts
You'd obviously need to monitor "~/.local/share/accounts/". In there the
click machinery will create symlinks to the directories specified above.
Any click packaging would satisfy the requirements really, but I think
what I have specified above is pretty simple to both use and implement.
** Affects: signon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1334722
Title:
Add an accounts click hook
Status in “signon” package in Ubuntu:
New
Bug description:
Click packages need to be able to add new account types just as debian
packages can. I would suggest a click manifest definition similar to
below.
manifest.json:
{
"description": "My Description",
"framework": "ubuntu-sdk-14.10-dev2",
"architecture": "all",
"hooks": {
"my-application": {
"accounts": "my-accounts" <-- this refers to the name of a dir in
your click package
}
},
"icon": "icon",
"maintainer": "Ubuntu Developers ",
"name": "com.package.name",
"title": "A click package providing account types",
"version": "1.0.0"
}
And then in your click package provide the directory "my-accounts", following
the same structure as in /usr/share/accounts:
my-accounts:
├── applications
│ └── something.application
├── providers
│ └── something.provider
├── qml-plugins
│ ├── something
│ └ Main.qml
├── services
│ └── yahoo-mail.service
└── service_types
└── ubuntuone.service-type
Your actual click hook file could be something like this:
Pattern: ${home}/.local/share/accounts/${id}
User-Level: yes
Hook-Name: accounts
You'd obviously need to monitor "~/.local/share/accounts/". In there
the click machinery will create symlinks to the directories specified
above.
Any click packaging would satisfy the requirements really, but I think
what I have specified above is pretty simple to both use and
implement.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1334722/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310330] Re: Request "More Colors..." option in Font Color/Background Color
Thanks for your reply! I've reported it here: https://bugs.freedesktop.org/show_bug.cgi?id=77695 Hope this is correct. ** Bug watch added: freedesktop.org Bugzilla #77695 https://bugs.freedesktop.org/show_bug.cgi?id=77695 -- 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/1310330 Title: Request "More Colors..." option in Font Color/Background Color Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: In any other word processor out there, it's much easier to change text or background colors. They don't have to be predefined first. Please add a "More Colors..." entry to the "Font Color" and "Background Color" buttons in LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-writer 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: Unity Date: Sun Apr 20 17:30:05 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1310330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310330] [NEW] Selecting colors is too complicated
Public bug reported: In any other word processor out there, it's much easier to change text or background colors. They don't have to be predefined first. Please add a "More Colors..." entry to the "Font Color" and "Background Color" buttons in LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-writer 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: Unity Date: Sun Apr 20 17:30:05 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1310330 Title: Selecting colors is too complicated Status in “libreoffice” package in Ubuntu: New Bug description: In any other word processor out there, it's much easier to change text or background colors. They don't have to be predefined first. Please add a "More Colors..." entry to the "Font Color" and "Background Color" buttons in LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-writer 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: Unity Date: Sun Apr 20 17:30:05 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1310330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1045353] Re: LibreOffice commands are not displayed in the HUD
** Changed in: hud (Ubuntu) Status: Confirmed => Invalid -- 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/1045353 Title: LibreOffice commands are not displayed in the HUD Status in “hud” package in Ubuntu: Invalid Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Ubuntu Release: Ubuntu 12.10 Quantal Quetzal beta1 Package version: libreoffice-gtk Package version: 1:3.6.1~rc2-1ubuntu3 Expected behavior: It should be possible to launch LO actions from the HUD. Actual behavior: Libreoffice commands are not shown in the HUD. According to comments, this is the case for: - Ubuntu 12.10 and 13.04 - LibreOffice cycles 3.6 and 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1045353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288025] Re: HUD entries don't get activated with gmenumodel
Another good test case that Ted has noticed is LibreOffice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel Status in Unity HUD: Confirmed Status in “evince” package in Ubuntu: Invalid Bug description: 1. Open evince 2. tap to get the HUD 3. type menu item name (eg open). Note that all the evince menu items seem to be available in the HUD 4. press enter 5. nothing happens ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 13:28:59 2014 InstallationDate: Installed on 2013-06-22 (255 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2013-12-05 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 487695] Re: autoduplex constraints should be dropped
I have now installed HPLIP 3.14.3. This has solved most of my problems (see bug https://bugs.launchpad.net/bugs/1276801), and my printer now behaves as described in this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/487695 Title: autoduplex constraints should be dropped Status in Common Print Dialog: New Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Invalid Status in “hplip” source package in Maverick: Fix Released Status in “system-config-printer” source package in Maverick: Fix Released Status in “hplip” source package in Natty: Fix Released Status in “system-config-printer” source package in Natty: Invalid Bug description: The "autoduplex" page sizes are a clever way of allowing the application to know in advance exactly where the page margins are when duplexing. However, it should not be an actual constraint on whether duplexing can be enabled. The reason is that it can never be clear to the user why they cannot select a duplexing option. Their page size setting is correct (e.g. A4), and the installable options setting says that a duplexer is installed. There is no way to discover the "magic" page sizes. Also there is no way for CUPS to know to set this magic page size as the default when adding a queue. It will look for "A4" or "Letter" depending on the locale. To manage notifications about this bug go to: https://bugs.launchpad.net/common-print-dialog-gtk/+bug/487695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288025] Re: HUD entries don't get activated with gmenumodel
** Branch linked: lp:~unity-api-team/hud/lp-1288025 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel Status in Unity HUD: Confirmed Status in “evince” package in Ubuntu: Invalid Bug description: 1. Open evince 2. tap to get the HUD 3. type menu item name (eg open). Note that all the evince menu items seem to be available in the HUD 4. press enter 5. nothing happens ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 13:28:59 2014 InstallationDate: Installed on 2013-06-22 (255 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2013-12-05 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288025] Re: HUD entries don't get activated with gmenumodel
** Also affects: hud Importance: Undecided Status: New ** Changed in: hud Status: New => Confirmed ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid ** Changed in: hud Importance: Undecided => High ** Changed in: hud Assignee: (unassigned) => Pete Woods (pete-woods) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel Status in Unity HUD: Confirmed Status in “evince” package in Ubuntu: Invalid Bug description: 1. Open evince 2. tap to get the HUD 3. type menu item name (eg open). Note that all the evince menu items seem to be available in the HUD 4. press enter 5. nothing happens ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 13:28:59 2014 InstallationDate: Installed on 2013-06-22 (255 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2013-12-05 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278511] Re: CTRL-Space no longer works under Unity
seb128: > that seems an issue with ibus, does it work if you run ibus-setup and change > the keybinding there? Yes, that works around the issue for the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1278511 Title: CTRL-Space no longer works under Unity Status in “ibus” package in Ubuntu: In Progress Bug description: No changes were done at all to any hot keys or settings. It was working last night before the latest update from 14.04. I am guessing Unity is somehow intercepting CTRL-space somewhere. I checked all the hot keys and nothing. Please fix. This is critical for all Emacs users. BTW, CTRL-Space works just fine using GNOME shell on the same OS install. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: GNOME Date: Mon Feb 10 11:58:48 2014 InstallationDate: Installed on 2013-12-17 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131217) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1278511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 487695] Re: autoduplex constraints should be dropped
I have problems with lost margins printing to a new OfficeJet 6700 using HPLIP version 3.14.1. Printing the test page on A4 paper during installation of 3.14.1 gave correct results. After installation, I changed the paper size from letter back to A4 and printed a test page. The ruler at the bottom is missing (see bug 1276801 for details and a scanned pdf of the output). There seem to be multiple reports of similar issues. Should these be collected somewhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/487695 Title: autoduplex constraints should be dropped Status in Common Print Dialog: New Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Invalid Status in “hplip” source package in Maverick: Fix Released Status in “system-config-printer” source package in Maverick: Fix Released Status in “hplip” source package in Natty: Fix Released Status in “system-config-printer” source package in Natty: Invalid Bug description: The "autoduplex" page sizes are a clever way of allowing the application to know in advance exactly where the page margins are when duplexing. However, it should not be an actual constraint on whether duplexing can be enabled. The reason is that it can never be clear to the user why they cannot select a duplexing option. Their page size setting is correct (e.g. A4), and the installable options setting says that a duplexer is installed. There is no way to discover the "magic" page sizes. Also there is no way for CUPS to know to set this magic page size as the default when adding a queue. It will look for "A4" or "Letter" depending on the locale. To manage notifications about this bug go to: https://bugs.launchpad.net/common-print-dialog-gtk/+bug/487695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278192] Re: cant load video driver
here is the output for lshw -c video *-display description: VGA compatible controller product: 82G33/G31 Express Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 32 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:42 memory:fdf0-fdf7 ioport:ff00(size=8) memory:d000-dfff memory:fdb0-fdbf -- 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/1278192 Title: cant load video driver Status in “xorg” package in Ubuntu: New Bug description: 1 updated to 13.10 and removed graphic card after problems developing . 2 i used the intel graphics installer for linux to load drivers and expected them to load . 3 run system test and expected to see the driver working ..instead i get this message "graphics/driver_versionFAILED ERROR: No video driver loaded! Possibly in failsafe mode! " also checked in software updater and no drivers listed to choose from . yes i rebooted the machine . ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 22:23:46 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (228 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402091930.61bc01~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402091930.61bc01~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 22:05:54 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278192] Re: cant load video driver
righto fixed that issue ..now back to this error ... graphics/driver_version FAILED ERROR: No video driver loaded! Possibly in failsafe mode! i just cant figure out why i cant use the intel driver ? -- 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/1278192 Title: cant load video driver Status in “xorg” package in Ubuntu: New Bug description: 1 updated to 13.10 and removed graphic card after problems developing . 2 i used the intel graphics installer for linux to load drivers and expected them to load . 3 run system test and expected to see the driver working ..instead i get this message "graphics/driver_versionFAILED ERROR: No video driver loaded! Possibly in failsafe mode! " also checked in software updater and no drivers listed to choose from . yes i rebooted the machine . ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 22:23:46 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (228 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402091930.61bc01~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402091930.61bc01~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 22:05:54 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278192] Re: cant load video driver
ok now i am getting this in system testing .. graphics/compiz_check FAILED OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits) OpenGL version string: 2.1 Mesa 10.2.0-devel (git-61bc014 saucy-oibaf- ppa) Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no and this ... graphics/VESA_drivers_not_in_useFAILED can anyone please help to fix this with me ? -- 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/1278192 Title: cant load video driver Status in “xorg” package in Ubuntu: New Bug description: 1 updated to 13.10 and removed graphic card after problems developing . 2 i used the intel graphics installer for linux to load drivers and expected them to load . 3 run system test and expected to see the driver working ..instead i get this message "graphics/driver_versionFAILED ERROR: No video driver loaded! Possibly in failsafe mode! " also checked in software updater and no drivers listed to choose from . yes i rebooted the machine . ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 22:23:46 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (228 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402091930.61bc01~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402091930.61bc01~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 22:05:54 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278192] [NEW] cant load video driver
Public bug reported: 1 updated to 13.10 and removed graphic card after problems developing . 2 i used the intel graphics installer for linux to load drivers and expected them to load . 3 run system test and expected to see the driver working ..instead i get this message "graphics/driver_version FAILED ERROR: No video driver loaded! Possibly in failsafe mode! " also checked in software updater and no drivers listed to choose from . yes i rebooted the machine . ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 22:23:46 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (228 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402091930.61bc01~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402091930.61bc01~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 22:05:54 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 saucy third-party-packages 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/1278192 Title: cant load video driver Status in “xorg” package in Ubuntu: New Bug description: 1 updated to 13.10 and removed graphic card after problems developing . 2 i used the intel graphics installer for linux to load drivers and expected them to load . 3 run system test and expected to see the driver working ..instead i get this message "graphics/driver_versionFAILED ERROR: No video driver loaded! Possibly in failsafe mode! " also checked in software updater and no drivers listed to choose from . yes i rebooted the machine . ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 22:23:46 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu E
[Desktop-packages] [Bug 1278160] Re: video driver
dpkg: warning: while removing nvidia-173, directory '/usr/lib/nvidia-173/tls' not empty so not removed so i run ...apt-get autoremove what next ? -- 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/1278160 Title: video driver Status in “xorg” package in Ubuntu: Incomplete Bug description: i cant seem to get a video driver to load ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 19:41:40 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-13-generic, i686: installed nvidia-304, 304.88, 3.11.0-14-generic, i686: installed nvidia-304, 304.88, 3.11.0-15-generic, i686: installed nvidia-304, 304.88, 3.11.0-17-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (227 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402090730.356aff~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402090730.356aff~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 19:33:09 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278160] Re: video driver
could you please explain how ? i know some commands but not that one .. cheers pete -- 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/1278160 Title: video driver Status in “xorg” package in Ubuntu: Incomplete Bug description: i cant seem to get a video driver to load ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 19:41:40 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-13-generic, i686: installed nvidia-304, 304.88, 3.11.0-14-generic, i686: installed nvidia-304, 304.88, 3.11.0-15-generic, i686: installed nvidia-304, 304.88, 3.11.0-17-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (227 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402090730.356aff~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402090730.356aff~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 19:33:09 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278160] Re: video driver
1 updated to 13.10 and removed graphic card after problems developing . 2 i used the intel graphics installer for linux to load drivers and expected them to load . 3 run system test and expected to see the driver working ..instead i get this message "graphics/driver_version FAILED ERROR: No video driver loaded! Possibly in failsafe mode! " also checked in software updater and no drivers listed to choose from . yes i rebooted the machine . -- 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/1278160 Title: video driver Status in “xorg” package in Ubuntu: Incomplete Bug description: i cant seem to get a video driver to load ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 19:41:40 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-13-generic, i686: installed nvidia-304, 304.88, 3.11.0-14-generic, i686: installed nvidia-304, 304.88, 3.11.0-15-generic, i686: installed nvidia-304, 304.88, 3.11.0-17-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (227 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402090730.356aff~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402090730.356aff~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 19:33:09 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278160] [NEW] video driver
Public bug reported: i cant seem to get a video driver to load ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 19:41:40 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-13-generic, i686: installed nvidia-304, 304.88, 3.11.0-14-generic, i686: installed nvidia-304, 304.88, 3.11.0-15-generic, i686: installed nvidia-304, 304.88, 3.11.0-17-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (227 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-31 (101 days ago) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52+git1401311830.128e74~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402090730.356aff~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402090730.356aff~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3+git1401241930.8de6f7~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909+git1402061930.823382~gd~s version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Sun Feb 9 19:33:09 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 8 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22114 vendor GSM xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 saucy third-party-packages 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/1278160 Title: video driver Status in “xorg” package in Ubuntu: New Bug description: i cant seem to get a video driver to load ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Sun Feb 9 19:41:40 2014 DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-13-generic, i686: installed nvidia-304, 304.88, 3.11.0-14-generic, i686: installed nvidia-304, 304.88, 3.11.0-15-generic, i686: installed nvidia-304, 304.88, 3.11.0-17-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0238] InstallationDate: Installed on 2013-06-26 (227 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release
