[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
Fix committed upstream in http://bazaar.launchpad.net/~apparmor- dev/apparmor/master/revision/3722. Thanks! ** Changed in: apparmor (Ubuntu) Status: New => Fix Committed ** Changed in: apparmor (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: apparmor Status: New => Fix Committed ** Changed in: apparmor Milestone: None => 2.12 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1717714 Title: @{pid} variable broken on systems with pid_max more than 6 digits Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: Confirmed Bug description: If your kernel.pid_max sysctl is set higher than the default, say at 7 digits, the @{pid} variable no longer matches all pids, causing some breakage in any profile using it. @{pid} is defined in /etc/apparmor.d/tunables: @{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]} It only covers up to 6 digits. This Ubuntu 17.04 system has: kernel.pid_max = 4194303 And is showing type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111 Which should be matched by @{PROC}/sys/vm/overcommit_memory r, in /etc/apparmor.d/abstractions/libvirt-qemu I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04 (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17) I am aware this is a non-default configuration, but I think this should work. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1717714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
** Changed in: pulseaudio (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Triaged Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+attachment/4660325/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1580394 Title: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power Status in alsa-driver package in Ubuntu: New Bug description: I have noticed that when I am on battery power on a Dell Latitude 3340 laptop with headphones plugged in , and there is no audio playing on the computer, there is a consistent static sound that comes through the headphones at a constant volume that is not affected by changing the volume level. I think it may be picking up some kind of analog loopback signal because keyboard presses and disk activity seem to influence the noise. When I plug the power cable into the laptop , the static immediately goes away. I reported this earlier to the upstream Linux Kernel bug tracker, but it seems to be fixed in any distro running a 4.4 kernel or greater that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This make me think it is not a kernel level issue and is found somewhere either in the audio settings on Ubuntu MATE or a pulseaudio bug. I cannot reproduce it on any other 16.04 distro version, but it also affects all the 14.04.4 distros as well. Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent the static. The BIOS Firmware version is up to date. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu-mate 1718 F pulseaudio /dev/snd/controlC0: ubuntu-mate 1718 F pulseaudio CasperVersion: 1.376 CurrentDesktop: MATE Date: Wed May 11 00:43:52 2016 LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727597] Re: systemd-udevd crashed with SIGABRT in __libc_open64()
*** This bug is a duplicate of bug 1715782 *** https://bugs.launchpad.net/bugs/1715782 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1715782, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1727597/+attachment/4995906/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727597/+attachment/4995909/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727597/+attachment/4995915/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727597/+attachment/4995917/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727597/+attachment/4995918/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727597/+attachment/4995919/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727597/+attachment/4995920/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715782 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727597 Title: systemd-udevd crashed with SIGABRT in __libc_open64() Status in systemd package in Ubuntu: New Bug description: This is one of those bugs that appear randomly, and not when doing anything in particular. In this specific case, I just had chrome open watching Netflix and popped up in the background. ``` dustin@bashfulrobot:~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 ``` ``` dustin@bashfulrobot:~$ sudo apt-cache policy systemd [sudo] password for dustin: systemd: Installed: 234-2ubuntu12 Candidate: 234-2ubuntu12 Version table: *** 234-2ubuntu12 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ``` I had no expectations beyond not getting the error. Other functionality had remained. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CustomUdevRuleFiles: 70-snap.gitter-desktop.rules 70-snap.core.rules 70-snap.discord.rules 70-snap.brave.rules Date: Wed Oct 25 14:00:30 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-10-20 (5 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FB002RUS ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_open64 (file=0x5653b842f0f0 "/dev/sdb", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __libc_open64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB002RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET37W(1.11):bd03/15/2016:svnLENOVO:pn20FB002RUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB002RUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FB002RUS 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/systemd/+bug/1727597/+subscriptions -- Mailing list: https://launchpad.
[Touch-packages] [Bug 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic
** Package changed: software-properties (Ubuntu) => python-apt (Ubuntu) ** Changed in: python-apt (Ubuntu) Assignee: Mike Davis (mdavi86) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1312673 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic Status in python-apt package in Ubuntu: Fix Released Bug description: lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.92.37 Candidate: 0.92.37 Version table: *** 0.92.37 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.92.37 Uname: Linux 3.14.0-999-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 25 19:27:37 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2012-09-30 (572 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 62914567 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '62914567'] SourcePackage: software-properties Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic UpgradeStatus: Upgraded to utopic on 2013-11-10 (165 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1312673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type()
** Information type changed from Private to Public ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() + gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727365 Title: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers() Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This bug is triggered for me by leaving the system inactive for a time and it happens whether the system settings is set to lock the screen or not, but I can be provoked by locking the screen. At the time when I want to reactivate the system (as I can see on the time stamp on the crash report), something happens and I loose the entire login session and am dropped at the login screen to login anew. This has lead me to believe that this has to do with re-enabling the display. The effect of this bug is that I loose *all* running programs in my session and has to start everything up again, which means that Ubuntu 17.10 is basically unusable for me. For this reason, of course depending on how many people are affected, I think this should be considered a high priority bug. This is a fresh install with no shenanigans except installing a few programs that I needed. I happy to provide any extra information is required and to any kind of testing that might be required as long as I can return to a non- modified system after test. Mandatory info: lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 apt-cache policy gnome-shell gnome-shell: Installeret: 3.26.1-0ubuntu4 Kandidat:3.26.1-0ubuntu4 Versionstabel: *** 3.26.1-0ubuntu4 500 500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 16:11:36 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['workspace-g...@mathematical.coffee.gmail.com', 'commandout...@elken.tdos.gmail.com']" b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-23 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f37ebf9cf80:push %rdx PC (0x7f37ebf9cf80) in non-executable VMA region: 0x7f37ebf99000-0x7f37ec00 rw-p None source "%rdx" ok destination "(%rsp)" (0x7fff6f7a1cb8) ok SegvReason: executing writable VMA None Signal: 11 SourcePackage: gnome-shell StacktraceTop: __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so Title: gnome-shell crashed with SIGSEGV in __bss_start() 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-shell/+bug/1727365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727580] [NEW] ubuntu-bug segfaults when trying to report a bug using the PID of the offending process
Public bug reported: Docs say ubuntu-bug $PID should work. Tried it: [leer@leer-eng: ~]$ ubuntu-bug 1392 Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Popup window gave error that this process was owned by another user (it was, the gdm user) and to run it as root or that user. Tried as root: [leer@leer-eng: ~]$ sudo ubuntu-bug 1392 Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Segmentation fault (core dumped) And that's all she wrote. Need I say more? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 22:32:13 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-27 (729 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Description changed: Docs say ubuntu-bug $PID should work. Tried it: - [leer@lgbeer-eng: ~]$ ubuntu-bug 1392 + [leer@leer-eng: ~]$ ubuntu-bug 1392 Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Popup window gave error that this process was owned by another user (it was, the gdm user) and to run it as root or that user. Tried as root: [leer@leer-eng: ~]$ sudo ubuntu-bug 1392 Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Segmentation fault (core dumped) - And that's all shw wrote. Need I say more? + And that's all she wrote. Need I say more? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 22:32:13 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-27 (729 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1727580 Title: ubuntu-bug segfaults when trying to report a bug using the PID of the offending process Status in apport package in Ubuntu: New Bug description: Docs say ubuntu-bug $PID should work. Tried it: [leer@leer-eng: ~]$ ubuntu-bug 1392 Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Popup window gave error that this process was owned by another user (it was, the gdm user) and to run it as root or that user. Tried as root: [leer@leer-eng: ~]$ sudo ubuntu-bug 1392 Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused Segmentation fault (core dumped) And that's all she wrote. Need I say more? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 22:32:13 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-27 (729 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1727580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725686] Re: Computer freezes when logging into Ubuntu 17.10 on Wayland
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725686 Title: Computer freezes when logging into Ubuntu 17.10 on Wayland Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I first installed Ubuntu 17.10, I logged into Wayland and it worked fine. There were some minor issues, but it was still functional. However, I started screencasting my computer with Ctrl- Alt-Shift-R, but my computer became very slow and I decided to shut it down. I closed all applications before shutting it down, but forgot to stop the screencast. Now, when I try to log into Ubuntu 17.10 using Wayland, the screen goes gray and my cursor is stuck in the middle of the screen. I can't move my cursor at all and the desktop never actually loads. I can still transition to other ttys, though, by using the Ctrl-Alt-(F key) commands. However, logging into Ubuntu on Xorg or Unity still works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726224] Re: wacom invisible mouse pointer in wayland
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1726224 Title: wacom invisible mouse pointer in wayland Status in gnome-shell package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet, which has touch and pen functionality. Controlling the mouse pointer through the touch functionality seems to work fine, but using the stylus produced very strange behaviour, depending the program. - With Firefox there there are two pointers - one that is moving in accordance with the stylus movements, and one stays put at the position, when the stylus movement was detected. - With Darktable the mouse pointer becomes invisible, once it's moved inside of the application window (it registers clicks though). Once the pointer is moved outside of the application window, it appears again. I'm running Ubuntu inside of a wayland session. libwacom2: 0.24-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726497] Re: nautilus crashed with SIGABRT in wl_abort()
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1726497 Title: nautilus crashed with SIGABRT in wl_abort() Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: This crash occurred when I was browsing my folders. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 08:55:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () wl_proxy_marshal_array_constructor_versioned () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 wl_proxy_marshal () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGABRT in wl_proxy_marshal_array_constructor_versioned() 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/gtk+3.0/+bug/1726497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727356] Re: Wayland does not start up
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up Status in gnome-shell package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727363] Re: Wayland dock "crash" after thumb (horizontal) scroll
** Package changed: wayland (Ubuntu) => gnome-shell-extension-ubuntu- dock (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727363 Title: Wayland dock "crash" after thumb (horizontal) scroll Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant) I don't know if this is the right place to leave this issue. The problem is very simple to reproduce if you have a Logitech MX Master mouse: if you make a horizontal scroll through the "thumb scroll wheel", the icons on the wayland dock will disappear. To display them again, you need to restart the session. If you tell me where I can pick a log, I'll be happy to provide it. Sorry for my english. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1727363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I have a theory that Bose devices are probably just noticing they've been connected in HSP mode by default and that's when they say "call from". In that case this might be fixed with bug 1720684, so keep an eye on that one. ** Tags added: bose -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
** Tags added: bose -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1
** Tags added: bose -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1716127 Title: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12,1 Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Plus the log snippet in comment #2 shows the hang is probably occurring in the kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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 Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
OK, I maintain the theory that this is a kernel regression then. When everything worked for you that was kernel 4.10, and now you're on 4.13. Plus the log snippet in comment #2 shows the hang is probably occurring in the call. Please try some older kernels, starting with 4.10... http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D The nvidia driver uses DKMS so should get automatically recompiled for each kernel you install. And in this case even an "old" kernel is pretty recent so nvidia shouldn't have any problem with them. ** Changed in: linux (Ubuntu) Status: Invalid => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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 Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727158] Re: lscpu shows incorrect instantaneous CPU MHz value
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1727158 Title: lscpu shows incorrect instantaneous CPU MHz value Status in util-linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10: lscpu has the following fields of interest to this report: Model name: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz CPU MHz: 3499.996 CPU max MHz: 5900. CPU min MHz: 1600. The CPU MHz field is incorrect: At idle it never shows down-step, and at full load, it never shows the CPU's boost frequency (which should be up to about 4.6GHz on my system). This was working correctly under Ubuntu 17.04, showing the full range between 1600 and 4600. But with Ubuntu 17.10 it remains constantly at the CPU's design spec of 3499.996. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: util-linux 2.30.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 22:00:02 2017 InstallationDate: Installed on 2017-09-01 (53 days ago) InstallationMedia: Ubuntu 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: util-linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727158] Re: lscpu shows incorrect instantaneous CPU MHz value
I can confirm this issue on 17.10. It worked fine in 16.10 from which I upgraded. Model name: Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz Stepping:7 CPU MHz: 3200.149 CPU max MHz: 4000. CPU min MHz: 1200. Meanwhile, the "i7z" utility correctly reports the current clockrate, i.e. 1200 Mhz idle and 4000 MHz under load. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1727158 Title: lscpu shows incorrect instantaneous CPU MHz value Status in util-linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10: lscpu has the following fields of interest to this report: Model name: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz CPU MHz: 3499.996 CPU max MHz: 5900. CPU min MHz: 1600. The CPU MHz field is incorrect: At idle it never shows down-step, and at full load, it never shows the CPU's boost frequency (which should be up to about 4.6GHz on my system). This was working correctly under Ubuntu 17.04, showing the full range between 1600 and 4600. But with Ubuntu 17.10 it remains constantly at the CPU's design spec of 3499.996. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: util-linux 2.30.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 22:00:02 2017 InstallationDate: Installed on 2017-09-01 (53 days ago) InstallationMedia: Ubuntu 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: util-linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727566] [NEW] extra left-behind domains break domain name rsolution
Public bug reported: This seems related to LP: #1717995 but that is marked fixed. I used my laptop at work, where I have a docking station with USB ethernet included (interface enx0050b6cf4d4a). The dhcp on the wired ethernet includes my work domain, purestorage.com. I undocked, suspended, and came home, where I have no USB ethernet (just wifi wlp4s0), and dhcp on wifi doesn't mention purestorage.com. However, I still have leftover state that stops purestorage.com names from resolving: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search lan purestorage.com dev.purestorage.com $ systemd-resolve --status Global DNS Domain: lan purestorage.com dev.purestorage.com DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.1.0.1 fda0:5173:b519::1 DNS Domain: lan Link 2 (enp0s31f6) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no It seems there are still issues around network interfaces being removed but leaving behind their DNS config. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:48:47 2017 InstallationDate: Installed on 2016-09-01 (419 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5087 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (91 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727566 Title: extra left-behind domains break domain name rsolution Status in systemd package in Ubuntu: New Bug description: This seems related to LP: #1717995 but that is marked fixed. I used my laptop at work, where I have a docking station with USB ethernet included (interface enx0050b6cf4d4a). The
[Touch-packages] [Bug 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic
aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1312673 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic Status in software-properties package in Ubuntu: Fix Released Bug description: lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.92.37 Candidate: 0.92.37 Version table: *** 0.92.37 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.92.37 Uname: Linux 3.14.0-999-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 25 19:27:37 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2012-09-30 (572 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 62914567 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '62914567'] SourcePackage: software-properties Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic UpgradeStatus: Upgraded to utopic on 2013-11-10 (165 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1312673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'
OK, I think I've followed instructions here. I built with the '#define SANDBOX_SECCOMP_FILTER_DEBUG 1' uncommented. Recalling at long last that Ubuntu is Debian (I use Red Hat/CentOS at work and get them confused), I used 'dpkg-buildpackage -rfakeroot -uc -b' to do the build; hope that's OK. I also found that I needed to comment away the four'#include' lines that follow the SANDBOX_SECCOMP_FILTER_DEBUG definition, or else I got many errors relating to conflicting structure definitions. Attached tarball 'ssd-test-20171025.tar.gz' contains 'sshd.log', the result of running 'sudo sshd -p -ddd'. It also contains an etc/ hierarchy that includes the current /etc/ssh/sshd_config and the relevant files from /etc/pam.d. I also threw in the result of 'strace -f' applied to that command, in case it helps narrow the point of failure further. I took a quick troll through the output, and I don't *think* I see it revealing more than a few bytes of a private key. Thanks for responding! I hope this stuff helps to move the walls in on the problem. ** Attachment added: "Requested files from test on 2017-10-25" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4995762/+files/sshd-test-20171025.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1690485 Title: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox' Status in openssh package in Ubuntu: New Bug description: The 'sshd' process gets 'authentication failure' and refuses to allow any login. dmesg indicates that the problem is SIGSYS on a call to 'socket' (syscall #41, signal #31). On a hunch, I decided to test whether the problem is related to 'seccomp' and changed /etc/ssh/sshd_config from the default # UsePrivilegeSeparation sandbox to the former standard value UsePrivilegeSeparation yes and logins started to work again. Obviously, I'd like to have the additional protection that sandboxing would give me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: openssh-server 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 12 21:06:20 2017 InstallationDate: Installed on 2017-04-08 (35 days ago) InstallationMedia: SourcePackage: openssh UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727562] [NEW] package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: ~$ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 ~$ apt-cache policy ntp ntp: Instalado: 1:4.2.8p4+dfsg-3ubuntu5.7 Candidato: 1:4.2.8p4+dfsg-3ubuntu5.7 Tabela de versão: *** 1:4.2.8p4+dfsg-3ubuntu5.7 500 500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.5 500 500 http://br.archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 22 03:09:46 2017 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-17 (312 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=eb654371-ee60-40e3-b2c8-78e71eeb818f ro quiet splash acpi_enforce_resources=lax vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: ntp Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2016-12-18 (311 days ago) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727562 Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 Status in ntp package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 ~$ apt-cache policy ntp ntp: Instalado: 1:4.2.8p4+dfsg-3ubuntu5.7 Candidato: 1:4.2.8p4+dfsg-3ubuntu5.7 Tabela de versão: *** 1:4.2.8p4+dfsg-3ubuntu5.7 500 500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.5 500 500 http://br.archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 22 03:09:46 2017 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-17 (312 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=eb654371-ee60-40e3-b2c8-78e71eeb818f ro quiet splash acpi_enforce_resources=lax vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: ntp Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2016-12-18 (311 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727294] Re: there is no possibility to gather information in a bug report about ubuntu-bug
Hello Aleksandr, I believe this is expected behaviour: when a GUI program is suspended, the GUI cannot respond to events. Running 'fg' or 'bg' in the shell will cause it to resume, and respond to clicks. Thanks ** Package changed: ecryptfs-utils (Ubuntu) => apport (Ubuntu) ** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1727294 Title: there is no possibility to gather information in a bug report about ubuntu-bug Status in apport package in Ubuntu: Invalid Bug description: ubuntu-bug ubuntu-bug dpkg-query: шаблону ubuntu-bug не соответствует ни один пакет Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. then you to try to select the user menu (where the sound and battarey) issue alexandr@aspire:~$ ubuntu-bug xprop dpkg-query: шаблону xprop не соответствует ни один пакет try to choose the "aport" ubuntu-bug -w Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. if you interrupt this processes the key combination of "ctrl+z" the manipulator mouse does not respond to touch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1727294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710634] Re: Incorrect directory for (lib)krb5 plugins
** Changed in: krb5 (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1710634 Title: Incorrect directory for (lib)krb5 plugins Status in krb5 package in Ubuntu: Triaged Status in krb5 package in Debian: Fix Released Bug description: The libkrb5-3 package built from the krb5 source hints at a (lib)krb5 plugin directory like this: debian/libkrb5-3.dirs.in:usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/krb5 debian/libkrb5-3.lintian-overrides:libkrb5-3: package-contains-empty-directory */plugins/krb5/ The correct (lib)krb5 plugins directory, however, is: /usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/libkrb5 This can be verified in the krb5 source: $ grep plugins/libkrb5 -r src src/lib/krb5/os/locate_kdc.c: LIBDIR "/krb5/plugins/libkrb5", src/lib/krb5/os/locate_kdc.c:static const char *objdirs[] = { LIBDIR "/krb5/plugins/libkrb5", NULL }; As well as in the built library: $ strings /usr/lib/x86_64-linux-gnu/libkrb5.so.3|grep plugins /usr/lib/x86_64-linux-gnu/krb5/plugins/authdata /usr/lib/x86_64-linux-gnu/krb5/plugins plugins /usr/lib/x86_64-linux-gnu/krb5/plugins/libkrb5 This also briefly introduced a bug in the ubuntu and debian sssd packages, which assumed .../plugins/krb5 was the correct path: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1664566 In debian it was fixed in commit e6c4e91473e75f0ddc917a24f4d561fab9900939: commit e6c4e91473e75f0ddc917a24f4d561fab9900939 Author: Timo Aaltonen Date: Fri Feb 17 11:22:12 2017 +0200 rules, common.install: Fix sssd_krb5_locator_plugin install path. (LP: #1664566) There is no immediate impact to the libkrb5-3 package itself, since MIT kerberos does not ship any libkrb5 plugin at the moment and it is an empty directory. It should be fixed, though, to avoid inducing similar bugs in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1710634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727294] [NEW] there is no possibility to gather information in a bug report about ubuntu-bug
You have been subscribed to a public bug: ubuntu-bug ubuntu-bug dpkg-query: шаблону ubuntu-bug не соответствует ни один пакет Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. then you to try to select the user menu (where the sound and battarey) issue alexandr@aspire:~$ ubuntu-bug xprop dpkg-query: шаблону xprop не соответствует ни один пакет try to choose the "aport" ubuntu-bug -w Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. if you interrupt this processes the key combination of "ctrl+z" the manipulator mouse does not respond to touch. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- there is no possibility to gather information in a bug report about ubuntu-bug https://bugs.launchpad.net/bugs/1727294 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716009] Re: problem with the sound since the latest update
why is there not any response to this bug report?! the latest updates were released just now, including linux-firmware 1.157.13, and the problem is still there even after i installed them on my computer - there is still no effect when adjusting sound volume slider from the sound menu on the menu bar and sound settings - what is going on, i thought the problem will be resolved after the new linux- firmware update?! - i haven't been able to adjust sound volume for almost two months -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716009 Title: problem with the sound since the latest update Status in alsa-driver package in Ubuntu: New Bug description: i am with an old intel chipset motherboard having an integrated realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the latest update there has had no effect when adjusting sound volume from the sound menu on the menu bar and sound settings, and no sound in counter strike 1.6 linux version, also, there has appeared an effect of a sound interruption/break (for less than a second) when switching between applications, however, i can still adjust the sound volume from gnome alsa mixer the latest update includes: snapd-login-service:amd64 libsnapd-glib1:amd64 linux-firmware:amd64 libgd3:amd64 the previous ——: libpackagekit-glib2-16:amd64 gir1.2-packagekitglib-1.0:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
Also affects me on Lubuntu 16.04. Installing IBus (sudo apt ibus) and using Preferences > Language Support to change the Keyboard input method system to IBus, followed by a system reboot, has fixed the issue (compose:ralt in Keyboard Layout Handler now functions as expected). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727291] Re: fonts-droid-fallback is missing "Provides: fonts-droid"
** Changed in: fonts-android (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1727291 Title: fonts-droid-fallback is missing "Provides: fonts-droid" Status in fonts-android package in Ubuntu: Incomplete Status in fonts-android package in Debian: New Bug description: 16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the new package Breaks the old package. However, the new package is missing "Provides: fonts-droid" which would allow existing scripts and 3rd party packages with dependency to "fonts-droid" to continue working. Unless there's some reason not to include "Provides: fonts-droid" I would request adding it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fonts-droid-fallback (not installed) ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-54-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Wed Oct 25 14:08:54 2017 InstallationDate: Installed on 2015-02-23 (975 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: fonts-android UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
@John: O.K., I think this excerpt from kern.log is what you might be looking for. ** Attachment added: "kern.log.txt" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+attachment/4995556/+files/kern.log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709135] Re: add bond primary parameter
We got hit by this as well. Some Ceph nodes lost all networking. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727301 Title: 229-4ubuntu20 added ARP option breaks existing bonding interfaces Status in systemd package in Ubuntu: Confirmed Bug description: this breaks existing configurations with bonding on upgrading from 229-4ubuntu19 to 229-4ubuntu20 on xenial as bond interfaces are now by default configured without ARP. Hence you suddenly lose network connectivity on upgrade. Very bad for a SRU. Plus adding "ARP=yes" to the Link section of a .network file does not work. Before this update, bond interfaces (specifically 802.3ad) were defaulting to ARP enabled. After the upgrade, they are created with NOARP set on the link. pre-upgrade: eth0: eth1: bond0: post-upgrade: eth0: eth1: bond0: Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575077] Re: package python-tdb 1.3.8-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tdb in Ubuntu. https://bugs.launchpad.net/bugs/1575077 Title: package python-tdb 1.3.8-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tdb package in Ubuntu: Confirmed Bug description: Upgraded from 15.10 Gnome ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-tdb 1.3.8-2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 19:26:31 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-14 (347 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: tdb Title: package python-tdb 1.3.8-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tdb/+bug/1575077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727291] Re: fonts-droid-fallback is missing "Provides: fonts-droid"
Thanks for your report! Hmm.. It would be a bit late for this kind of change in Xenial, wouldn't it? I added a Debian bug from March 2016 with a similar request (transitional package), but that bug hasn't been fixed. Which packages and scripts *depending* on fonts-droid do you have in mind? (Can't help to think that they should have been changed by now...) ** Changed in: fonts-android (Ubuntu) Status: New => Incomplete ** Bug watch added: Debian Bug tracker #816911 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816911 ** Also affects: fonts-android (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816911 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1727291 Title: fonts-droid-fallback is missing "Provides: fonts-droid" Status in fonts-android package in Ubuntu: Incomplete Status in fonts-android package in Debian: Unknown Bug description: 16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the new package Breaks the old package. However, the new package is missing "Provides: fonts-droid" which would allow existing scripts and 3rd party packages with dependency to "fonts-droid" to continue working. Unless there's some reason not to include "Provides: fonts-droid" I would request adding it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fonts-droid-fallback (not installed) ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-54-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Wed Oct 25 14:08:54 2017 InstallationDate: Installed on 2015-02-23 (975 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: fonts-android UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Hi Daniel, thank you for helping out. I can report that the issues are back today (After 2 days of working). This time is crazy, it breaks more often. I had to reinstall the whole 17.10 and of course it happens but less often (Like the original bug report). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: New Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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 Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files
Staying on gnome-control-center bluetooth pane while receiving file works too. When so dbus session show it registers itself to obexd RegisterAgent with '/org/gnome/share/agent'. As soon as we exit the gnome-control-center bluetooth pane it unregister itself and stop advertising itself as org.bluez.obex.Agent1 on the dbus session bus. obexd thus fails as no agent is available. part 2 is https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1645631 though me might want to keep it there as there are 4 different issues in this previous report. My test shown that when I was with an agent the file goes temporarily to $HOME/.cache/obexd/ then to the Downloads folder. So I do not confirm the bug reports 1645631 findings. This refutes the root folder is not correct issue (dbus monitor shows the same cache dir with or without an agent). gnome-file-share-properties is still available in gnome-user-share on ubuntu. As you shown it registers itself and stays available to the obex server obexd. So it is a correct workaround. But it might go away like it did in debian. A fix upstream is more than wanted. Mostly an agent that runs session wide not gnome-control-center a bluetooth pane that is never active except when pairing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1694455 Title: Bluetooth: Cannot receive files Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: # Use case Ubuntu 17.04, quite fresh installation, updated. Bluetooth file transmission I want to send files to my smartphone, and receive files sent by my smartphone via bluetooth. I pair both devices, initiate file transfer from one of the devices, and the other device asks me what to do. # Problems This is a mix from usability and technical issues. 1. OBEX disabled (bug 1645631) The bluetooth file transmission service OBEX was not started. I started and enabled OBEX: `systemctl --user start obex` `systemctl --user enable obex` ``` Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service... Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 ``` 2. OBEX silently fails (this bug) After having OBEX enabled, I was able to transmit files from laptop to smartphone, yet I could not receive files on the laptop. In the system log, you could see that OBEX fails (please note `FORBIDDEN`): ``` Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected ``` I did not receive a popup notification asking me to receive the file or not. In the file sharing preferences `gnome-file-share-properties`, there is a setting to automatically receive files via bluetooth. With this box checked, you're finally able to receive files from your smartphone. Successful log for comparison: ``` Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected ``` # Expected behaviour OBEX is started by default to handle bluetooth file transfers. If no automatic file receipt is configured, a popup notification asks me if I want to receive the file or not. If this is not possible, there should be a notification pointing the user to the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725060] Re: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1725060 Title: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1 Status in wpa package in Ubuntu: Confirmed Bug description: After some update, my network is a bit erratic and I found it producing messages like this in journald every second: Oct 20 07:57:23 maldita wpa_supplicant[1519]: wlp2s0: CTRL-EVENT-SCAN- FAILED ret=-16 retry=1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: wpasupplicant 2.4-0ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:59:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-25 (1789 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1725060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC
** Changed in: gcc Status: Unknown => Fix Released ** Changed in: gcc Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Fix Released Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Status in gcc-5 source package in Xenial: Fix Released Status in binutils source package in Yakkety: Won't Fix Status in gcc-5 source package in Yakkety: Won't Fix Status in gcc-6 source package in Yakkety: Won't Fix Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709135] Re: add bond primary parameter
Sounds like maybe that kernel defaults to noarp and we'd want systemd to retain previous behavior? Do you have any sysctl configuration that forces arp state? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724933] Re: I can't adjust display brightness
This appears to be quite an old issue with Optimus graphics. For me the workaround was to pass specific kernel parameters at boot time to inhibit acpi control of the backlight but allow intel_backlight control I followed the instructions at https://nisheetlall.wordpress.com/2016/07/12/solved-brightness-fix-in-linux-for-optimus-laptops/ which worked first time for me. Your mileage may of course vary - it happens that I have exactly the same Lenovo Z570 laptop as the author of those instructions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1724933 Title: I can't adjust display brightness Status in xorg package in Ubuntu: Confirmed Bug description: I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I can't adjust display brightness. when I press F2|F3 keys icon brightness appears, the controller moves but the brightness doesn't change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 22:14:51 2017 DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3388] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-06-18 (123 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3388 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124471610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727462] Re: totem crashed with SIGSEGV
*** This bug is a duplicate of bug 1681210 *** https://bugs.launchpad.net/bugs/1681210 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1681210, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1727462/+attachment/4995133/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727462/+attachment/4995135/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727462/+attachment/4995140/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727462/+attachment/4995141/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727462/+attachment/4995142/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727462/+attachment/4995143/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727462/+attachment/4995144/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1681210 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1727462 Title: totem crashed with SIGSEGV Status in gstreamer1.0 package in Ubuntu: New Bug description: Repeated issue with Totem not playing video (audio tracks still audible) whilst using Nvidia proprietary drivers under Ubuntu 17.10. X.Org Nouveau drivers appear to work properly. Crash occurred after switching back to latest Nvidia drivers for testing purposes. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.3-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 18:36:32 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-08-03 (82 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f1d66284b59:mov(%rsi),%rsi PC (0x7f1d66284b59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: totem crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1727462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727470] [NEW] [RFE] Automatically update the Ubuntu version strings
Public bug reported: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: l10n ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings Status in Ubuntu Translations: New Status in python-apt package in Ubuntu: New Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1727174 Title: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a+134000] Status in ibus package in Ubuntu: Incomplete Bug description: uname -a Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch Distributor ID: Ubuntu Description: Ubuntu 17.10 Release: 17.10 Codename: artful read-config SCHEMA: org.freedesktop.ibus.general dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul'] use-system-keyboard-layout: true embed-preedit-text: true enable-by-default: false use-global-engine: false use-xmodmap: true switcher-delay-time: 400 version: '1.5.14' engines-order: ['libpinyin'] preload-engines: ['libpinyin', 'xkb:us::eng'] xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 'jp(kana)', 'mal', 'mkd', 'ru', 'ua'] SCHEMA: org.freedesktop.ibus.general.hotkey next-engine: ['Alt+Shift_L'] disable-unconditional: @as [] enable-unconditional: @as [] trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 'Hangul', 'Alt+Release+Alt_R'] previous-engine: @as [] prev-engine: @as [] next-engine-in-menu: ['Alt+Shift_L'] triggers: ['space'] SCHEMA: org.freedesktop.ibus.panel x: -1 property-icon-delay-time: 500 y: -1 lookup-table-orientation: 1 show: 2 xkb-icon-rgba: '#415099' auto-hide-timeout: 1 show-im-name: false follow-input-cursor-when-always-shown: false custom-font: 'Sans 10' show-icon-on-systray: true use-custom-font: false ibus engine xkb:us::eng ps -ef|grep ibus gdm 1969 1647 0 12:42 tty1 00:00:00 ibus-daemon --xim --panel disable gdm 1972 1969 0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf gdm 1975 1 0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 --kill-daemon gdm 2046 1969 0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-engine-simple hdzhong 2516 2433 0 12:42 tty2 00:00:02 ibus-daemon --xim --panel disable hdzhong 3966 2516 0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf hdzhong 3968 1 0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 --kill-daemon hdzhong 3984 2516 0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-engine-simple hdzhong 4198 3939 0 12:58 pts/100:00:00 grep --color=auto ibus dpkg: ii ibus 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - core ii ibus-anthy 1.5.9-2 amd64anthy engine for IBus ii ibus-clutter:amd64 0.0+git20090728.a936bacf-5.1 amd64ibus input method framework for clutter ii ibus-gtk:amd64 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - GTK+2 support ii ibus-gtk3:amd64 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - GTK+3 support ii ibus-libpinyin 1.7.3-2 amd64 Intelligent Pinyin engine based on libpinyin for IBus ii ibus-qt4 1.3.3-1 amd64 qt-immodule for ibus (QT4) (plugin) ii ibus-sunpinyin 2.0.3-5build3amd64 sunpinyin engine for ibus ii ibus-table 1.9.14-3 all table engine for IBus ii ibus-table-wubi 1.8.2-2 all ibus-table input method: Wubi ii ibus-wayland 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - Wayland support ii libibus-1.0-5:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus - shared library ii libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus - development file ii libibus-qt1 1.3.3-1
[Touch-packages] [Bug 1727449] Re: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()
*** This bug is a duplicate of bug 1664886 *** https://bugs.launchpad.net/bugs/1664886 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1664886, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1727449/+attachment/4995006/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727449/+attachment/4995009/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727449/+attachment/4995017/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727449/+attachment/4995019/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727449/+attachment/4995020/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727449/+attachment/4995021/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727449/+attachment/4995023/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1664886 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727449 Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate() Status in systemd package in Ubuntu: New Bug description: just started up and logged in ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 19:24:58 2017 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2016-12-10 (318 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=a8d6579d-c193-4fff-92fe-f6fa638cd416 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fbc64f68baa:movzbl 0x2f(%rdi),%r8d PC (0x7fbc64f68baa) ok source "0x2f(%rdi)" (0x47f00750134) not located in a known VMA region (needed readable region)! destination "%r8d" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: systemd StacktraceTop: ?? () from /lib/systemd/libsystemd-shared-234.so internal_hashmap_iterate () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate() UpgradeStatus: Upgraded to artful on 2017-10-21 (4 days ago) UserGroups: dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd11/14/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
@Doug, can you attach your breakage? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727447] Re: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c li
** Description changed: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. - The PID mentioned is connected to the steam client running. has as well - been reported here - https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just - ubuntu-bug did not want to send in a proper bug report on this package. + The PID mentioned is connected to the steam client running. has as well been reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just ubuntu-bug did not want to send in a proper bug report on this package. + (marked the bug report the link goes to as a duplicate of this bug) IMHO this is critical, even if SSDs are more stable as people think, this produces unnecessary write and delete cycles ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1727447 Title: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Status in dbus package in Ubuntu: New Status in steam package in Ubuntu: New Bug description: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. The PID mentioned is connected to the steam client running. has as well been reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just ubuntu-bug did not want to send in a proper bug report on this package. (marked the bug report the link goes to as a duplicate of this bug) IMHO this is critical, even if SSDs are more stable as people think, this produces unnecessary write and delete cycles ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1727447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727447] Re: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c li
** Also affects: steam (Ubuntu) Importance: Undecided Status: New ** Description changed: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. - The PID mentioned is connected to the steam client running. + The PID mentioned is connected to the steam client running. has as well + been reported here + https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just + ubuntu-bug did not want to send in a proper bug report on this package. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. The PID mentioned is connected to the steam client running. has as well been reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just ubuntu-bug did not want to send in a proper bug report on this package. + + IMHO this is critical, even if SSDs are more stable as people think, + this produces unnecessary write and delete cycles ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1727447 Title: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Status in dbus package in Ubuntu: New Status in steam package in Ubuntu: New Bug description: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. The PID mentioned is connected to the steam client running. has as well been reported here https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1726083 just ubuntu-bug did not want to send in a proper bug report on this package. (marked the bug report the link goes to as a duplicate of this bug) IMHO this is critical, even if SSDs are more stable as people think, this produces unnecessary write and delete cycles ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1727447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I'm not sure about split-horizon DNS, frankly I think that is a different bug entirely. However, I have had no problems with DNS leaks over my VPN connections whatsoever on Ubuntu 17.10. The bugfix I personally requested from the NM-devs and backported to Ubuntu 17.04 (running NetworkManager v1.4.x) was effectively just patching the negative dns-priority bug related to systemd-resolved. From 'man nm- settings': "Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used." This means that DNS servers configured for the non-VPN connection will be 'unseated' and ONLY the VPN-configured DNS servers are used. Ubuntu 17.10 is running NetworkManager v1.8.4, so Thomas Haller's merged bugfix is present and working. You MUST use the command: 'sudo nmcli connection modify ipv4.dns-priority -42' or similar to actually set negative DNS priority for the VPN connection. Restart the network manager with 'sudo service network-manager restart', then connect to the VPN. Examine the output of 'systemd-resolved --status' and use the 'Extended' test on dnsleaktest.com to verify that you are not leaking DNS queries. I use openvpn, but setting negative dns priority should work for preventing DNS leaks over regular VPN connections of all kinds as a kind of 'catch-all'. Auto-connecting to openvpn through the GUI is a little troublesome in 17.10, but this 'fix' worked for me: https://askubuntu.com/questions/967408/how-to-automatically-connect-to-vpn-in-ubuntu-17-10/967415#967415 -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report 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/network-manager/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727447] [NEW] arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c
Public bug reported: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. The PID mentioned is connected to the steam client running. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1727447 Title: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Status in dbus package in Ubuntu: New Bug description: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. The PID mentioned is connected to the steam client running. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1727447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727447] Re: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c li
This is generated every second: Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_ref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2688. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_ref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2688. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_ref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2688. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: process 4451: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2824. Oct 25 19:19:20 NEXUS-ONE org.gnome.Shell.desktop[1659]: This is normally a bug in some application using the D-Bus library. ** Description changed: Maybe related to my bug report on the steam package, my hard guess is that the missing system tray is causing this. Sadly enough it really spams the syslog in a way which makes it unusable. Have to truncate it every day from a size of around 60MB down to 0. + + The PID mentioned is connected to the steam client running. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dbus 1.10.22-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 25 19:19:54 2017 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification be
[Touch-packages] [Bug 1727356] Re: Wayland does not start up
Thanks for the help, @Brian. I thought about the package 'wayland', too, but trying to report a bug against it came out like this: $ ubuntu-bug wayland dpkg-query: no packages found matching wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up Status in wayland package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726340] Re: Please add 'dkms' to the dependency list
Please give a detailed test case for why dkms needs to be pre-installed. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726340 Title: Please add 'dkms' to the dependency list Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - appimage not installable (miss gconf-service) - ... and finally have glanced at missing 'important' packages, like 'dkms, tweaks, dconf, gconf-service' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727356] Re: Wayland does not start up
> It seems that your bug report is not filed about a specific source package See, Mr. Bot, if I'd knew the package, I'd report the bug not here, but upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up Status in wayland package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727356] Re: Wayland does not start up
** Package changed: ubuntu => wayland (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up Status in wayland package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
I had the same problem with a Dell Inspiron 7720 and a Lenovo 710S (both booting the same external SSD with Kubuntu 16.04) - so annoying! It was solved with #32, so easily! Many kudos! I just can't believe this solution is yet to be included in all distros if it works so well! Stupid bugs like this give Linux a bad name for no good reason! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks 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: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
I don't know if my issue is related to this or the few others I've seen, so I pre-apologize if this should be moved elsewhere or even if it's not relevant in this context. I'm far from an expert in DNS . . . My experience was that after upgrading to 16.10 (or higher: it happens in 17.10, too, and I imagine it will in 18.04). DNS lookup for internal sites would fail when I was connected to an openconnect VPN. In 16.04, my workaround was to comment out dnsmasq in NetworkManager.conf, but in 16.10, 17.04, and 18.04, this option no longer appeared. Also, I additionally had to comment out a reference to a local host in /etc/resolv.conf, which was added below the VPN-only nameservers, which in my case were sufficient. Recently, I tried Fedora 25 and was surprised to see the same issue -- this suggests it's not an Ubuntu-specific problem, unless Canonical is providing some libs that Fedora is using, I don't know. I found this workaround for my particular case while again searching in a Fedora context for a workaround: https://www.freedesktop.org/software/systemd/man/nss-resolve.html TL;DR: I added "resolve [!UNAVAIL=return]" to the hosts line in /etc/nsswitch.conf right before any entry that has "dns" in it. This worked for me in Fedora and Ubuntu both. (Note that in the latest Arch release, this was not an issue for me.) I'm hoping that this comment will prove helpful to anyone like me who might be searching in vain for a workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source
[Touch-packages] [Bug 1727356] [NEW] Wayland does not start up
You have been subscribed to a public bug: $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment wayland -- Wayland does not start up https://bugs.launchpad.net/bugs/1727356 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708309] Re: Online accounts dialog can be crashed easily by choosing two options
Possible duplicate of LP: #1720400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1708309 Title: Online accounts dialog can be crashed easily by choosing two options Status in gnome-online-accounts package in Ubuntu: New Bug description: Up to date Artful installation. Open online accounts and choose one of the options available, such as Google. Wait for the next dialog to finish and then press escape to close it. Choose a different option. Online accounts reliably crashes. https://youtu.be/Be2HPkcafp8 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 3 00:07:52 2017 InstallationDate: Installed on 2017-08-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
** Description changed: Impact == On artful every time gnome-control-center (goa panel) is used to add a google account, gnome-control-center crashes. This is one of the most reported crashes after the release. Test Case = - Open gnome-control-center - Go to online-account panel - Add a Google online account. - gnome-control-center should not crash while adding a google online account. Regression Potential === - This is a minimal patch approved upsteam but not yet commited. Check if closing a gtk window/dialog creates no artifacts both on xorg and on wayland. + This is a minimal patch applied upstream: + https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22&id=1c3aff510 + + Check if closing a gtk window/dialog creates no artifacts both on xorg + and on wayland. Original Bug Report === The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render Status in GTK+: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Bug description: Impact == On artful every time gnome-control-center (goa panel) is used to add a google account, gnome-control-center crashes. This is one of the most reported crashes after the release. Test Case = - Open gnome-control-center - Go to online-account panel - Add a Google online account. - gnome-control-center should not crash while adding a google online account. Regression Potential === This is a minimal patch applied upstream: https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22&id=1c3aff510 Check if closing a gtk window/dialog creates no artifacts both on xorg and on wayland. Original Bug Report === The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1720400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726647] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1726647 Title: crash reports still sent to LP on artful Status in apport package in Ubuntu: Fix Committed Status in apport source package in Artful: Fix Released Bug description: /etc/apport/crashdb.conf was not modified to stop sending crash reports to Launchpad for Ubuntu 17.10, since it was released they should only be going to errors.ubuntu.com. The problem_types field needs to change to ['Bug', 'Package']. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 17:43:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1726647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726647] Re: crash reports still sent to LP on artful
This bug was fixed in the package apport - 2.20.7-0ubuntu3.1 --- apport (2.20.7-0ubuntu3.1) artful; urgency=medium * etc/apport/crashdb.conf: Disable Launchpad crash reports for 17.10 release. (LP: #1726647) -- Brian Murray Tue, 24 Oct 2017 08:22:21 -0700 ** Changed in: apport (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1726647 Title: crash reports still sent to LP on artful Status in apport package in Ubuntu: Fix Committed Status in apport source package in Artful: Fix Released Bug description: /etc/apport/crashdb.conf was not modified to stop sending crash reports to Launchpad for Ubuntu 17.10, since it was released they should only be going to errors.ubuntu.com. The problem_types field needs to change to ['Bug', 'Package']. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 17:43:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1726647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726340] Re: Please add 'dkms' to the dependency list
and gradio: third party apps not listed into the menu (ppa:nichrotis/misc) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726340 Title: Please add 'dkms' to the dependency list Status in ubuntu-meta package in Ubuntu: New Bug description: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - appimage not installable (miss gconf-service) - ... and finally have glanced at missing 'important' packages, like 'dkms, tweaks, dconf, gconf-service' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726340] Re: Please add 'dkms' to the dependency list
dkms: graphic driver ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726340 Title: Please add 'dkms' to the dependency list Status in ubuntu-meta package in Ubuntu: New Bug description: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - appimage not installable (miss gconf-service) - ... and finally have glanced at missing 'important' packages, like 'dkms, tweaks, dconf, gconf-service' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1716127 Title: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12,1 Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1716127 Title: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12,1 Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
As a matter of fact, I just checked the bug happens with scilab, available in universe. Scilab returns some interesting debug info in the standard output, which O copy in the attached text file. NEW INFO. I didn't see before that matlab was generating a crash log for this. This log confirms that the error comes from java: "Assertion in void {anonymous}::mwJavaAbort() at javainit.cpp line 1411: Fatal Java Exception. See Java Crash Report for details." The java crash report gives the following: Operating System: Linux 4.10.0-37-generic #41-Ubuntu SMP Fri Oct 6 20:20:37 UTC 2017 x86_64 Processor ID: x86 Family 6 Model 60 Stepping 3, GenuineIntel Host Name: FATAL ERROR in native method: Nativewindow X11 IOError: Display 0x7fb2cb9e5210 (localhost:10.0): Resource temporarily unavailable at sun.awt.X11.XlibWrapper.XEventsQueued(Native Method) at sun.awt.X11.XToolkit.run(Unknown Source) at sun.awt.X11.XToolkit.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Which says that X11 is at fault. ** Attachment added: "scilab debugging information" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1726595/+attachment/4994791/+files/scilabdebug.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1726595 Title: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 Status in openssh package in Ubuntu: Incomplete Bug description: OBSERVED BEHAVIOR: Matlab stays in busy state when using some functions like "plot" or even "exit", while executing through a ssh tunnel with X11 forwarding. REPRODUCE THE BUG: You need matlab (my version is R2017a) to reproduce the bug. I suspect any version >= 2014b would reproduce the bug (HG2 framework), and maybe any version. 1. Connect to self (or from other machine) with X forwarding: $ ssh -X user@localhost 2. Launch matlab $ matlab & 3. Plot something >> plot(1,1) ADDITIONAL INFORMATION - Normal behavior would be appearance of a new window and a single point at position (1,1). - No ressources seem to be used. - Opening a figure alone is possible. (>> figure). Opening other windows from the graphical user interface is possible - Opening Matlab without the java machine seems to work, but matlab relies heavily on java. At least "exit" which doesn't work with java, works without java. - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything. - This used to work perfectly for as long as I have been using Ubuntu (since 2012). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: openssh-client 1:7.5p1-10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 23 17:44:23 2017 ExecutablePath: /usr/bin/ssh InstallationDate: Installed on 2017-08-25 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) modified.conffile..etc.ssh.ssh_config: [modified] mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1726595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726340] Re: Please add 'dkms' to the dependency list
Why do you need dkms installed? gconf has been deprecated for years and is intentionally not installed by default (and would be a separate issue any way). ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726340 Title: Please add 'dkms' to the dependency list Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - appimage not installable (miss gconf-service) - ... and finally have glanced at missing 'important' packages, like 'dkms, tweaks, dconf, gconf-service' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'
And the exact change I want is to uncomment the "#define SANDBOX_SECCOMP_FILTER_DEBUG 1" line in sandbox-seccomp-filter.c; but please read the block comment above that line first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1690485 Title: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox' Status in openssh package in Ubuntu: New Bug description: The 'sshd' process gets 'authentication failure' and refuses to allow any login. dmesg indicates that the problem is SIGSYS on a call to 'socket' (syscall #41, signal #31). On a hunch, I decided to test whether the problem is related to 'seccomp' and changed /etc/ssh/sshd_config from the default # UsePrivilegeSeparation sandbox to the former standard value UsePrivilegeSeparation yes and logins started to work again. Obviously, I'd like to have the additional protection that sandboxing would give me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: openssh-server 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 12 21:06:20 2017 InstallationDate: Installed on 2017-04-08 (35 days ago) InstallationMedia: SourcePackage: openssh UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'
This issue was never previously closed, only marked Incomplete (which is an open state). While it's possible to do a normal package build to get things configured exactly the way we do, I don't think that's necessary here. I suggest: * git clone https://anonscm.debian.org/git/pkg-ssh/openssh.git * cd openssh * sudo apt build-dep ./ * make the change I suggested in comment #2 * ./configure --sysconfdir=/etc/ssh --libexecdir=/usr/lib/openssh --with-privsep-path=/run/sshd --with-pid-dir=/run --with-pam * make Don't install the result. Instead, run "sudo `pwd`/sshd -p -ddd" (where is some free port on your system) and try "ssh -oStrictHostKeyChecking=no -p localhost". That should be close enough for this purpose, and if it isn't then we can refine from there. Also, could you attach your PAM configuration (/etc/pam.d/sshd plus any files mentioned in @include lines there)? The strace you attached is unfortunately not very useful. What we need to find out here is what bit of code is making the offending socket call, which is going to require some context around it: that's usually best achieved by not limiting the set of syscalls traced by strace. Unfortunately that also means that your private host keys will show up in the strace, so if you do that then you need to be careful to redact anything like that from the output! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1690485 Title: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox' Status in openssh package in Ubuntu: New Bug description: The 'sshd' process gets 'authentication failure' and refuses to allow any login. dmesg indicates that the problem is SIGSYS on a call to 'socket' (syscall #41, signal #31). On a hunch, I decided to test whether the problem is related to 'seccomp' and changed /etc/ssh/sshd_config from the default # UsePrivilegeSeparation sandbox to the former standard value UsePrivilegeSeparation yes and logins started to work again. Obviously, I'd like to have the additional protection that sandboxing would give me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: openssh-server 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 12 21:06:20 2017 InstallationDate: Installed on 2017-04-08 (35 days ago) InstallationMedia: SourcePackage: openssh UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: Confirmed Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in pacemaker source package in Xenial: Fix Released Status in init-system-helpers source package in Zesty: Confirmed Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: Confirmed Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: Confirmed Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu Zesty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: Confirmed Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in pacemaker source package in Xenial: Fix Released Status in init-system-helpers source package in Zesty: Confirmed Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: Confirmed Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: Confirmed Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: Confirmed Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in pacemaker source package in Xenial: Fix Released Status in init-system-helpers source package in Zesty: Confirmed Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: Confirmed Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: Confirmed Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: init-system-helpers (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: Confirmed Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in pacemaker source package in Xenial: Fix Released Status in init-system-helpers source package in Zesty: Confirmed Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: Confirmed Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: Confirmed Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727401] [NEW] Corruption on windowed 3D apps running on dGPU (Intel/AMD)
Public bug reported: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in mesa package in Ubuntu: New Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
I did a fresh install of artful on a shuttle SZ170 with the following ethernet adapters according to `lshw`: *-network description: Ethernet interface product: I211 Gigabit Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 03 serial: 80:ee:73:c8:ec:1a size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.4.0-k duplex=full firmware=0. 6-1 ip=192.168.0.14 latency=0 link=yes multicast=yes port=twisted and *-network description: Ethernet interface product: Ethernet Connection (2) I219-LM vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 31 serial: 80:ee:73:c8:ec:1b size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.8-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:126 memory:df20-df21 I have dhclient and bind9 installed: root@atlantis:~# dhclient --version isc-dhclient-4.3.5 root@atlantis:~# dpkg --list|grep -i dhc ii dnsmasq-base 2.78-1 amd64Small caching DNS proxy and DHCP/TFTP server ii isc-dhcp-client4.3.5-3ubuntu2 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common4.3.5-3ubuntu2 amd64common manpages relevant to all of the isc-dhcp packages root@atlantis:~# dpkg --list|grep -i bind9 ii bind9-host 1:9.10.3.dfsg.P4-12.6ubuntu1 amd64Version of 'host' bundled with BIND 9.X ii libbind9-140:amd64 1:9.10.3.dfsg.P4-12.6ubuntu1 amd64BIND9 Shared Library used by BIND I've disabled the second ethernet adapter. Periodically `enp3s0` looses its IP address which it got via dhcp from my cable router. I think its related to this bug. I understand the basics of dhcp (I can run some commands), so I don't know the next steps to continue the diagnosis. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in bind9 package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in bind9 source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic
** Summary changed: - software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic + software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1312673 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic Status in software-properties package in Ubuntu: Fix Released Bug description: lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.92.37 Candidate: 0.92.37 Version table: *** 0.92.37 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.92.37 Uname: Linux 3.14.0-999-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 25 19:27:37 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2012-09-30 (572 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 62914567 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '62914567'] SourcePackage: software-properties Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic UpgradeStatus: Upgraded to utopic on 2013-11-10 (165 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1312673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706292] Re: [i915_bpo] Move KBL pci-id 5917 to correct group
while this is being fixed upstream, it's not a bug worth tracking as it didn't fix the upstream corruption issue, which needed a patch to mesa ** Changed in: mesa (Ubuntu Xenial) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1706292 Title: [i915_bpo] Move KBL pci-id 5917 to correct group Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in mesa source package in Xenial: Invalid Bug description: KBL 5917 is in the wrong group, needs to be GT2 but it's currently marked as GT1 which causes some issues when trying to output using a dGPU as render slave. There might be some other hidden issues but this is all we've seen so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718022] Re: RM: obsolete product
** Changed in: telepathy-ofono (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1718022 Title: RM: obsolete product Status in telepathy-ofono package in Ubuntu: Triaged Bug description: telepathy-ofono was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:telepathy-ofono No reverse dependencies found $ reverse-depends -b src:telepathy-ofono No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1718022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630839] Re: Request for applying a patch to support OpenVSwitch in hostapd
Please submit the patch upstream and have it merged there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1630839 Title: Request for applying a patch to support OpenVSwitch in hostapd Status in wpa package in Ubuntu: New Bug description: Hello Devs, I'm requesting the patch https://github.com/helmut- jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources with the attached patch and worked well with ath9k_htc + OpenVSwitch from Ubuntu 16.04. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: hostapd 1:2.4-0ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 5 23:40:38 2016 InstallationDate: Installed on 2016-01-14 (266 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: wpa UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago) modified.conffile..etc.default.hostapd: [modified] mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1630839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713710] Re: RM: obsolete product
** Changed in: click-apparmor (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1713710 Title: RM: obsolete product Status in click-apparmor package in Ubuntu: Triaged Bug description: click-apparmor was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:click-apparmor No reverse dependencies found $ reverse-depends -b src:click-apparmor No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1713710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289047] Re: [Trusty] hostapd package is broken
You can't have the same device managed by both hostapd and network- manager. ** Changed in: wpa (Ubuntu) Status: Triaged => Invalid ** Changed in: hundredpapercuts Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in One Hundred Papercuts: Invalid Status in wpa package in Ubuntu: Invalid Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. WORKAROUND: For this to persist through reboots, execute the following in a terminal: sudo nano /etc/NetworkManager/NetworkManager.conf Add the following entry where the x's are replaced with your WiFi MAC address, save, and then reboot: [keyfile] unmanaged-devices=mac:xx:xx:xx:xx:xx:xx ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1289047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364104] Re: wpasupplicant is haaving bug wifi connected but no web connectivity
** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1364104 Title: wpasupplicant is haaving bug wifi connected but no web connectivity Status in wpa package in Ubuntu: Incomplete Bug description: I have ASUS NE pce-n5 card installed. The net gets connected Active connection information is ok, but there is no net connectivity. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 1 17:27:00 2014 InstallationDate: Installed on 2014-05-02 (122 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1364104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646364] Re: fsprotect fails to install on 16.04 server
Today again stumbled over this problem after initramfs-tools had an upgrade and nvidia dkms driver wanted to be configured. I have to apply the mentioned fix every time again since Xenial was released. This is annoying: can some one backport the mentioned fix from 0.122 ??? ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1646364 Title: fsprotect fails to install on 16.04 server Status in fsprotect package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After an apt-get install on a clean 16.04 server install, fsprotect fails like so: (This is from the second try, but it is exactly the same) user@computer:~$ sudo apt-get install fsprotect [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done fsprotect is already the newest version (1.0.6). 0 to upgrade, 0 to newly install, 0 to remove and 9 not to upgrade. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.5) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.5) ... update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic cp: failed to access '/var/tmp/mkinitramfs_ewwYu8//bin/touch': Too many levels of symbolic links E: /usr/share/initramfs-tools/hooks/fsprotect failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) user@computer:~$ If I comment out the last line of /usr/share/initramfs-tools/hooks/fsprotect #copy_exec /usr/bin/touch "/bin" This will happen user@computer:~$sudo apt-get install fsprotect Reading package lists... Done Building dependency tree Reading state information... Done fsprotect is already the newest version (1.0.6). 0 to upgrade, 0 to newly install, 0 to remove and 9 not to upgrade. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.5) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.5) ... update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. user@computer:~$ I modified /etc/default/grub to make fsprotect active "fsprotect=1G" Reboot, and fixed!!! uname -a: Linux computer 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd: Description:Ubuntu 16.04.1 LTS Release:16.04 apt-cache policy fsprotect: fsprotect: Installed: 1.0.6 Candidate: 1.0.6 Version table: *** 1.0.6 500 500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status ubuntu-bug report: ProblemType: Bug ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 1 16:11:14 2016 Dependencies: adduser 3.113+nmu3ubuntu4 apt 1.2.15 apt-utils 1.2.15 busybox-initramfs 1:1.22.0-15ubuntu1 coreutils 8.25-2ubuntu2 cpio 2.11+dfsg-5ubuntu1 debconf 1.5.58ubuntu1 debconf-i18n 1.5.58ubuntu1 debianutils 4.7 dpkg 1.18.4ubuntu1.1 e2fslibs 1.42.13-1ubuntu1 e2fsprogs 1.42.13-1ubuntu1 gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 gnupg 1.4.20-1ubuntu3.1 gpgv 1.4.20-1ubuntu3.1 init-system-helpers 1.29ubuntu3 initramfs-tools 0.122ubuntu8.5 initramfs-tools-bin 0.122ubuntu8.5 initramfs-tools-core 0.122ubuntu8.5 initscripts 2.88dsf-59.3ubuntu2 insserv 1.14.0-5ubuntu3 klibc-utils 2.0.4-8ubuntu1.16.04.2 kmod 22-1ubuntu4 libacl1 2.2.52-3 libapt-inst2.0 1.2.15 libapt-pkg5.0 1.2.15 libattr1 1:2.4.47-2 libaudit-common 1:2.4.5-1ubuntu2 libaudit1 1:2.4.5-1ubuntu2 libblkid1 2.27.1-6ubuntu3.1 libbz2-1.0 1.0.6-8 libc6 2.23-0ubuntu4 libcomerr2 1.42.13-1ubuntu1 libdb5.3 5.3.28-11 libfdisk1 2.27.1-6ubuntu3.1 libgcc1 1:6.0.1-0ubuntu1 libgcrypt20 1.6.5-2ubuntu0.2 libgpg-error0 1.21-2ubuntu1 libgpm2 1.20.4-6.1 libklibc 2.0.4-8ubuntu1.16.04
[Touch-packages] [Bug 1718027] Re: RM: obsolete product
** Changed in: libusermetrics (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1718027 Title: RM: obsolete product Status in libusermetrics package in Ubuntu: Triaged Bug description: libusermetrics was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:libusermetrics No reverse dependencies found $ reverse-depends -b src:libusermetrics No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1718027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727390] [NEW] New bugfix release 17.2.3
Public bug reported: [Impact] A new upstream bugfix release is available. FILL [Test case] [Regression potential] ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Artful) Importance: Undecided Status: New ** Summary changed: - New bugfix release + New bugfix release 17.2.3 ** Also affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727390 Title: New bugfix release 17.2.3 Status in mesa package in Ubuntu: New Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: [Impact] A new upstream bugfix release is available. FILL [Test case] [Regression potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456221] Re: while installing regional settings
** Changed in: wpa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1456221 Title: while installing regional settings Status in wpa package in Ubuntu: Invalid Bug description: I just tried to install additional language pack ProblemType: Package DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 CrashReports: 600:111:116:0:2015-05-18 15:39:26.381760672 +0200:2015-05-18 15:39:26.381760672 +0200:/var/crash/rsyslog.0.uploaded 600:0:116:207779:2015-05-18 15:34:47.344107389 +0200:2015-05-18 15:34:48.344107389 +0200:/var/crash/network-manager.0.crash 640:0:116:1587420:2015-05-18 15:39:23.263367891 +0200:2015-05-18 15:39:25.286591098 +0200:/var/crash/rsyslog.0.crash 600:0:116:207759:2015-05-18 15:34:47.332113265 +0200:2015-05-18 15:34:48.332113265 +0200:/var/crash/wpasupplicant.0.crash 644:0:116:0:2015-05-18 15:39:24.607106916 +0200:2015-05-18 15:39:24.607106916 +0200:/var/crash/rsyslog.0.upload Date: Mon May 18 15:34:48 2015 DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.2:package wpasupplicant is already installed and configured ErrorMessage: package wpasupplicant is already installed and configured InstallationDate: Installed on 2015-05-18 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) SourcePackage: wpa Title: package wpasupplicant 2.1-0ubuntu1.2 failed to install/upgrade: package wpasupplicant is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1456221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503448] Re: package wpasupplicant 2.1-0ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Changed in: wpa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1503448 Title: package wpasupplicant 2.1-0ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in wpa package in Ubuntu: Invalid Bug description: Failed to install software updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Tue Oct 6 17:49:32 2015 DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-02-02 (976 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: wpa Title: package wpasupplicant 2.1-0ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-25 (406 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1503448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293279] Re: computer freezes completely
** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1293279 Title: computer freezes completely Status in wpa package in Ubuntu: Incomplete Bug description: Im running Ubuntu 13.10 saucy on a Dell Inspiron 15R 5521. The computer completely freezes with no aparent reason. After looking at the log, the following message appears consistently just before the crash: wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] These are the log messages around the crash (manually forced restart at 19:59:52): Mar 16 19:28:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] Mar 16 19:29:05 pina whoopsie[1076]: online Mar 16 19:29:06 pina whoopsie[1076]: online Mar 16 19:35:02 pina whoopsie[1076]: online Mar 16 19:37:02 pina whoopsie[1076]: online Mar 16 19:38:07 whoopsie[1076]: last message repeated 3 times Mar 16 19:38:08 pina whoopsie[1076]: online Mar 16 19:38:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] Mar 16 19:38:46 pina whoopsie[1076]: online Mar 16 19:39:59 whoopsie[1076]: last message repeated 2 times Mar 16 19:42:09 pina whoopsie[1076]: online Mar 16 19:44:09 pina whoopsie[1076]: online Mar 16 19:44:10 pina whoopsie[1076]: online Mar 16 19:47:10 pina whoopsie[1076]: online Mar 16 19:48:11 whoopsie[1076]: last message repeated 3 times Mar 16 19:48:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] Mar 16 19:48:40 pina whoopsie[1076]: online Mar 16 19:49:59 whoopsie[1076]: last message repeated 2 times Mar 16 19:51:16 pina whoopsie[1076]: online Mar 16 19:51:17 pina whoopsie[1076]: online Mar 16 19:56:23 pina whoopsie[1076]: online Mar 16 19:57:13 pina whoopsie[1076]: online Mar 16 19:59:52 pina kernel: imklog 5.8.11, log source = /proc/kmsg started. Mar 16 19:59:52 pina rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="753" x-info="http://www.rsyslog.com";] start Mar 16 19:59:52 pina rsyslogd: rsyslogd's groupid changed to 103 Mar 16 19:59:52 pina rsyslogd: rsyslogd's userid changed to 101 Mar 16 19:59:52 pina rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] I don't know if the following is useful but if I see the log in a text editor, I can see a lot of "NULL" characters, something like: Mar 16 19:28:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] Mar 16 19:29:05 pina whoopsie[1076]: online Mar 16 19:29:06 pina whoopsie[1076]: online Mar 16 19:35:02 pina whoopsie[1076]: online Mar 16 19:37:02 pina whoopsie[1076]: online Mar 16 19:38:07 whoopsie[1076]: last message repeated 3 times Mar 16 19:38:08 pina whoopsie[1076]: online Mar 16 19:38:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] Mar 16 19:38:46 pina whoopsie[1076]: online Mar 16 19:39:59 whoopsie[1076]: last message repeated 2 times Mar 16 19:42:09 pina whoopsie[1076]: online Mar 16 19:44:09 pina whoopsie[1076]: online Mar 16 19:44:10 pina whoopsie[1076]: online Mar 16 19:47:10 pina whoopsie[1076]: online Mar 16 19:48:11 whoopsie[1076]: last message repeated 3 times Mar 16 19:48:22 pina wpa_supplicant[1085]: wlan0: WPA: Group rekeying completed with 84:c9:b2:d3:b2:89 [GTK=CCMP] Mar 16 19:48:40 pina whoopsie[1076]: online Mar 16 19:49:59 whoopsie[1076]: last message repeated 2 times Mar 16 19:51:16 pina whoopsie[1076]: online Mar 16 19:51:17 pina whoopsie[1076]: online Mar 16 19:56:23 pina whoopsie[1076]: online Mar 16 19:57:13 pina whoopsie[1076]: online NULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLMar 16 19:59:52 pina kernel: imklog 5.8.11, log source = /proc/kmsg started. Mar 16 19:59:52 pina rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="753" x-info="http://www.rsyslog.com";] start Mar 16 19:59:52 pina rsyslogd: rsyslogd's groupid changed to 103 Mar 16 19:59:52 pina rsyslogd: rsyslogd's userid changed to 101 Mar 16 19:59:52 pina rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1293279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1317221] Re: wireless no connection after upgrade from 13.10 to 14.0o4
** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1317221 Title: wireless no connection after upgrade from 13.10 to 14.0o4 Status in wpa package in Ubuntu: Incomplete Bug description: After upgrade from Kubuntu 13.10 to 14.04 network is still seen, and connection continues to be initialized, but is never established. After having replaced binary /sbin/wpa_supplicant (version 2.1) by /sbin/wpa_supplicant (version 1.0 of Kubuntu 13.10) everything seems to be running again smoothly. Appended is 1. network configuration and 2. debug output of wpa_supplicant v2.1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1 [modified: sbin/wpa_supplicant] ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Wed May 7 19:39:12 2014 InstallationDate: Installed on 2011-09-30 (950 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_GB:de:es:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: Upgraded to trusty on 2014-04-18 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1317221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
** Changed in: wpa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in wpa package in Ubuntu: Invalid Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396820] Re: Wireless stopped working after upgrade
This is for an outdated version of wpa-supplicant, closing. ** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1396820 Title: Wireless stopped working after upgrade Status in wpa package in Ubuntu: Incomplete Bug description: After upgrading to 14.04 connection to the wireless was hardly possible. After downgrading the wpasupplicant package to 1.0-3ubuntu2-mtrudel1 wireless connection was restored. System is Ubuntu 14.04.1 LTS on a HP Presario CQ71. Sorry I could only send the bug report from the 'repaired' system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 1.0-3ubuntu2~mtrudel1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 27 00:25:52 2014 InstallationDate: Installed on 2014-01-12 (318 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: wpa UpgradeStatus: Upgraded to trusty on 2014-04-19 (221 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1396820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242431] Re: ignores TPTK; can't verify EAPOL-Key integrity
** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1242431 Title: ignores TPTK; can't verify EAPOL-Key integrity Status in wpa package in Ubuntu: Incomplete Bug description: ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWSCAN]: Device or resource busy wlan0: Failed to initiate AP scan wlan0: Trying to associate with $BSSID (SSID=$BSSID freq=2462 MHz) ioctl[SIOCSIWFREQ]: Device or resource busy wlan0: Association request to the driver failed wlan0: Associated with $BSSID wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet ^C # wl ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument wlan0: Trying to associate with 00:22:6b:fc:89:53 (SSID='HringidanET' freq=2462 MHz) ioctl[SIOCSIWFREQ]: Device or resource busy wlan0: Association request to the driver failed wlan0: Associated with 00:22:6b:fc:89:53 wlan0: WPA: Key negotiation completed with 00:22:6b:fc:89:53 [PTK=CCMP GTK=TKIP] wlan0: CTRL-EVENT-CONNECTED - Connection to 00:22:6b:fc:89:53 completed (auth) [id=1 id_str=] [time passes] wlan0: WPA: Group rekeying completed with $BSSID [GTK=TKIP] On the first invocation of wpa_supplicant (by site-local script wl), the message integrity code (MIC) check fails repeatedly. But after an interrupt, a second invocation (the last two times I tried) succeeded immediately. Rekeying usually succeeds. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: wpasupplicant 1.0-3ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Oct 20 20:03:08 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-05 (229 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=is_IS.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: Upgraded to raring on 2013-05-06 (167 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1242431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1124789] Re: Unclean termination on dbus-daemon shutdown
** Changed in: wpa (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1124789 Title: Unclean termination on dbus-daemon shutdown Status in hostap: Fix Released Status in wpa package in Ubuntu: Fix Released Bug description: When wpa_supplicant is terminated normally (i.e. with SIGTERM or SIGINT or 'wpa_cli terminate'), it brings down any wireless interfaces it is managing. However, if wpa_supplicant is started by dbus activation and if the dbus messagebus is then shut down, it terminates abruptly and improperly without deconfiguring any network interfaces. Note that wpa_supplicant has its PID file installed in /run/sendsigs.omit.d, so /etc/init.d/sendsigs makes no attempt to shut it down. Since wpa_supplicant is not supervised by upstart, it is typical for dbus-daemon to be shut down before wpa_supplicant is. This has been reported upstream (along with steps to reproduce and a patch) at: http://w1.fi/bugz/show_bug.cgi?id=474 This bug, along with bug 1124803 (in network-manager), means that when I connect my laptop to a wifi network, no attempt is made to disconnect from that network when shutting the system down. This in turn triggers a bug in my BIOS which causes this system to hardlock in the middle of BIOS post when I reboot while still connected to a wifi network: http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: wpasupplicant 1.0-2ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4 Uname: Linux 3.5.0-24-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Wed Feb 13 22:12:08 2013 MarkForUpload: True SourcePackage: wpa UpgradeStatus: Upgraded to quantal on 2012-10-20 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hostap/+bug/1124789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399888] Re: Wireless network connection terminates and won't reconnect
This is for an outdated version of wpa-supplicant, closing. ** Changed in: wpa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1399888 Title: Wireless network connection terminates and won't reconnect Status in wpa package in Ubuntu: Incomplete Bug description: On: Linux x 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Wireless connections terminate without obvious reason. A reconnect is not possible. Every now and then (every second day) the network connection drops. The network indicator shows no signal strenght (empty icon) The correct connection is selected, a wealth of other SSIDs are in the list. A reconnect opens up the password dialog (which is an indication that the old error was reintroduced into the code). I reported this bug several times. The reason at the time was that reconnection would try to fetch the encrypted password and reencrypt it leading to a wrong password. There is a workaround: Disabling and Enabling the network connection reconnects correctly. In the code (as I analyzed then), this is due to the fact that the password from searing is taken as is and forwarded to the authentication code (not reencrypted). The connection gets established again. This issue did not occur in 12.04 and 12.10 (due to less connection problems or due to a fix is beyond me, I simple confirmed there were no connection aborts). It reappeared in 13.x and now is back as an annoyance. The error numbers then were around 460.000 - 490.000 as far is I remember (I have deleted bug reports I considered solved). I observed this issue on any Ubuntu machine. I also observed that the list of SSIDs is extremely long when this incident arises (approx. 15 - 20). Maybe a storm of SSID broadcasts is the basic cause but I have not done any research beyond what I described here. Hope this gets fixed for good now. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:27:42 2014 InstallationDate: Installed on 2013-05-17 (567 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1399888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1251134] Re: wpa_supplicant crashes when coming out of suspend
** Changed in: wpa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1251134 Title: wpa_supplicant crashes when coming out of suspend Status in wpa package in Ubuntu: Incomplete Bug description: Whenever (although possibly not every single time) I come out of suspend (i.e. reopening the lid of my laptop) I get a system error that wpa_supplicant has crashed. The next time I come out of suspend (although sometimes on that occassion) the wireless doesn't reconnect. I then need to restart my machine to get the wireless to reconnect. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: wpasupplicant 1.0-3ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 14 07:02:39 2013 InstallationDate: Installed on 2012-08-17 (453 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: wpa UpgradeStatus: Upgraded to saucy on 2013-10-19 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1251134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591533] Re: Can't create Ad-Hoc WiFi connection
** Changed in: wpa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1591533 Title: Can't create Ad-Hoc WiFi connection Status in wpa package in Ubuntu: Incomplete Bug description: I'm trying to create Ad-Hoc WiFi connection from BQ Aquaris M10 Ubuntu Edition to Nokia N900, running Qt Mobile Hotspot. My desktop PC connects ok, but Ubuntu Touch can't connect with message: wlan0: Association request to the driver failed I've tried unpotected and WEP protected connection. As a consequence to this failure, tablet reboots when next time connecting to normal infrastructure AP. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: wpasupplicant 2.4-0ubuntu7~overlay3 Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Sat Jun 11 18:49:04 2016 InstallationDate: Installed on 2016-05-24 (18 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160524-114757) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1591533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668724] Re: fails to mount cgroupfs inside containers running on 16.04
Drat. I do think this should still be pushed. I don't know when I'll have time to do it though. Please keep it open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1668724 Title: fails to mount cgroupfs inside containers running on 16.04 Status in cgroup-lite package in Ubuntu: Fix Released Status in cgroup-lite source package in Precise: Won't Fix Status in cgroup-lite source package in Trusty: Incomplete Status in cgroup-lite source package in Xenial: Incomplete Status in cgroup-lite source package in Yakkety: Won't Fix Bug description: I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts, and have noticed that the cgroups-mount script for mounting the cgroups inside the containers has stopped working. This is because systemd now comounts multiple controllers on a single hierarchy, which prevents mounting them individually inside the container. === SRU Justification Impact: nested containers fail to start Reproduce: create a root owned container; install lxc and cgroup-lite; create a container, and try to start it. Starting will fail if cgroup-lite is running in the first level container without this patch. Regression potential: should be low, it's possible that the regexp is simply wrong for some cases. === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668724] Re: fails to mount cgroupfs inside containers running on 16.04
I'll still aim to push this for trusty and xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1668724 Title: fails to mount cgroupfs inside containers running on 16.04 Status in cgroup-lite package in Ubuntu: Fix Released Status in cgroup-lite source package in Precise: Won't Fix Status in cgroup-lite source package in Trusty: Incomplete Status in cgroup-lite source package in Xenial: Incomplete Status in cgroup-lite source package in Yakkety: Won't Fix Bug description: I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts, and have noticed that the cgroups-mount script for mounting the cgroups inside the containers has stopped working. This is because systemd now comounts multiple controllers on a single hierarchy, which prevents mounting them individually inside the container. === SRU Justification Impact: nested containers fail to start Reproduce: create a root owned container; install lxc and cgroup-lite; create a container, and try to start it. Starting will fail if cgroup-lite is running in the first level container without this patch. Regression potential: should be low, it's possible that the regexp is simply wrong for some cases. === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670494] Re: 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
I understand this bug will be fixed when Marc rebased Ubuntu wpa package on top of the Debian's. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1670494 Title: 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards Status in wpa package in Ubuntu: Confirmed Bug description: init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs wpa_supplicant with the -W option, which causes it to wait for wpa_cli to attach. init_wpa_supplicant() then attaches wpa_cli to wpa_supplicant. When the nl80211 driver is used with some Intel cards, wpa_supplicant automatically defines a second p2p_dev_${WPA_IFACE} interface. If multiple interfaces are defined in wpa_supplicant, then wpa_supplicant will wait for multiple wpa_cli instances to attach. Since init_wpa_supplicant() only attaches a single wpa_cli process, this causes wpa_supplicant to hang, which ultimately leads to a timeout and causes interface configuration to fail. This has been fixed upstream: http://lists.infradead.org/pipermail/hostap/2015-December/034410.html And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402 However, the updated wpa_supplicant has not made it to Ubuntu (not even Zesty), and the "-m ''" workaround mentioned in the mailing list thread associated with the upstream fix does not work with the version of wpa_supplicant that comes with Ubuntu. Could the P2P patches that were merged into Debian be merged into Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1670494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347831] Re: hostapd is missing 802.11ac mode support
My understanding is that this is no longer an issue with the current hostapd. ** Changed in: wpa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1347831 Title: hostapd is missing 802.11ac mode support Status in wpa package in Ubuntu: Fix Released Bug description: When I try to create an AP using 802.11ac hostapd complains about unknown configuration items. I have a Compex acWave WLE900VX mini-pcie card that's fully supported by the ath10k_pci module. I took the example hostapd.conf settings from kernel.org ath10k page: http://wireless.kernel.org/en/users/Drivers/ath10k/configuration -- start hostapd.conf --- interface=wlan0 driver=nl80211 ssid=ath10k-test hw_mode=a channel=36 ht_capab=[HT40+] ieee80211n=1 ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=42 --- end hostapd.conf --- sudo hostapd -dd hostapd.conf random: Trying to read entropy from /dev/random Configuration file: hostapd.conf Line 10: unknown configuration item 'ieee80211ac' Line 11: unknown configuration item 'vht_oper_chwidth' Line 12: unknown configuration item 'vht_oper_centr_freq_seg0_idx' 3 errors found in configuration file 'hostapd.conf' The solution is to add the following to the ./configure file at compile time: "CONFIG_IEEE80211AC=y" As 802.11ac picks up in popularity everyone is going to want this support. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1347831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp