[Desktop-packages] [Bug 1696320] [NEW] "Unknown audio device" dialog pops up every time
Public bug reported: As per http://voices.canonical.com/david.henningsson/2014/03/07/headset- jacks-on-newer-laptops/ I am opening a new bug for different hardware, but the problem is the same as https://bugs.launchpad.net/ubuntu/+source /unity-settings-daemon/+bug/1297790 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: thomas 2519 F...m pulseaudio /dev/snd/controlC1: thomas 2519 F pulseaudio /dev/snd/controlC0: thomas 2519 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Wed Jun 7 08:48:00 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-25 (407 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to zesty on 2017-04-14 (53 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0D8H72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1696320 Title: "Unknown audio device" dialog pops up every time Status in alsa-driver package in Ubuntu: New Bug description: As per http://voices.canonical.com/david.henningsson/2014/03/07 /headset-jacks-on-newer-laptops/ I am opening a new bug for different hardware, but the problem is the same as https://bugs.launchpad.net/ubuntu/+source/unity-settings- daemon/+bug/1297790 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: thomas 2519 F...m pulseaudio /dev/snd/controlC1: thomas 2519 F pulseaudio /dev/snd/controlC0: thomas 2519 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Wed Jun 7 08:48:00 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-25 (407 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to zesty on 2017-04-14 (53 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0D8H72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695983] Re: Removing an imported openvpn connection doesn't clean up copied certificates
Hi, I want to know why you filed this against xorg? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1695983 Title: Removing an imported openvpn connection doesn't clean up copied certificates Status in xorg package in Ubuntu: Incomplete Bug description: I imported an openvpn connection with the KDE network manager, which worked fine. On import I was asked whether I want my certificates to be copied to .local/share/networkmanagement, which I confirmed. Them I removed my connection and reimported it again, this time receiving the following error message: "Error copying certificate to /home/user/.local/share/networkmanagement/certificates/myopenvpn.key: Destination file exists" Seems like copied certificates aren't cleaned up when an openvpn connection is removed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 5 21:56:31 2017 InstallationDate: Installed on 2017-06-04 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695983] Re: Removing an imported openvpn connection doesn't clean up copied certificates
and/or how -- 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/1695983 Title: Removing an imported openvpn connection doesn't clean up copied certificates Status in xorg package in Ubuntu: Incomplete Bug description: I imported an openvpn connection with the KDE network manager, which worked fine. On import I was asked whether I want my certificates to be copied to .local/share/networkmanagement, which I confirmed. Them I removed my connection and reimported it again, this time receiving the following error message: "Error copying certificate to /home/user/.local/share/networkmanagement/certificates/myopenvpn.key: Destination file exists" Seems like copied certificates aren't cleaned up when an openvpn connection is removed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 5 21:56:31 2017 InstallationDate: Installed on 2017-06-04 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1608018] Re: log flooded with gnome-session not authorized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1608018 Title: log flooded with gnome-session not authorized Status in gnome-session package in Ubuntu: Confirmed Bug description: Syslog on my system is flooded with authorization warnings every second: Jul 30 09:17:17 svenBlack gnome-session[3093]: Error executing command as another user: Not authorized Jul 30 09:17:17 svenBlack gnome-session[3093]: This incident has been reported. No further information is given on what command resulted in an error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-session 3.18.1.2-1ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jul 30 09:17:19 2016 InstallationDate: Installed on 2015-04-27 (459 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to xenial on 2016-04-16 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1608018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
the debdiff of libmbim for review ** Patch added: "libmbim_1.12.2-2ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1693756/+attachment/4890873/+files/libmbim_1.12.2-2ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
debdiff of libqmi for review ** Patch added: "libqmi_1.12.6-1ubuntu1.dsc.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1693756/+attachment/4890874/+files/libqmi_1.12.6-1ubuntu1.dsc.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
debdiff of modemmanager for review ** Patch added: "modemmanager_1.4.12-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1693756/+attachment/4890875/+files/modemmanager_1.4.12-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 175316] Re: no IDN in nslookup and host
I also vote for this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/175316 Title: no IDN in nslookup and host Status in BIND: New Status in bind9 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Confirmed Status in bind9 package in Debian: New Bug description: Binary package hint: bind9 Neither nslookup or host supports IDN. If you try , for example, to get the IP for "registrera-domän.se" it fails every time. As the use of IDN is increasing I think it would be a good thing if these tools supported this. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/175316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 753520] Re: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()
Still an issue in zesty, can the package not be updated? Comment #26 is a good work around. ** Tags added: zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/753520 Title: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules() Status in freerdp: New Status in remmina: New Status in remmina package in Ubuntu: Triaged Bug description: Binary package hint: remmina 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy remmina remmina: Installed: 1.1.1-1ubuntu1 Candidate: 1.1.1-1ubuntu1 Version table: *** 1.1.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one has their default keyboard setting set to en_US > System Settings... > Text Entry > change to Input sources to use: Maori > close window > secondary click the Text Input tray icon and change from English to Maori > restart > open Remmina and it works. 4) What happens instead is it crashes consistently: remmina Remmina plugin VNC (type=Protocol) registered. Remmina plugin VNCI (type=Protocol) registered. Remmina plugin RDP (type=Protocol) registered. Remmina plugin RDPF (type=File) registered. Remmina plugin RDPS (type=Preference) registered. Segmentation fault First reported against Ubuntu 11.04, remmina 0.9.3-2 WORKAROUND: Use en_US. WORKAROUND: Remove remmina-plugin-rdp. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: remmina 0.9.3-2 ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CrashCounter: 1 Date: Thu Apr 7 15:17:34 2011 ExecutablePath: /usr/bin/remmina InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) ProcCmdline: remmina ProcEnviron: LANGUAGE=en_ZA:en LANG=en_ZA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc61738202b : mov(%r12),%rdi PC (0x7fc61738202b) ok source "(%r12)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: remmina StacktraceTop: find_keyboard_layout_in_xorg_rules () from /usr/lib/libfreerdpkbd.so.0 detect_keyboard_layout_from_xkb () from /usr/lib/libfreerdpkbd.so.0 detect_and_load_keyboard () from /usr/lib/libfreerdpkbd.so.0 freerdp_kbd_init () from /usr/lib/libfreerdpkbd.so.0 remmina_plugin_rdpset_init () from /usr/lib/remmina/plugins/remmina-plugin-rdp.so Title: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/freerdp/+bug/753520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696388] [NEW] xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window
Public bug reported: I initially spotted the issue when opening a downloaded source tarball from chromium-browser, which uses xdg-open under the covers to open downloaded files. Steps to reproduce: 1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz 2) xdg-open linux-4.11.3.tar.xz Expected result: the tarball is mounted in nautilus and a nautilus window is open to display the contents of the tarball Actual result: the tarball is mounted in nautilus, but no window is shown, thus leaving the user thinking that nothing happened ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: file-roller 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 12:22:47 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (339 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: file-roller UpgradeStatus: Upgraded to artful on 2017-06-04 (2 days ago) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1696388 Title: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window Status in file-roller package in Ubuntu: New Bug description: I initially spotted the issue when opening a downloaded source tarball from chromium-browser, which uses xdg-open under the covers to open downloaded files. Steps to reproduce: 1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz 2) xdg-open linux-4.11.3.tar.xz Expected result: the tarball is mounted in nautilus and a nautilus window is open to display the contents of the tarball Actual result: the tarball is mounted in nautilus, but no window is shown, thus leaving the user thinking that nothing happened ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: file-roller 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 12:22:47 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (339 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: file-roller UpgradeStatus: Upgraded to artful on 2017-06-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1696388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696388] Re: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window
When I run xdg-open, here are the processes that get spawned: /bin/sh /usr/bin/xdg-open linux-3.2.89.tar.xz /usr/bin/perl /usr/bin/run-mailcap --action=view linux-3.2.89.tar.xz /usr/lib/gvfs/gvfsd-archive file=/tmp/filenaxeY1.2.89.tar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1696388 Title: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window Status in file-roller package in Ubuntu: New Bug description: I initially spotted the issue when opening a downloaded source tarball from chromium-browser, which uses xdg-open under the covers to open downloaded files. Steps to reproduce: 1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz 2) xdg-open linux-4.11.3.tar.xz Expected result: the tarball is mounted in nautilus and a nautilus window is open to display the contents of the tarball Actual result: the tarball is mounted in nautilus, but no window is shown, thus leaving the user thinking that nothing happened ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: file-roller 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 12:22:47 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (339 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: file-roller UpgradeStatus: Upgraded to artful on 2017-06-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1696388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696395] [NEW] gnome-control-center crashed with SIGSEGV in um_carousel_select_item()
Public bug reported: Test Case 1. In a live session, open system settings 2. Click on 'Users' Expected result The 'users' panel opens (even if I think the 'users' panel should not be there at all) Actual result This crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 10:37:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1372 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55c78b9944f8 :mov 0x48(%rsi),%eax PC (0x55c78b9944f8) ok source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: um_carousel_select_item () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace ** Information type changed from Private to Public Security ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696395 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() Status in gnome-control-center package in Ubuntu: New Bug description: Test Case 1. In a live session, open system settings 2. Click on 'Users' Expected result The 'users' panel opens (even if I think the 'users' panel should not be there at all) Actual result This crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 10:37:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1372 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55c78b9944f8 : mov 0x48(%rsi),%eax PC (0x55c78b9944f8) ok source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: um_carousel_select_item () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() 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/gnome-control-center/+bug/1696395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696388] Re: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window
$ run-mailcap --action=view --debug linux-3.2.89.tar.xz - parsing parameter "linux-3.2.89.tar.xz" - file "linux-3.2.89.tar.xz" has encoding "xz" - Reading mime.types file "/home/osomon/.mime.types"... could not read "/home/osomon/.mime.types" -- No such file or directory - Reading mime.types file "/usr/local/etc/mime.types"... could not read "/usr/local/etc/mime.types" -- No such file or directory - Reading mime.types file "/usr/share/etc/mime.types"... could not read "/usr/share/etc/mime.types" -- No such file or directory - Reading mime.types file "/etc/mime.types"... - extension "tar" maps to mime-type "application/x-tar" - Reading mailcap file "/home/osomon/.mailcap"... could not read "/home/osomon/.mailcap" -- No such file or directory - Reading mailcap file "/etc/mailcap"... - Reading mailcap file "/usr/local/etc/mailcap"... could not read "/usr/local/etc/mailcap" -- No such file or directory - Reading mailcap file "/usr/share/etc/mailcap"... could not read "/usr/share/etc/mailcap" -- No such file or directory - Reading mailcap file "/usr/etc/mailcap"... could not read "/usr/etc/mailcap" -- No such file or directory Processing file "linux-3.2.89.tar.xz" of type "application/x-tar" (encoding=xz)... - decoding "linux-3.2.89.tar.xz" as "/tmp/fileIegizX.2.89.tar" - checking mailcap entry "application/x-tar; /usr/lib/gvfs/gvfsd-archive file=%s; test=test -n "$DISPLAY"" - program to execute: /usr/lib/gvfs/gvfsd-archive file=%s - running test: test -n "$DISPLAY" (result=0=true) - executing: /usr/lib/gvfs/gvfsd-archive file=/tmp/fileIegizX.2.89.tar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1696388 Title: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window Status in file-roller package in Ubuntu: New Bug description: I initially spotted the issue when opening a downloaded source tarball from chromium-browser, which uses xdg-open under the covers to open downloaded files. Steps to reproduce: 1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz 2) xdg-open linux-4.11.3.tar.xz Expected result: the tarball is mounted in nautilus and a nautilus window is open to display the contents of the tarball Actual result: the tarball is mounted in nautilus, but no window is shown, thus leaving the user thinking that nothing happened ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: file-roller 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 12:22:47 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (339 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: file-roller UpgradeStatus: Upgraded to artful on 2017-06-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1696388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696395]
StacktraceTop: um_carousel_select_item (self=0x55c78de65520, item=0x0) at um-carousel.c:212 reload_users (d=0x55c78d8fc440, selected_user=0x55c78dbfaec0) at um-user-panel.c:299 g_closure_invoke (closure=0x55c78e06b900, return_value=return_value@entry=0x0, n_param_values=2, param_values=param_values@entry=0x7ffdbce75730, invocation_hint=invocation_hint@entry=0x7ffdbce756b0) at ../../../../gobject/gclosure.c:804 signal_emit_unlocked_R (node=node@entry=0x55c78e0204e0, detail=detail@entry=0, instance=instance@entry=0x55c78dbfadb0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdbce75730) at ../../../../gobject/gsignal.c:3635 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7ffdbce758f0) at ../../../../gobject/gsignal.c:3391 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696395 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() Status in gnome-control-center package in Ubuntu: New Bug description: Test Case 1. In a live session, open system settings 2. Click on 'Users' Expected result The 'users' panel opens (even if I think the 'users' panel should not be there at all) Actual result This crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 10:37:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1372 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55c78b9944f8 : mov 0x48(%rsi),%eax PC (0x55c78b9944f8) ok source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: um_carousel_select_item () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() 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/gnome-control-center/+bug/1696395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696395] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1696395/+attachment/4891031/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696395 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() Status in gnome-control-center package in Ubuntu: New Bug description: Test Case 1. In a live session, open system settings 2. Click on 'Users' Expected result The 'users' panel opens (even if I think the 'users' panel should not be there at all) Actual result This crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 10:37:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1372 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55c78b9944f8 : mov 0x48(%rsi),%eax PC (0x55c78b9944f8) ok source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: um_carousel_select_item () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() 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/gnome-control-center/+bug/1696395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696395] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1696395/+attachment/4891032/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696395 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() Status in gnome-control-center package in Ubuntu: New Bug description: Test Case 1. In a live session, open system settings 2. Click on 'Users' Expected result The 'users' panel opens (even if I think the 'users' panel should not be there at all) Actual result This crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 10:37:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1372 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55c78b9944f8 : mov 0x48(%rsi),%eax PC (0x55c78b9944f8) ok source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: um_carousel_select_item () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() 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/gnome-control-center/+bug/1696395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696395] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1696395/+attachment/4891033/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1696395/+attachment/4891021/+files/CoreDump.gz ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696395 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() Status in gnome-control-center package in Ubuntu: New Bug description: Test Case 1. In a live session, open system settings 2. Click on 'Users' Expected result The 'users' panel opens (even if I think the 'users' panel should not be there at all) Actual result This crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 10:37:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1372 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55c78b9944f8 : mov 0x48(%rsi),%eax PC (0x55c78b9944f8) ok source "0x48(%rsi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: um_carousel_select_item () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item() 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/gnome-control-center/+bug/1696395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696388] Re: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window
In a zesty VM, xdg-open runs file-roller, whereas in artful it runs `run-mailcap --action=view`. xdg-open itself hasn't changed recently though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1696388 Title: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window Status in file-roller package in Ubuntu: New Bug description: I initially spotted the issue when opening a downloaded source tarball from chromium-browser, which uses xdg-open under the covers to open downloaded files. Steps to reproduce: 1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz 2) xdg-open linux-4.11.3.tar.xz Expected result: the tarball is mounted in nautilus and a nautilus window is open to display the contents of the tarball Actual result: the tarball is mounted in nautilus, but no window is shown, thus leaving the user thinking that nothing happened ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: file-roller 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 12:22:47 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (339 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: file-roller UpgradeStatus: Upgraded to artful on 2017-06-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1696388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696388] Re: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window
`xdg-mime query filetype linux-3.2.89.tar.xz` returns nothing on artful, whereas it returns "application/x-xz-compressed-tar" on zesty, which explains why xdg-open takes a different code path. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1696388 Title: xdg-open filename.tar.xz mounts tarball in nautilus but doesn't open a nautilus window Status in file-roller package in Ubuntu: New Bug description: I initially spotted the issue when opening a downloaded source tarball from chromium-browser, which uses xdg-open under the covers to open downloaded files. Steps to reproduce: 1) wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.3.tar.xz 2) xdg-open linux-4.11.3.tar.xz Expected result: the tarball is mounted in nautilus and a nautilus window is open to display the contents of the tarball Actual result: the tarball is mounted in nautilus, but no window is shown, thus leaving the user thinking that nothing happened ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: file-roller 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 7 12:22:47 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (339 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: file-roller UpgradeStatus: Upgraded to artful on 2017-06-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1696388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696300] Re: Update to 5.3.3
Thanks Olivier, the update looks good and I'm going to sponsor it ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu) Status: New => In Progress ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1696300 Title: Update to 5.3.3 Status in libreoffice package in Ubuntu: In Progress Bug description: The latest fresh version of libreoffice is 5.3.3, released on 2017-05-11. I have updated the packages (for libreoffice and libreoffice-l10n) from 5.3.1. Packaging changes are committed to https://code.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/+git/libreoffice-debian-pkg/+ref/ubuntu-artful-5.3. Corresponding packages are built in https://launchpad.net/~osomon/+archive/ubuntu/lo-builds/+packages. I am attaching debdiffs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1696300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693632] Re: cups-browsed crashed with SIGSEGV in resolve_callback()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1693632 Title: cups-browsed crashed with SIGSEGV in resolve_callback() Status in cups-filters package in Ubuntu: Confirmed Bug description: 05/25/2017 Upgrade from 17.04 Desktop Fresh Install using "update- manger -d" ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-browsed 1.14.0-1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CupsErrorLog: E [25/May/2017:16:10:14 -0400] [Client 5] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP-Officejet-Pro-8610) from localhost E [25/May/2017:16:10:16 -0400] [Client 5] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP-Officejet-Pro-8610) from localhost E [25/May/2017:18:03:36 -0400] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/hp-officejet-pro-8610) from localhost Date: Thu May 25 16:10:21 2017 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lpstat: device for HP-Officejet-Pro-8610: ipp://HP6CC217115CD8.local:631/ipp/print MachineType: Gateway GT5628 Papersize: letter PpdFiles: HP-Officejet-Pro-8610: HP Officejet Pro 8610, driverless, cups-filters 1.14.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x560323ea9339:mov(%r15),%edx PC (0x560323ea9339) ok source "(%r15)" (0x) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () avahi_service_resolver_event () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 Title: cups-browsed crashed with SIGSEGV in avahi_service_resolver_event() UpgradeStatus: Upgraded to artful on 2017-05-25 (0 days ago) UserGroups: dmi.bios.date: 05/22/2008 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.15A.0316.2008.0522.1909 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG33SXG2 dmi.board.vendor: Intel Corporation dmi.board.version: AAD94468-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.15A.0316.2008.0522.1909:bd05/22/2008:svnGateway:pnGT5628:pvr:rvnIntelCorporation:rnDG33SXG2:rvrAAD94468-403:cvn:ct3:cvr: dmi.product.name: GT5628 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1693632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
The problem is only reproducible with some Kernel versions, how can it not be related to the Kernel? I actually have a Sky Lake, not a Haswell like the reporter. So maybe one of those commits for Baytrail caused a regression on other Intel Graphics processors? Another culprit seems to be Dell laptops... I'm on a Dell Latitude E7470, other people mentioned them too, although it might just be because it's a common brand. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696312] Re: No puedo ejecutar java.
This user would like to know how to run Java in Firefox. ** Changed in: firefox (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/firefox/+question/642020 -- 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/1696312 Title: No puedo ejecutar java. Status in firefox package in Ubuntu: Invalid Bug description: Buenos días, me gustaría saber como puedo ejecutar java en Mozilla Firefox V.53 se que ya no dan soporte para Java pero si no puedo ejecutar java me veo obligado a cambiar de navegador, pues necesito ejecutarlo porque visito web que lo requieren. Hay alguna solución? Gracias por vuestra atención. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: firefox 53.0.3+build1-0ubuntu0.16.10.2 ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcosqd 2059 F pulseaudio BuildID: 20170524174609 Channel: Unavailable CurrentDesktop: Unity Date: Wed Jun 7 07:20:27 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-04-14 (53 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.73 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=53.0.3/20170524174609 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Tangiz dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa7620:pvr0100:rvnAcer:rnTangiz:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 7620 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1696312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version
>From previous experience in the same situation, *normally*, a typo like this are worth SRU'ing to stable release when it is bundled with other fixes (non-typo related). I'm afraid SRU'ing only this particular change won't make (SRU approval) it to -updates. Ivy, if you can find another cups bug to fix and merge the two in one SRU, I think you'll have better chance to get the SRU approval. Unless you can actually show that not fixing this particular bug has a significant impact. - Eric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1695876 Title: German Documentation file displays incorrect CUPS version Status in CUPS: Fix Released Status in cups package in Ubuntu: New Bug description: The /doc/de/index.html.in file in the package source has an incorrect version number written into a header instead of using '@CUPS_VERSION@' to populate this file as in the other languages' version of the same file, seemingly resulting in /usr/share/cups/doc-root/de/index.html having the wrong version once CUPS is installed: ... CUPS 2.0.2 ... instead of: ... CUPS @CUPS_VERSION@ ... resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1695876/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
The attachment "libmbim_1.12.2-2ubuntu1.1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693155] Re: Squashed blurry battery indicator in gnome-shell
The ubuntu-mono source does not exist post-precise. It was replaced with the ubuntu-themes source. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-mono in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version
Upstream commit url : https://github.com/apple/cups/commit/88d45155d6deb71e0ed2203d9bb1eb63a17d3abf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1695876 Title: German Documentation file displays incorrect CUPS version Status in CUPS: Fix Released Status in cups package in Ubuntu: New Bug description: The /doc/de/index.html.in file in the package source has an incorrect version number written into a header instead of using '@CUPS_VERSION@' to populate this file as in the other languages' version of the same file, seemingly resulting in /usr/share/cups/doc-root/de/index.html having the wrong version once CUPS is installed: ... CUPS 2.0.2 ... instead of: ... CUPS @CUPS_VERSION@ ... resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1695876/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696415] [NEW] NetworkManager seems to drop IPv4 DHCP lease even though it was successfully renewed
Public bug reported: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-04 (214 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: default via 192.168.0.5 dev eth0 proto static metric 100 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 37da1802-e1ce-3326-a6d0-f855cc32806d 802-3-ethernet 1496839466 wo 07 jun 2017 14:44:26 CEST yes 4294966297no /org/f
[Desktop-packages] [Bug 1696261] Re: Settings app items have bad text wrapping
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1696261 Title: Settings app items have bad text wrapping Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Ubuntu GNOME 17.04 with GNOME 3.24. gnome-control-center: Installed: 1:3.24.1-0ubuntu1 Candidate: 1:3.24.1-0ubuntu1 What actually happened: When I open settings, I find that my perfectly innocuous Region & Language settings have been kidnapped by a stranger named Lan Guage. I don't know who Mr. Guage is but I would like him to return my settings. What I expected to happen: Find settings app that has not been visited by Lan Guage. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 15:57:59 2017 InstallationDate: Installed on 2017-05-30 (7 days ago) InstallationMedia: System76 17.04 "Zesty Zapus" - Release amd64 (20170410) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1696261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Thanks for taking your time to work though this. My link name is vpn0 Link 3 (vpn0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: DNS Domain: ~. Link 2 (enp30s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.1 -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Thanks for the work Daniel, I've sponsored to Xenial let's see what the proposed testing is going ** Changed in: pulseaudio (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions -- Mailing list: https:
[Desktop-packages] [Bug 1201679] ❣extremely useful stuff
Yo! I found some extremely useful stuff and it was a real discovery for me, just give it a try! You may find more information here https://clck.ru/BDs9H Thanks for your consideration, pavlushko Sent from Mail for Windows 10 ** Attachment added: "41D20FC126EC5662475F99898210EF38.jpg" https://bugs.launchpad.net/bugs/1201679/+attachment/4891155/+files/41D20FC126EC5662475F99898210EF38.jpg -- 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/1201679 Title: ibus' Super+Space shortcut (usually) doesn't work Status in One Hundred Papercuts: Expired Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: 1. Add the ubuntu-desktop PPA on Ubuntu 13.10 "Saucy" sudo add-apt-repository ppa:ubuntu-desktop/ppa sudo apt-get update sudo apt-get upgrade sudo apt-get install indicator-keyboard 2. Log out and log back in. 2. Open System Settings>Region & Language 3. Switch to the Text Entry tab. 4. Click the + button to add at least two more keyboard layouts. 5. Log out and log back in. 6. Try to use the (new) default Super+Space keyboard shortcut to switch between keyboard layouts. What happens --- Usually, Super+Space is ignored. It worked for me once on login but every other time I tested it didn't work. It works fine in GNOME Shell but not in Unity. gsettings reset org.gnome.settings-daemon.plugins.media-keys switch-input-source seems to be enough to nudge Unity into respecting the Super+Space keyboard shortcut. My guess is that Unity is too aggressive in binding the Super key to itself. Workaround - Shift+Super+Space, the keyboard shortcut to switch backward between keyboard layouts works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jul 16 00:28:27 2013 InstallationDate: Installed on 2013-06-14 (31 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1201679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696418] [NEW] gnome-help/shell-introduction.page link to removed files
Public bug reported: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Affects: language-pack-gnome-es-base (Ubuntu) Importance: Undecided Status: New ** Tags: i386 language-pack-gnome trusty ** Also affects: language-pack-gnome-es-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: New Status in language-pack-gnome-es-base package in Ubuntu: New Bug description: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682978] Re: Random Screen Rotation
That happens to me also on Ubuntu Gnome 17.04. It's not random though but rather when the screen shuts off after I leave the computer inactive. When I turn the screen back on, it's 90 degrees clockwise (and quite puzzling to get the mouse working to be able to reboot because of muscle memory). -- 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/1682978 Title: Random Screen Rotation Status in xorg package in Ubuntu: Confirmed Bug description: My screen randomly rotates 90 degrees clockwise without warning. It has happened twice so far, once was yesterday after I installed UG 17.04, and once today. The first time was when I was still getting my system setup for myself after install, and the second time was while I had left the system unattended for an extended period of time. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 14 20:35:02 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-13 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
I am having the same issues even with the newer Kernel, 4.4.0-79-generic. Like others have mentioned above, I can mess with the settings and sometimes "it gets it" and other times it just causes the whole machine to lock up and I have to force reboot it. Even when the monitors do show up in xrandr - they are blank with the no signal screen. Messing with the settings becomes a 50/50 but even if it does "manage to find it", the moment you have to walk away, or the screen goes to sleep, its not coming back. Here is a screen shot of the error I get sometimes, other times, there is no error and the machine just locks. I am also on a Dell E7250 Intel Core i5-5300 Intel HD Graphics 5500 Broadwell GT2 ** Attachment added: "Error message" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686189/+attachment/4891194/+files/Ubuntu_Monitor_Issue.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696453] [NEW] Touch Screen Stops Working after restart
Public bug reported: Greetings! i have haier y11b laptop with touch screen touch screen works fine but after a restart it stops working. suspend does not affect any thing just restart. i works after i shutdown my laptop and turn it on again. ** Affects: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: touch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1696453 Title: Touch Screen Stops Working after restart Status in xinput package in Ubuntu: New Bug description: Greetings! i have haier y11b laptop with touch screen touch screen works fine but after a restart it stops working. suspend does not affect any thing just restart. i works after i shutdown my laptop and turn it on again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1696453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696459] [NEW] CIFS mounted directory flood request to Samba server
Public bug reported: cifs-utils 2:6.6-5ubuntu1, Ubuntu 17.04 x86_x64 - FSTAB mounted a cifs filesystem on startup of a Samba server version 2:4.5.8+dfsg-0ubuntu0.17.04.2 running Ubuntu 17.04 ARMHF with only "credentials" mount option, mounted directory access normally. - Samba server rebooted, on start get a very high CPU usage of /usr/sbin/smbd, only a remount of cifs client will solve this problem. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1696459 Title: CIFS mounted directory flood request to Samba server Status in lightdm package in Ubuntu: New Bug description: cifs-utils 2:6.6-5ubuntu1, Ubuntu 17.04 x86_x64 - FSTAB mounted a cifs filesystem on startup of a Samba server version 2:4.5.8+dfsg-0ubuntu0.17.04.2 running Ubuntu 17.04 ARMHF with only "credentials" mount option, mounted directory access normally. - Samba server rebooted, on start get a very high CPU usage of /usr/sbin/smbd, only a remount of cifs client will solve this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1696459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694454] Re: Can't open gnome terminal
I managed to start the gnome-terminal via this command: "dbus-launch gnome-terminal" It outputs this error tho: "WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." I also managed to start it with: "sudo gnome-terminal" without any errors. Before that I tried "locale-gen" and "sudo localectl set-locale LANG="en_US.UTF-8"" as mentioned in similar forum posts but they don't seem to help in this case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1694454 Title: Can't open gnome terminal Status in gnome-terminal package in Ubuntu: New Bug description: Selecting gnome terminal after search(winkey->type "term"->select Terminal), results in loading terminal for a few seconds and simply disappearing of the loading indication from the title bar. Nothing else happens. No error and no terminal shown. This behavior appeared after upgrade to 17.04 I don't have such a problem when opening MATE Terminal. Also when I run "gnome-terminal" in the mate terminal it outputs this: "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" >> lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 >> apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu8 Candidate: 3.20.2-1ubuntu8 Version table: *** 3.20.2-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 30 17:15:09 2017 InstallationDate: Installed on 2015-06-17 (713 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1694454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696256] Re: libllvm-3.8-ocaml-dev: missing files in package
** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.8 in Ubuntu. https://bugs.launchpad.net/bugs/1696256 Title: libllvm-3.8-ocaml-dev: missing files in package Status in llvm-toolchain-3.8 package in Ubuntu: New Bug description: [Xenial] libllvm-ocaml-dev creates a link to /usr/lib/ocaml/llvm-3.8 but this file doesn't exist and probably should be included in libllvm-3.8 -ocaml-dev. # apt-get install libllvm-ocaml-dev # ocamlfind query llvm ocamlfind: Package `llvm' not found # ls -lA /usr/lib/ocaml/llvm lrwxrwxrwx 1 root root 8 Jun 21 2016 /usr/lib/ocaml/llvm -> llvm-3.8 # ls -lA /usr/lib/ocaml/llvm-3.8 ls: cannot access '/usr/lib/ocaml/llvm-3.8': No such file or directory # dpkg -L libllvm-ocaml-dev /. /usr /usr/share /usr/share/doc /usr/share/doc/libllvm-ocaml-dev /usr/share/doc/libllvm-ocaml-dev/copyright /usr/lib /usr/lib/ocaml /usr/lib/ocaml/METAS /usr/share/doc/libllvm-ocaml-dev/changelog.Debian.gz /usr/share/doc/libllvm-ocaml-dev/NEWS.Debian.gz /usr/lib/ocaml/METAS/META.llvm /usr/lib/ocaml/llvm # dpkg -L libllvm-3.8-ocaml-dev /. /var /var/lib /var/lib/ocaml /var/lib/ocaml/md5sums /var/lib/ocaml/md5sums/libllvm-3.8-ocaml-dev.md5sums /var/lib/ocaml/lintian /var/lib/ocaml/lintian/libllvm-3.8-ocaml-dev.info /usr /usr/lib /usr/lib/ocaml /usr/lib/ocaml/META /usr/share /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/libllvm-3.8-ocaml-dev /usr/share/doc /usr/share/doc/libllvm-3.8-ocaml-dev /usr/share/doc/libllvm-3.8-ocaml-dev/copyright /usr/share/doc/libllvm-3.8-ocaml-dev/changelog.Debian.gz /usr/share/doc/libllvm-3.8-ocaml-dev/NEWS.Debian.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1696256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files
Thanks for your report. This is a bit confusing, since language-pack- gnome-es-base was last updated in trusty almost a year ago. Can you please run: sudo apt-get install --reinstall language-pack-gnome-es-base and let us know if it makes a difference. ** Changed in: gnome-user-docs (Ubuntu) Status: New => Incomplete ** Changed in: language-pack-gnome-es-base (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: Confirmed Status in language-pack-gnome-es-base package in Ubuntu: Confirmed Bug description: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files
Hmm... I now see that precisely the update I mentioned did fail with respect to gnome-help. https://packages.ubuntu.com/trusty-updates/all/language-pack-gnome-es- base/filelist This needs to be investigated further. Thanks again! ** Changed in: gnome-user-docs (Ubuntu) Status: Incomplete => Confirmed ** Changed in: language-pack-gnome-es-base (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: Confirmed Status in language-pack-gnome-es-base package in Ubuntu: Confirmed Bug description: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Huh. No, actually my patch DID work. See the line under vpn0 that says DNS Domain: ~. So the correct bus call was made and all dns queries SHOULD be directed to the link-specified listed DNS servers. Your problem actually appears to be that there are no link-specified dns servers. See the line that says DNS Servers: Please try manually specifying the correct DNS servers in the network-manager-openconnect gui settings. That should fix your problem I believe. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553434] Re: fglrx-updates-core 2:15.201-0ubuntu0.14.04.1: fglrx-updates-core module failed to build for xenia kernel (generic and lowlatency)
*** This bug is a duplicate of bug 1502978 *** https://bugs.launchpad.net/bugs/1502978 Same thing happened again. Why is this still marked as a duplicate? Is this indicative of another flaw in the system? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1553434 Title: fglrx-updates-core 2:15.201-0ubuntu0.14.04.1: fglrx-updates-core module failed to build for xenia kernel (generic and lowlatency) Status in fglrx-installer-updates package in Ubuntu: Confirmed Bug description: Not sure if apport-bug includes the following info, so I'll include the compile error just in case it doesn't. Note: the module does build on the -wily kernels. Hardware: Toshiba Sattellite A300-1M9, a fantastic laptop built in 2008. They don't build 'em like that anymore. But it has more features in it than today's laptops. But anyway. Lest I turn it into a sales pitch, here's the compile error from dkms: /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c: In function ‘firegl_major_proc_read’: /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be len = seq_printf(m, "%d\n", major); ^ /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c: In function ‘KCL_fpu_save_init’: /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:6508:49: error: ‘XSTATE_FP’ undeclared (first use in this function) if (!(fpu->state.xsave.header.xfeatures & XSTATE_FP)) ^ /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:6508:49: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c: At top level: /var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:6498:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ make[2]: *** [/var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.o] Error 1 Cheers. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-updates-core 2:15.201-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-9.24~14.04.1~beta1-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-9-generic Date: Sat Mar 5 02:33:09 2016 DuplicateSignature: dkms:fglrx-updates-core:2:15.201-0ubuntu0.14.04.1:/var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be PackageVersion: 2:15.201-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: fglrx-installer-updates Title: fglrx-updates-core 2:15.201-0ubuntu0.14.04.1: fglrx-updates-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1553434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
The DNS servers have always been listed under the vpn0 link when I run systemd-resolve --status, even before your patch. I still get no internal network name resolution, even when hard coding the DNS servers in network manager. Maybe I've got a different issue than what others are seeing, but I have confirmed that on 16.10 the vpn works correctly, resolves internal names, and doesn't leak, but on 17.04 it no longer works. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files
@Sebastien: One theory about what might have caused this is that the latest full langpack update for trusty happened at a point of time (2016-07-20) when gnome-user-docs had been moved to universe, and hence was ignored by the langpack builder. The easiest way (workaround) to fix it is probably to rebuild gnome- user-docs without translation stripping. (Would add approximately 8 MB to the ISO.) The not-so-easy way is a full langpack update for trusty (without testing as a requirement to move the packages to -updates), while making sure somehow that gnome-help isn't ignored. Might need to be preceded by a no-change rebuild of gnome-user-docs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: Confirmed Status in language-pack-gnome-es-base package in Ubuntu: Confirmed Bug description: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696502] [NEW] Suspend laptop while ethernet is connected with wifi disabled, unplug ethernet, wake laptop, NetworkManager never recovers
Public bug reported: Repro steps: 1. Configure ethernet not to enable automatically when plugged in. 2. Plug laptop into ethernet and enable ethernet connection. 3. Disable wifi. 4. Confirm that you have network connectivity. 5. Suspend laptop. 6. Unplug ethernet. 7. Wake laptop. NetworkManager hangs forever trying to reestablish the ethernet connection that is no longer there. You can't even interrupt it because the "Disconnect" menu item is greyed out (see screenshot). Only recovery is to restart NetworkManager. Sometimes it seems like I even have to restart it twice to recover. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Jun 7 13:18:23 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-05-19 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.43.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.50 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-05-19T14:16:03.840790 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Selection_005.png" https://bugs.launchpad.net/bugs/1696502/+attachment/4891480/+files/Selection_005.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696502 Title: Suspend laptop while ethernet is connected with wifi disabled, unplug ethernet, wake laptop, NetworkManager never recovers Status in network-manager package in Ubuntu: New Bug description: Repro steps: 1. Configure ethernet not to enable automatically when plugged in. 2. Plug laptop into ethernet and enable ethernet connection. 3. Disable wifi. 4. Confirm that you have network connectivity. 5. Suspend laptop. 6. Unplug ethernet. 7. Wake laptop. NetworkManager hangs forever trying to reestablish the ethernet connection that is no longer there. You can't even interrupt it because the "Disconnect" menu item is greyed out (see screenshot). Only recovery is to restart NetworkManager. Sometimes it seems like I even have to restart it twice to recover. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Jun 7 13:18:23 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-05-19 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.43.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.50 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-05-19T14:16:03.840790 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.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/1696502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files
Gunnar, there are no more scheduled 14.04 iso releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: Confirmed Status in language-pack-gnome-es-base package in Ubuntu: Confirmed Bug description: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695983] Re: Removing an imported openvpn connection doesn't clean up copied certificates
Sorry, xorg is certainly nonsense... I just ran "ubuntu-bug" and selected "Other problem". As all the following options where related to display problem, I selected "I don't know". That's how I ended up filing it against xorg. -- 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/1695983 Title: Removing an imported openvpn connection doesn't clean up copied certificates Status in xorg package in Ubuntu: Incomplete Bug description: I imported an openvpn connection with the KDE network manager, which worked fine. On import I was asked whether I want my certificates to be copied to .local/share/networkmanagement, which I confirmed. Them I removed my connection and reimported it again, this time receiving the following error message: "Error copying certificate to /home/user/.local/share/networkmanagement/certificates/myopenvpn.key: Destination file exists" Seems like copied certificates aren't cleaned up when an openvpn connection is removed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 5 21:56:31 2017 InstallationDate: Installed on 2017-06-04 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695983] Re: Removing an imported openvpn connection doesn't clean up copied certificates
Though I could swear that in the web interface I then selected "I don't know" instead of "xorg"... -- 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/1695983 Title: Removing an imported openvpn connection doesn't clean up copied certificates Status in xorg package in Ubuntu: Incomplete Bug description: I imported an openvpn connection with the KDE network manager, which worked fine. On import I was asked whether I want my certificates to be copied to .local/share/networkmanagement, which I confirmed. Them I removed my connection and reimported it again, this time receiving the following error message: "Error copying certificate to /home/user/.local/share/networkmanagement/certificates/myopenvpn.key: Destination file exists" Seems like copied certificates aren't cleaned up when an openvpn connection is removed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 5 21:56:31 2017 InstallationDate: Installed on 2017-06-04 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Huh, weird, yeah it's quite possible it's a different issue entirely, or a problem related to network-manager-openconnect. Because the routing- only domain is clearly listed as DNS Domain ~. so systemd-resolved should only send queries to the specified dns servers for the interface vpn0. Yeah...not sure sorry. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files
@Jeremy: That's good, I suppose. Then a rebuild without translation stripping ought to be less controversial. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: Confirmed Status in language-pack-gnome-es-base package in Ubuntu: Confirmed Bug description: p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Also here Ubuntu 16.04, kernel 4.11.3, Asus UX303UB. Probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125 -- 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/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: Fix Released Status in OEM Priority Project xenial series: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 RESULT: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. WORKAROUND: (http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade) SYSTEM INFO: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS
** Description changed: - Note to Sponsors - - Since Precise is still partially open, let's see if the Release/SRU Teams are willing to accept this SRU for Precise ecause of the Impact there. + Note + + Yes, I know precise is basically unsupported but it might be nice to fix Travis here anyway. Impact -- Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS. This is a problem because the very popular Travis service for continuous integration (CI) on platforms like Github still uses 12.04 LTS. Travis does not offer a 16.04 platform and the 14.04 platform is still only in beta. This caused this pull request to fail its CI check: https://travis-ci.org/zdohnal/system-config-printer/builds/222023750 https://github.com/zdohnal/system-config-printer/pull/41 This SRU adds these Desktop Environments to the recognized list for 14.04 LTS: Cinnamon, EDE, LXQt. If accepted, 12.04 LTS will also add TDE. Test Case - 1. Save the following lines in a file named calc.desktop [Desktop Entry] Name=Calculator Exec=gnome-calculator Icon=accessories-calculator Type=Application OnlyShowIn=Cinnamon;LXQt;EDE; Categories=GNOME;GTK;Utility;Calculator; 2. Run desktop-file-validate calc.desktop The command should complete with no error message. A failure would look something like: calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Cinnamon"; values extending the format should start with "X-" Regression Potential - This only adds a few entries to the list of registered desktop environments. This change is backported from desktop-file-utils 0.23 which is in Ubuntu 16.04 LTS. ** Changed in: desktop-file-utils (Ubuntu Precise) Status: Triaged => In Progress ** Changed in: desktop-file-utils (Ubuntu Trusty) Status: Triaged => In Progress ** Patch removed: "desktop-file-utils-lp1693089-precise.patch" https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+attachment/4882254/+files/desktop-file-utils-lp1693089-precise.patch ** Patch removed: "desktop-file-utils-lp1693089-trusty.patch" https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+attachment/4882255/+files/desktop-file-utils-lp1693089-trusty.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1693089 Title: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS Status in desktop-file-utils package in Ubuntu: Fix Released Status in desktop-file-utils source package in Precise: In Progress Status in desktop-file-utils source package in Trusty: In Progress Bug description: Note Yes, I know precise is basically unsupported but it might be nice to fix Travis here anyway. Impact -- Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS. This is a problem because the very popular Travis service for continuous integration (CI) on platforms like Github still uses 12.04 LTS. Travis does not offer a 16.04 platform and the 14.04 platform is still only in beta. This caused this pull request to fail its CI check: https://travis-ci.org/zdohnal/system-config-printer/builds/222023750 https://github.com/zdohnal/system-config-printer/pull/41 This SRU adds these Desktop Environments to the recognized list for 14.04 LTS: Cinnamon, EDE, LXQt. If accepted, 12.04 LTS will also add TDE. Test Case - 1. Save the following lines in a file named calc.desktop [Desktop Entry] Name=Calculator Exec=gnome-calculator Icon=accessories-calculator Type=Application OnlyShowIn=Cinnamon;LXQt;EDE; Categories=GNOME;GTK;Utility;Calculator; 2. Run desktop-file-validate calc.desktop The command should complete with no error message. A failure would look something like: calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Cinnamon"; values extending the format should start with "X-" Regression Potential - This only adds a few entries to the list of registered desktop environments. This change is backported from desktop-file-utils 0.23 which is in Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1515446] Re: network file systems in FSTAB no longer mount at boot with NetworkManager
I can confirm that. I updated 16.04 (works) -> 16.10 (works) -> 17.04 (doesn't work any more). calling "mount -a" mounts the directories without problems. -- 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/1515446 Title: network file systems in FSTAB no longer mount at boot with NetworkManager Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Wily: Fix Released Status in network-manager package in Debian: New Bug description: [Impact] * This breaks NFS mounts coming up reliably. In some cases this can be quite intermittent. [Test Case] 1. Add a mountpoint to an NFS share by name to fstab. 2. See that it mounts with the mount command. 3. Reboot 5+ times, note that it doesn't come up all (or the majority of the time). [Regression Potential] * There could be a regression for the same reason it's blocked in Debian, because of dependency issues with packages not converted to systemd that want to run /etc/rcS.d/. You can check for this by looking for breaking/disable services during bootup. Ubuntu is in a much better state than Debian, but there is a possibility we missed something. Otherwise, this will increase boot time, but when the user logs the networking will be more likely to be ready. -Previous description- After a fresh install of 15.10, nfs shares no longer mount on boot. I'm using the same line to mount as I did in 14.04 prior: :/share /mnt/share ntfs4 _netdev, auto 0 0 This line worked just fine in 14.04, and 14.10 on my laptop, to mount the shares at boot. Manual mounting after boot works fine. Systemctl shows a name resolution failure (see below) lsb_release -rd Description:Ubuntu 15.10 Release:15.10 lsb_release -rd Description:Ubuntu 15.10 Release:15.10 bjwest@razorback:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.2.8-9ubuntu10 Candidate: 1:1.2.8-9ubuntu10 Version table: *** 1:1.2.8-9ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status systemctl status mnt-share.mount ● mnt-share.mount - /mnt/share Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 15s ago Where: /mnt/share What: hog:/share Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev (code=exited, status=32) Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share... Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server hog: Temporary failure in name resolution Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, code=exited status=32 Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share. Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1515446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1515446] Re: network file systems in FSTAB no longer mount at boot with NetworkManager
As workaround you can put "mount -a" into /etc/rc.local just before the "exit 0". This at least works here to get my shares. How can I help to solve this? -- 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/1515446 Title: network file systems in FSTAB no longer mount at boot with NetworkManager Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Wily: Fix Released Status in network-manager package in Debian: New Bug description: [Impact] * This breaks NFS mounts coming up reliably. In some cases this can be quite intermittent. [Test Case] 1. Add a mountpoint to an NFS share by name to fstab. 2. See that it mounts with the mount command. 3. Reboot 5+ times, note that it doesn't come up all (or the majority of the time). [Regression Potential] * There could be a regression for the same reason it's blocked in Debian, because of dependency issues with packages not converted to systemd that want to run /etc/rcS.d/. You can check for this by looking for breaking/disable services during bootup. Ubuntu is in a much better state than Debian, but there is a possibility we missed something. Otherwise, this will increase boot time, but when the user logs the networking will be more likely to be ready. -Previous description- After a fresh install of 15.10, nfs shares no longer mount on boot. I'm using the same line to mount as I did in 14.04 prior: :/share /mnt/share ntfs4 _netdev, auto 0 0 This line worked just fine in 14.04, and 14.10 on my laptop, to mount the shares at boot. Manual mounting after boot works fine. Systemctl shows a name resolution failure (see below) lsb_release -rd Description:Ubuntu 15.10 Release:15.10 lsb_release -rd Description:Ubuntu 15.10 Release:15.10 bjwest@razorback:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.2.8-9ubuntu10 Candidate: 1:1.2.8-9ubuntu10 Version table: *** 1:1.2.8-9ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status systemctl status mnt-share.mount ● mnt-share.mount - /mnt/share Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 15s ago Where: /mnt/share What: hog:/share Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev (code=exited, status=32) Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share... Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server hog: Temporary failure in name resolution Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, code=exited status=32 Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share. Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1515446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652299] Re: Menus jump around under Wayland
** Changed in: gimp Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1652299 Title: Menus jump around under Wayland Status in The Gimp: Expired Status in Ubuntu GNOME: New Status in gimp package in Ubuntu: New Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 that when I for instance will go to the Filters menu and go down to Artistic and then when I move my mouse to where its pull-down menu is, I find that suddenly it jumps to the File menu being open, or another one. This is not always the case, but it happens a lot, so much that it disrupts my work. This happens with quite a few of the pull-down menus, though mostly with the longer ones. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gimp 2.8.18-1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 23 12:41:28 2016 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gimp UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1652299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696580] [NEW] dificultades con kadenlive
Public bug reported: No funciona en el ambiente mate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 7 16:22:27 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-06-07 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: Error: no composite extension UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 1155-0718-8197-6541-2374-2356-24 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jun 7 14:25:27 2017 xserver.configfile: default xserver.devices: inputMicrosoft Vmbus HID-compliant Mouse TOUCHSCREEN, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputTPPS/2 IBM TrackPoint MOUSE, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1696580 Title: dificultades con kadenlive Status in xorg package in Ubuntu: New Bug description: No funciona en el ambiente mate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 7 16:22:27 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-06-07 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UnitySupportTest: Error: comman
[Desktop-packages] [Bug 301749] Re: installed GTK themes are not completely deleted in gnome-appearance-properties
** Changed in: gnome-control-center Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/301749 Title: installed GTK themes are not completely deleted in gnome-appearance- properties Status in gnome-control-center: Expired Status in gnome-control-center package in Ubuntu: Invalid Bug description: Say I install a new GTK theme and remove it afterwards by clicking "delete" in "gnome-appearance-properties", "Theme" tab. Then there is still the whole data of the theme in ~/.themes. I don't think that this is intended, or is it? The thing is that I also had problems at times when I wanted to reinstall the whole theme again: then the old directory clashed with the new one (they had the same name). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/301749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
Well, this bug also is affecting me, I used the workaround in #10 and it works, but I still need to put my password in order to unlock the "Login" Keyring (My system don't have autologin enabled btw), the weird thing is that this system is fresh installed (no more than a week) and It was working fine until today. Maybe there is some package that I installed yesterday that is affecting the system. Google-chrome affected Online accounts also is affected I didn't test other apps, but as far I could check those apps were affected by this issue Greetings -- 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/1689825 Title: gnome-keyring not unlocked on boot Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] [NEW] [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
Public bug reported: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Lots of idle time; started playing an audio stream and pulseaudio died after about 10 seconds of audio" https://bugs.launchpad.net/bugs/1696589/+attachment/4891698/+files/pulseverbose.log.1.failed-after-10-seconds.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink P
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
** Attachment added: "log up to point of failure, but I don't remember details of activity at the time" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+attachment/4891706/+files/pulseverbose.log.3.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
** Attachment added: "log up to point of failure, but I don't remember details of activity at the time" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+attachment/4891707/+files/pulseverbose.log.4.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
Each time this failure occurs it is sufficient to run "pulseaudio --start" to get my devices back online, then restart the audio apps so they can find the device again. I normally use the external audio device (headphone jack) on a hot- plugged ThinkPad OneLink Plus dock. I have not seen pulseaudio fail when the laptop is not docked, but I don't listen to audio much in that mode. The failure does not seem to be coincident with plug/unplug actions. It seems to be tied to audio playback. -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685104] Re: Netflix returns error F7363-1260 as movie loads. Loading site is good
I wanted to add that I am seeing this problem - however, Netflix initially worked fine for about a month. My current Firefox version is 53.0.3 32-bit. I do not know if this is the version that was installed with Ubuntu Mate (16.04 LTS), or if I was updated to 53.0.3. (and if it was an update, I don't know when it occurred - I'm new at linux, and the logging I was able to find in Firefox did not show any updates). Netflix was working, I left the machine for a while and was logged out. When I came back, I received the error. No amount of disabling extensions, restarting, logging out/in, and cache clearing has had any effect. Luckily, I have another machine I can use to watch, but I hope someone is able to fix this soon. If anyone would like further information from me, I am happy to help, but I will need instructions on how to get the information you want. -- 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/1685104 Title: Netflix returns error F7363-1260 as movie loads. Loading site is good Status in firefox package in Ubuntu: Confirmed Bug description: Loading the Netflix site is good. The home page comes up with the movie choices displayed. The speed is good. The movies have played very well with a good quality image, since 2010 or so, until about two or three days ago. A little choppiness is appearant for a short time at start up, but it always evens out. Now, when a movie choice is made, it starts to load a movie and then returns error codes. At first, it returned the error codes F7363-1260 and F7355-1204. I have reloaded pipelight and I set libevcodec to true. I also reinstalled the repository ppa:heyarje/libav-11 and got libav-tools libavcodec-extra-56. I reinstalled wine. These actions eliminated the error F7355-1204, but not the error F7363-1260. My OS is 12.04. On a 32 bit machine. Chrome was not an option because firefox has always done a great job. Now I can't get 32 bit chrome. I have the Netflix desk top, which is too resource intensive, so I don't use it. I have widevine. I just recently installed UAControl, which I have never needed, and I am learning to use it. My thoery is that firefox sent out an update that has reset something that I am not aware of, because I am sure that I set libev to true in the past and I had to have wine to run silver light. I have noticed that a stop script message has been displayed with increasing frequency, but that is on the home page. I simply reload the page to cure this problem. Thank you, Bill Delaney ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 52.0.2+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-116-generic. ApportVersion: 2.0.1-0ubuntu17.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1928 F pulseaudio BuildID: 20170329151308 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with AD1980 at irq 23' Mixer name : 'Analog Devices AD1980' Components : 'AC97a:41445370' Controls : 41 Simple ctrls : 29 Channel: Unavailable Date: Fri Apr 21 00:41:56 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Locales: extensions.sqlite corrupt or missing MarkForUpload: True MostRecentCrashID: bp-7b5ef866-3e71-476f-a75e-9d9d32160710 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=52.0.2/20170329151308 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-7b5ef866-3e71-476f-a75e-9d9d32160710 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to precise on 2016-02-11 (435 days ago) dmi.bios.date: 07/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0U7077 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/07/2006:svnDellInc.:pnDimension8400:pvr:rvnD
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
It's my lucky day. Pulseaudio has failed several times today. I see this in syslog for only one of the failures: $ grep -Ei "alsa|pulseaudio|usb" /var/log/syslog Jun 7 14:50:15 phord-x1 pulseaudio[9173]: CLI got EOF from user. Jun 7 14:50:15 phord-x1 pulseaudio[9173]: Freed 27 "UNIX socket client" Jun 7 14:50:15 phord-x1 pulseaudio[9173]: Created 28 "UNIX socket client" Jun 7 14:50:15 phord-x1 pulseaudio[9173]: CLI got EOF from user. Jun 7 14:50:15 phord-x1 pulseaudio[9173]: Freed 28 "UNIX socket client" Jun 7 14:50:32 phord-x1 pulseaudio[9173]: Created 29 "UNIX socket client" Jun 7 15:16:36 phord-x1 pulseaudio[9173]: Got POLLNVAL from ALSA Jun 7 15:16:36 phord-x1 pulseaudio[9173]: Could not recover from POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device Jun 7 15:16:36 phord-x1 kernel: [26867.240852] usb 1-4.1.4: reset full-speed USB device number 18 using xhci_hcd After this I ran pulseaudio manually. An hour or so later it quit. Not much detail, though: $ time LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 [1]17630 killed LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 32.48s user 29.58s system 1% cpu 1:08:45.80 total I've attached the log from that 2nd failure (PID=17630). I don't have the log from the first one because I had restarted it manually without logs earlier in the day. ** Attachment added: "pulseaudio log from another failure" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+attachment/4891739/+files/pulseverbose.log.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Patch removed: "patch for network-manager source" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch ** Patch removed: "possible cisco network-manager-openconnect-fix" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4890352/+files/resolved-vpn-dns-leak-fix.patch ** Attachment removed: "patched network manager .deb for easy fix installation on Ubuntu 17.04" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4889755/+files/network-manager_1.4.4-1ubuntu3_amd64.deb ** Attachment removed: "updated patched .deb packaged network-manager for easy testing" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4890421/+files/network-manager_1.4.4-1ubuntu3_amd64.deb -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Bug is confirmed to still be active in: 4.8.0-54-generic #57~16.04.1-Ubuntu SMP Wed May 24 16:22:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I am doing what andreasj64 does to get by. If I was a C programmer I'd work on it, but I'm Java and Python. -- 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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
In reference to John Bedford's comment: >bedfojo (commercial-johnbedford) wrote on 2017-06-06: #57 >Nicholas, thank you very much for your work on this patch. >It works correctly for me: no DNS leak detected by either https://ipleak.net >or >https://dnsleaktest.com for me, when both detected leaks in the unpatched >version. >Running Ubuntu-MATE 17.04. >Could we perhaps get this upstreamed into NM? >bedfojo (commercial-johnbedford) wrote on 2017-06-06: #58 >I should add that I'm using network-manager-openvpn and >network-manager-openvpn-gnome. I think it would be great if we could get this patch upstreamed into the network-manager! I've attached a finalized version of the patch with a more informative / verbose syslog message that also accounts for cisco gre/gretap connections not in #49. Please use this patch when building network-manager for Ubuntu 17.04. I will also attach a .deb build of network-manager for easy installation and testing for anyone interested. So far, this is known to solve dns leaks with network-manager-openvpn but could also solve dns leaks for other VPNs that use TUN, TAP, or Cisco GRE network interfaces through the network-manager. You should now see a message in your syslog when connecting that looks like the following: NetworkManager[32636]: [1496880041.6435] systemd-resolved[0x55cc602ce430]: Link #12 type is VPN TUN or TAP, fixing DNS leak... Make sure to stop apt from replacing the patched .deb using: sudo apt-mark hold network-manager To verify that you are using the 'routing-only domain', use the command systemd-resolve --status and look for the line "DNS Domain: ~." under the VPN link number. Alternatively, check that you are not experiencing DNS leaks using the 'extended test' on https://dnsleaktest.com/ Cheers :) ** Patch added: "resolved-vpn-dns-leak-fix.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4891740/+files/resolved-vpn-dns-leak-fix.patch -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Attachment added: "patched network-manager .deb for easy testing on Ubuntu 17.04" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4891741/+files/network-manager_1.4.4-1ubuntu4_amd64.deb -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)
Hi Mao, I have installed a version of the kernel which ignores the capabilities of the PCI bridge when determining whether a device can be the boot device. With this patched kernel, X starts without needing a config file. This confirms: - that the vga card is not marked as boot device because of the the PCI bridge that the VGA card sits behind. - not being marked as boot vga is what is causing X not to pick it up the card. This is a debug patch only, and not a patch we will be able to get upstream, so I think we will need to discuss with the HiSilicon people why their hardware is behaving this way. Regards, Daniel -- 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/1691991 Title: Xorg Segmentation fault on Hisilicon D05 board (arm64) Status in xorg package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg [sudo] password for ubuntu: X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu Current Operating System: Linux ubuntu 4.10.0-20.22-generic #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug earlycon=pl011,mmio,0x602B console=tty0 Build Date: 02 November 2016 10:05:28PM xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" pci id for fd 10: 19e5:1711, driver (null) EGL_MESA_drm_image required. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48] (EE) (EE) Segmentation fault at address 0xa0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. Aborted (core dumped) ubuntu@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1689371] Re: Update gnome-desktop3 to 3.24.2
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1689371 Title: Update gnome-desktop3 to 3.24.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Zesty: Fix Committed Bug description: Impact -- The only purpose of this update is to update the reported GNOME version number to 3.24.2. Since this is the last scheduled project-wide point release for GNOME 3.24, this should be the last update like this for Ubuntu 17.04. https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-24 Test Case - Install gnome-recipes (this version is a very large download; it will be a smaller download in 17.10) Open the Recipes app. In the top bar, click the Recipes app menu and select About. Switch to the System tab. The Desktop should say "GNOME 3.24.2". Regression Potential There shouldn't really be a regression here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1689371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)
hi Daniel, Agree with you that is something they need to fix. I have sent mail to HiSilicon and their VGA card vendors and they replied some for confirming and understand questions or our requests. I will push them again. thanks, Mao On Thu, Jun 8, 2017 at 8:41 AM, Daniel Axtens wrote: > Hi Mao, > > I have installed a version of the kernel which ignores the capabilities > of the PCI bridge when determining whether a device can be the boot > device. With this patched kernel, X starts without needing a config > file. > > This confirms: > - that the vga card is not marked as boot device because of the the PCI > bridge that the VGA card sits behind. > - not being marked as boot vga is what is causing X not to pick it up the > card. > > This is a debug patch only, and not a patch we will be able to get > upstream, so I think we will need to discuss with the HiSilicon people > why their hardware is behaving this way. > > Regards, > Daniel > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1691991 > > Title: > Xorg Segmentation fault on Hisilicon D05 board (arm64) > > Status in xorg package in Ubuntu: > New > > Bug description: > ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg > [sudo] password for ubuntu: > > X.Org X Server 1.18.4 > Release Date: 2016-07-19 > X Protocol Version 11, Revision 0 > Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu > Current Operating System: Linux ubuntu 4.10.0-20.22-generic > #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64 > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic > root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug > earlycon=pl011,mmio,0x602B console=tty0 > Build Date: 02 November 2016 10:05:28PM > xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see > http://www.ubuntu.com/support) > Current version of pixman: 0.33.6 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017 > (==) Using system config directory "/usr/share/X11/xorg.conf.d" > pci id for fd 10: 19e5:1711, driver (null) > EGL_MESA_drm_image required. > (EE) > (EE) Backtrace: > (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48] > (EE) > (EE) Segmentation fault at address 0xa0 > (EE) > Fatal server error: > (EE) Caught signal 11 (Segmentation fault). Server aborting > (EE) > (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org >for help. > (EE) Please also check the log file at "/var/log/Xorg.0.log" for > additional information. > (EE) > (EE) Server terminated with error (1). Closing log file. > Aborted (core dumped) > ubuntu@ubuntu:~$ > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions > -- Zhanglei Mao Solutions Architect, Sales and Business Development Canonical Group Ltd. zhanglei@canonical.com +86-13625010929 (m) +852-6700 6026 (m) www.ubuntu.com www.canonical.com -- 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/1691991 Title: Xorg Segmentation fault on Hisilicon D05 board (arm64) Status in xorg package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg [sudo] password for ubuntu: X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu Current Operating System: Linux ubuntu 4.10.0-20.22-generic #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug earlycon=pl011,mmio,0x602B console=tty0 Build Date: 02 November 2016 10:05:28PM xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" pci id for fd 10: 19e5:1711, driver (null) EGL_MESA_drm_image required. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xa
[Desktop-packages] [Bug 1696618] [NEW] Certain emails are not loaded properly via IMAP+
Public bug reported: I'm pretty sure this is a bug, as it is not documented nor reported by anyone else before. 1) simone@simone-ThinkPad-T540p:~$ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 2) simone@simone-ThinkPad-T540p:~$ apt-cache policy evolution evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://ftp.sjtu.edu.cn/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://ftp.sjtu.edu.cn/ubuntu xenial/universe amd64 Packages 3) This bug is ***serious, as it scares people away from Evolution. I have setup my main email account as IMAP+. Most of the email are downloaded correctly, but some of them are not. From the message source, it seems that is a MULTIPART message, and not all parts are loaded. When the problem happens, all headers are not displayed when previewing the mail, but somehow the "From" in the list is correct. To view the email, I have to use my phone (K9 Mail) or Thunderbird. I am really wanting to switch to Evolution because I think is an overall better, more performing and more integrated program, but this stupid bug is causing me to think it over. 4) I expect to see the message when I click it... not empty If you need any further info, like the complete exact message source code, I **can** provide it (nothing secret in there). ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1696618 Title: Certain emails are not loaded properly via IMAP+ Status in evolution package in Ubuntu: New Bug description: I'm pretty sure this is a bug, as it is not documented nor reported by anyone else before. 1) simone@simone-ThinkPad-T540p:~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 2) simone@simone-ThinkPad-T540p:~$ apt-cache policy evolution evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://ftp.sjtu.edu.cn/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://ftp.sjtu.edu.cn/ubuntu xenial/universe amd64 Packages 3) This bug is ***serious, as it scares people away from Evolution. I have setup my main email account as IMAP+. Most of the email are downloaded correctly, but some of them are not. From the message source, it seems that is a MULTIPART message, and not all parts are loaded. When the problem happens, all headers are not displayed when previewing the mail, but somehow the "From" in the list is correct. To view the email, I have to use my phone (K9 Mail) or Thunderbird. I am really wanting to switch to Evolution because I think is an overall better, more performing and more integrated program, but this stupid bug is causing me to think it over. 4) I expect to see the message when I click it... not empty If you need any further info, like the complete exact message source code, I **can** provide it (nothing secret in there). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1696618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693155] Re: Squashed blurry battery indicator in gnome-shell
** No longer affects: ubuntu-mono (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-mono in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
I'm not familiar with what Fix Committed means on SRUs, but will keep an eye on: https://launchpad.net/ubuntu/+source/pulseaudio (it's not there yet) -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
** Changed in: oem-priority/xenial Status: Fix Released => Triaged ** Changed in: oem-priority Status: Fix Released => Triaged ** Changed in: oem-priority Status: Triaged => In Progress ** Changed in: oem-priority Status: In Progress => Triaged -- 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/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged Status in network-manager package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 RESULT: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. WORKAROUND: (http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade) SYSTEM INFO: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in again
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1696621 Title: Desktop icons slip under the top bar after logging in again Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in again
Yes and no. Nautilus draws the desktop (including icons) but it remains to be seen where the root cause of this bug is. It might be gnome-shell failing to communicate the work area correctly to nautilus... As for whether to show desktop icons at all, it should be noted this is a different decision to when we were looking at Unity8. In Unity8/Mir the desktop icons didn't exist simply because supporting desktop windows like nautilus wasn't anywhere near implemented yet. But users did complain even in the limited testing of Unity8, about not being able to use the desktop as a desktop for icons. -- 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/1696621 Title: Desktop icons slip under the top bar Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in again
Also note... Starting in http://cdimage.ubuntu.com/daily-live/20170607/ the live session relies on putting icons on the desktop and this bug is immediately visible on boot. So I guess we do need to fix this. ** Summary changed: - Desktop icons slip under the top bar after logging in again + Desktop icons slip under the top bar ** Description changed: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. + + The same problem is visible in the Ubuntu live session starting with + 20170607. ** Tags added: visual-quality ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: nautilus (Ubuntu) Importance: Undecided => Medium -- 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/1696621 Title: Desktop icons slip under the top bar Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in
** Summary changed: - Desktop icons slip under the top bar + Desktop icons slip under the top bar after logging in -- 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/1696621 Title: Desktop icons slip under the top bar after logging in Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar
Yes, I am aware that the live session has an Install Ubuntu icon on the desktop. Ubuntu GNOME does not. Fedora worked around this with a simple Welcome app that starts the installer or tells you where to find the installer if you want to close the Welcome app. I will be proposing that Ubuntu 17.10 install gnome-tweak-tool by default. Just because many people want desktop icons does not mean that they have to be enabled by default if we provide an easy way for them to be enabled. Because of course there are many people who don't use desktop icons. (It sounds like the Unity8 complaining may have been because it was impossible, not necessarily because of the defaults.) -- 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/1696621 Title: Desktop icons slip under the top bar after logging in Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Nicholas, does the patch come from upstream? We should backport the patch into Ubuntu's NM properly, so everyone can benefit. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in
** Bug watch added: GNOME Bug Tracker #760651 https://bugzilla.gnome.org/show_bug.cgi?id=760651 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=760651 Importance: Unknown Status: Unknown -- 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/1696621 Title: Desktop icons slip under the top bar after logging in Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
No, it's not an upstream patch. My patch can be applied directly to the current source on 17.04 obtained using 'apt-get source network-manager', so that would be network-manager 1.4.4-1ubuntu3 from http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in
** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => Medium -- 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/1696621 Title: Desktop icons slip under the top bar after logging in Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in
** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1696621 Title: Desktop icons slip under the top bar after logging in Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695928] Re: Please remove obsolete UOA packages
** Description changed: Ubuntu Online Accounts is no longer maintained. There is an alternative, GNOME Online Accounts for the GNOME desktop. Also, Unity's Online Accounts settings panel does not currently work without oxide-qt but oxide-qt will be removed from Ubuntu 17.10. Please remove these source packages and their binaries: - gnome-control-center-signon account-plugins account-plugin-fitbit account-polld pay-service qt-purchasing-opensource-src storage-provider-webdav sync-monitor ubuntuone-credentials ubuntu-push unity-china-photo-scope unity-scope-gdrive ubuntu-system-settings-online-accounts online-accounts-api storage-framework keeper mcloud ubuntu-system-settings address-book-app address-book-service buteo-sync-plugins-contacts-google camera-app dialer-app indicator-transfer indicator-transfer-buteo libertine messaging-app ubuntu-experience-tests unity-scopes-shell unity8 Other Notes --- The Shotwell suggests have been dropped in artful-proposed. Shotwell is temporarily stuck in -proposed because of an autopkgtest issue https://bugzilla.gnome.org/781802 - Kubuntu still uses the signon-ui source. - The signon-ui binary is now NBS (it was transitional pre-vivid depending on signon-ui-x11) + Kubuntu still uses signon-ui unity still recommends unity-scope-gdrive because it FTBFS https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097 See also https://code.launchpad.net/~xnox/ubuntu- seeds/unity8-removals/+merge/323615 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1695928 Title: Please remove obsolete UOA packages Status in gnome-control-center-signon package in Ubuntu: New Bug description: Ubuntu Online Accounts is no longer maintained. There is an alternative, GNOME Online Accounts for the GNOME desktop. Also, Unity's Online Accounts settings panel does not currently work without oxide-qt but oxide-qt will be removed from Ubuntu 17.10. Please remove these source packages and their binaries: - gnome-control-center-signon account-plugins account-plugin-fitbit account-polld pay-service qt-purchasing-opensource-src storage-provider-webdav sync-monitor ubuntuone-credentials ubuntu-push unity-china-photo-scope unity-scope-gdrive ubuntu-system-settings-online-accounts online-accounts-api storage-framework keeper mcloud ubuntu-system-settings address-book-app address-book-service buteo-sync-plugins-contacts-google camera-app dialer-app indicator-transfer indicator-transfer-buteo libertine messaging-app ubuntu-experience-tests unity-scopes-shell unity8 Other Notes --- The Shotwell suggests have been dropped in artful-proposed. Shotwell is temporarily stuck in -proposed because of an autopkgtest issue https://bugzilla.gnome.org/781802 Kubuntu still uses signon-ui unity still recommends unity-scope-gdrive because it FTBFS https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097 See also https://code.launchpad.net/~xnox/ubuntu- seeds/unity8-removals/+merge/323615 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
If that's the case, would you mind to upstream the patch? -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506847] Re: gnome-screenshot doesn't put the screenshot in clipboard
This happens to me running Wayland, works in X -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1506847 Title: gnome-screenshot doesn't put the screenshot in clipboard Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 14.04 and I've noticed that gnome-screenshot doesn't work as it used to a couple of weeks ago, so probably an update broke it. When I take a snapshot (Print Screen or Shift+Print Screen), I get the gnome-screenshot dialog with the options "Copy to clipboard" and "Save file". Saving file works, but copy to clipboard an pasting to another application doesn't. Copy and paste of images does work in general (e.g. by using the "Copy image" option in the browser - I can paste this image to another program), so this seems to be solely related to gnome-screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1506847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
@Giacomo On Xenial's linux 4.4, Skylake uses i915_bpo instead of i915. Please file a separate bug for this. @Robert What version was the last working linux kernel? -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687863] Re: evolution PIM does not reliably reconnect after suspend
** Description changed: - After suspend, evolution PIM will get "offline" on my desktop (My - system: ubuntu 16.10, gnome desktop) in about half of the occurencies. - Switching it "online" manually works, the machine reconnects to the web - without any trouble. + After resume from suspend, evolution PIM will remain "offline" on my + desktop (My system: ubuntu 16.10, gnome desktop) in about half of the + occurencies. Switching it "online" manually works. The machine itself + reconnects to the web without any trouble. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1687863 Title: evolution PIM does not reliably reconnect after suspend Status in evolution package in Ubuntu: New Bug description: After resume from suspend, evolution PIM will remain "offline" on my desktop (My system: ubuntu 16.10, gnome desktop) in about half of the occurencies. Switching it "online" manually works. The machine itself reconnects to the web without any trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1687863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 178758] Re: Desktop-wide setting for preferred tag encoding
** Changed in: totem Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/178758 Title: Desktop-wide setting for preferred tag encoding Status in Totem: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Binary package hint: totem Although bug #117154 is marked as fixed, the problem still exists for other mp3 files. Example included here. Description of problem: Totem/gstreamer displays ID3 tags info when playing MP3 files... But it does not autodetect correct character set of those ID3 tags nor it have any support to let user choose character set in Options dialog. File to illustrate problem: http://launchpadlibrarian.net/10535961/vidis_vidis.mp3 Audacious can be used to display id3 tag correctly: -- audacious -- Title: Vidíš, vidíš Artist: Bratři Ebenové Album: Já na tom dělám -- totem -- Title: Vidí, vidí Artist: Bratøi Ebenové Album: Já na tom dìlám Screenshots: http://launchpadlibrarian.net/10536027/screenshot-totem.png http://launchpadlibrarian.net/10536104/screenshot-audacious.png To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/178758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp