[Touch-packages] [Bug 1775972] [NEW] [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all
Public bug reported: 1. lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 2. alsa-utils: Installed: 1.1.3-1ubuntu1 Candidate: 1.1.3-1ubuntu1 Version table: *** 1.1.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shooter2160 F pulseaudio /dev/snd/controlC0: shooter2160 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 12:24:21 2018 InstallationDate: Installed on 2018-05-29 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1627 F pulseaudio shooter2160 F pulseaudio /dev/snd/controlC0: gdm1627 F pulseaudio shooter2160 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3016 dmi.board.asset.tag: Default string dmi.board.name: H110M-CS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3016:bd12/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-CS:rvrRevX.0x: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 modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-06-07T15:23:18.829781 mtime.conffile..etc.pulse.default.pa: 2018-06-07T15:56:30.613488 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1775972 Title: [System Product Name, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: 1. lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 2. alsa-utils: Installed: 1.1.3-1ubuntu1 Candidate: 1.1.3-1ubuntu1 Version table: *** 1.1.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shooter2160 F pulseaudio /dev/snd/controlC0: shooter2160 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 12:24:21 2018 InstallationDate: Installed on 2018-05-29 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest:
[Touch-packages] [Bug 1775974] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem
Public bug reported: I have updated the software several times but the sound card is not seen on the settings. Seems a software bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vincenzo 1138 F...m pulseaudio /dev/snd/controlC0: vincenzo 1138 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 08:12:53 2018 InstallationDate: Installed on 2018-05-02 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1775974 Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have updated the software several times but the sound card is not seen on the settings. Seems a software bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vincenzo 1138 F...m pulseaudio /dev/snd/controlC0: vincenzo 1138 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 08:12:53 2018 InstallationDate: Installed on 2018-05-02 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1775974/+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 1775985] [NEW] No sound in bionic
Public bug reported: Dual-boot system Windows 10 / Ubuntu 18.04 LTS - Sound working in Windows but no sound card detected in Ubuntu. I've followed all troubleshooting steps on Ubuntu's alsa troubleshooting wiki. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info-output.txt" https://bugs.launchpad.net/bugs/1775985/+attachment/5150555/+files/alsa-info-output.txt ** Description changed: Dual-boot system Windows 10 / Ubuntu 18.04 LTS - Sound working in Windows but no sound card detected in Ubuntu. I've followed all troubleshooting steps on Ubuntu's alsa troubleshooting wiki. - - $ bash alsa-info.sh --stdout - cat: /proc/asound/version: No such file or directory - grep: /proc/asound/cards: No such file or directory - cat: /proc/asound/cards: No such file or directory - lspci: Unable to load libkmod resources: error -12 - cat: /proc/asound/modules: No such file or directory - ls: cannot access '/dev/snd/*': No such file or directory - grep: /proc/asound/cards: No such file or directory - /usr/sbin/alsactl: save_state:1595: No soundcards found... - cat: /tmp/alsa-info.kAHvSVYxl9/alsactl.tmp: No such file or directory - upload=true&script=true&cardinfo= - !! - !!ALSA Information Script v 0.4.64 - !! - - !!Script ran on: Sat Jun 9 10:11:08 UTC 2018 - - - !!Linux Distribution - !!-- - - Ubuntu 18.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu - 18.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu - 18.04 LTS" HOME_URL="https://www.ubuntu.com/"; - SUPPORT_URL="https://help.ubuntu.com/"; - BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; - PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies - /privacy-policy" UBUNTU_CODENAME=bionic - - - !!DMI Information - !!--- - - Manufacturer: Gigabyte Technology Co., Ltd. - Product Name: GA-78LMT-USB3 - Product Version: - Firmware Version: FA - Board Vendor: Gigabyte Technology Co., Ltd. - Board Name:GA-78LMT-USB3 - - - !!ACPI Device Status Information - !!--- - - /sys/bus/acpi/devices/PNP0103:00/status15 - /sys/bus/acpi/devices/PNP0700:00/status15 - /sys/bus/acpi/devices/PNP0A03:00/status15 - /sys/bus/acpi/devices/PNP0C0C:00/status11 - /sys/bus/acpi/devices/PNP0C0F:00/status9 - /sys/bus/acpi/devices/PNP0C0F:01/status9 - /sys/bus/acpi/devices/PNP0C0F:02/status9 - /sys/bus/acpi/devices/PNP0C0F:03/status9 - /sys/bus/acpi/devices/PNP0C0F:04/status9 - /sys/bus/acpi/devices/PNP0C0F:05/status9 - /sys/bus/acpi/devices/PNP0C0F:06/status9 - /sys/bus/acpi/devices/PNP0C0F:07/status9 - /sys/bus/acpi/devices/device:0b/status 15 - /sys/bus/acpi/devices/device:0c/status 15 - /sys/bus/acpi/devices/device:0e/status 15 - /sys/bus/acpi/devices/device:0f/status 15 - - - !!Kernel Information - !!-- - - Kernel release:4.16.3+ - Operating System: GNU/Linux - Architecture: x86_64 - Processor: x86_64 - SMP Enabled: Yes - - - !!ALSA Version - !! - - Driver version: - Library version:1.1.3 - Utilities version: 1.1.3 - - - !!Loaded ALSA modules - !!--- - - - !!Sound Servers on this system - !! - - Pulseaudio: - Installed - Yes (/usr/bin/pulseaudio) - Running - Yes - - - !!Soundcards recognised by ALSA - !!- - - - !!PCI Soundcards installed in the system - !!-- - - 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) - 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] - - - !!Advanced information - PCI Vendor/Device/Subsystem ID's - !!--- - - 00:14.2 0403: 1002:4383 - Subsystem: 1458:a014 - -- - 01:00.1 0403: 1002:aaa0 - Subsystem: 1682:aaa0 - - - !!Modprobe options (Sound related) - !! - - snd_pcsp: index=-2 - snd_usb_audio: index=-2 - snd_atiixp_modem: index=-2 - snd_intel8x0m: index=-2 - snd_via82xx_modem: index=-2 - snd_atiixp_modem: index=-2 - snd_intel8x0m: index=-2 - snd_via82xx_modem: index=-2 - snd_usb_audio: index=-2 - snd_usb_caiaq: index=-2 - snd_usb_ua101: index=-2 - snd_usb_us122l: index=-2 - snd_usb_usx2y: index=-2 - snd_cmipci: mpu_port=0x330 fm_port=0x388 - snd_pcsp: index=-2 - snd_usb_audio: index=-2 - - - !!Loaded sound module options - !!--- - - - !!ALSA Device nodes - !!- - - - !!Aplay/Arecord output - !! - - APLAY - - aplay: device_list:270: no soundcards found... - - ARECORD - - arecord: device_list:270: no soundcards found... - - !!Amixe
[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
Thanks Michael. Your solution works for me in combination with Workaround 1 of https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades but with "PageFlip" line removed. -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1528139] Re: serialize_profile_from_old_profile() crash if file contains multiple profiles
For the records - I'm just working on a different implementation of
"(V)iew Changes", which will also replace the workaround with a real fix
:-) This will probably be in AppArmor 3.0, and will appear as merge
request on gitlab this weekend.
--
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/1528139
Title:
serialize_profile_from_old_profile() crash if file contains multiple
profiles
Status in AppArmor:
Fix Released
Status in AppArmor 2.10 series:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
= Changed Local Profiles =
The following local profiles were changed. Would you like to save
them?
[1 - /sbin/dhclient]
2 - /usr/sbin/nmbd
3 - /usr/bin/snx
4 - /usr/sbin/dnsmasq
5 - /{usr/,}bin/ping
6 - /usr/sbin/smbd
7 - /usr/lib/telepathy/mission-control-5
(S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes
b/w (C)lean profiles / Abo(r)t
Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in
apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2197, in
do_logprof_pass
save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2277, in
save_profiles
newprofile = serialize_profile_from_old_profile(aa[which], which, '')
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3961, in
serialize_profile_from_old_profile
if write_prof_data[hat]['network'].is_covered(network_obj, True, True):
AttributeError: 'collections.defaultdict' object has no attribute 'is_covered'
An unexpected error occoured!
For details, see /tmp/apparmor-bugreport-v7wx9fu9.txt
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
When I pressed V button aa-logprof exits with error.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: apparmor 2.10-0ubuntu6
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Mon Dec 21 09:54:51 2015
InstallationDate: Installed on 2014-04-19 (611 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-21-generic
root=/dev/mapper/ubuntu-root ro splash elevator=cfq nomdmonddf nomdmonisw
crashkernel=384M-:128M
SourcePackage: apparmor
Syslog:
UpgradeStatus: Upgraded to wily on 2015-11-14 (36 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1528139/+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 1775994] [NEW] package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Public bug reported: as I opened the laptop, I got this bug error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbinutils:amd64 2.30-20ubuntu2~18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: binutils:amd64: Install binutils-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 9 02:55:07 2018 Dependencies: binutils-common 2.30-20ubuntu2~18.04 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 zlib1g 1:1.2.11.dfsg-0ubuntu2 DuplicateSignature: package:libbinutils:amd64:2.30-20ubuntu2~18.04 Processing triggers for man-db (2.8.3-2) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-31 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: binutils Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1775994 Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in binutils package in Ubuntu: New Bug description: as I opened the laptop, I got this bug error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbinutils:amd64 2.30-20ubuntu2~18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: binutils:amd64: Install binutils-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 9 02:55:07 2018 Dependencies: binutils-common 2.30-20ubuntu2~18.04 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 zlib1g 1:1.2.11.dfsg-0ubuntu2 DuplicateSignature: package:libbinutils:amd64:2.30-20ubuntu2~18.04 Processing triggers for man-db (2.8.3-2) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-31 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: binutils Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1775994/+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 1775994] Re: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
** Tags removed: need-duplicate-check -- 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/1775994 Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in binutils package in Ubuntu: New Bug description: as I opened the laptop, I got this bug error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbinutils:amd64 2.30-20ubuntu2~18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: binutils:amd64: Install binutils-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 9 02:55:07 2018 Dependencies: binutils-common 2.30-20ubuntu2~18.04 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 zlib1g 1:1.2.11.dfsg-0ubuntu2 DuplicateSignature: package:libbinutils:amd64:2.30-20ubuntu2~18.04 Processing triggers for man-db (2.8.3-2) ... dpkg: error processing package libbinutils:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-31 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: binutils Title: package libbinutils:amd64 2.30-20ubuntu2~18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1775994/+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 951317] Re: ufw crashed with UnicodeDecodeError in get_loglevel(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128)
*** This bug is a duplicate of bug 953372 *** https://bugs.launchpad.net/bugs/953372 Thanks, it helped me in arch also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/951317 Title: ufw crashed with UnicodeDecodeError in get_loglevel(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) Status in ufw package in Ubuntu: Confirmed Bug description: # ufw version ufw 0.31-0ubuntu1 Copyright 2008-2010 Canonical Ltd. # python --version Python 2.7.3rc1 # ufw status verbose Traceback (most recent call last): File "/usr/sbin/ufw", line 111, in res = ui.do_action(pr.action, "", "", pr.force) File "/usr/lib/python2.7/dist-packages/ufw/frontend.py", line 580, in do_action res = self.get_status(True) File "/usr/lib/python2.7/dist-packages/ufw/frontend.py", line 246, in get_status out = self.backend.get_status(verbose, show_count) File "/usr/lib/python2.7/dist-packages/ufw/backend_iptables.py", line 416, in get_status (level, logging_str) = self.get_loglevel() File "/usr/lib/python2.7/dist-packages/ufw/backend.py", line 542, in get_loglevel rstr += "on (%s)" % (self.defaults['loglevel']) UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: ufw 0.31-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sat Mar 10 11:47:10 2012 ExecutablePath: /usr/sbin/ufw InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/sbin/ufw status verbose PythonArgs: ['/usr/sbin/ufw', 'status', 'verbose'] SourcePackage: ufw Title: ufw crashed with UnicodeDecodeError in get_loglevel(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) UpgradeStatus: Upgraded to precise on 2012-03-03 (6 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/951317/+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 1642718] Re: At least 3-5 minute gap between removing power cable and system notifying of event
Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=98796. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-11-20T13:58:53+00:00 Nikita Yerenkov-Scott wrote: I have noticed something very strange after upgrading to Ubuntu GNOME 16.10 with GNOME 3.22, and that is that if: - My laptop is fully charged and I remove the power cable: 1. The indicator in the top right hand side of the screen changes from the icon indicating that it is fully charged to the icon indicating that it is charging, but not fully charged. 2. In about 3-5 minutes (longer if I suspend my machine mid way during this time span) I will hear the noise which signifies that my machine has disconnected from the power cable and the icon will change to the normal one which indicates that the machine does not have a power cable attached to it (the time indicator will also show how long until the battery runs out instead of how long until it is fully charged). - My laptop is not fully charged and I remove the power cable: 1. The same happens as for the previous bullet point, however step 1 is skipped as it is not fully charged yet. - Either or the above bullet points, however I attach the power cable instead of removing it: 1. All of the expected (the noise and the icon change) happen immediately. I have described this with the Adwaita icon theme, however it is icon theme independent. If this is of any relevance, I have a Lenovo B590 laptop. I initially reported this issue here: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718 But thought I should also do so upstream. I first started off by reporting this issue to the upstream GNOME Shell project, however we established that the issue is in UPower rather than GNOME Shell: https://bugzilla.gnome.org/show_bug.cgi?id=774717#c7 Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718/comments/1 On 2016-11-20T13:59:41+00:00 Nikita Yerenkov-Scott wrote: I have UPower version 0.99.4-3 installed. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718/comments/2 On 2018-06-04T13:24:12+00:00 Gitlab-migration wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/upower/upower/issues/31. Reply at: https://bugs.launchpad.net/ubuntu- gnome/+bug/1642718/comments/4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1642718 Title: At least 3-5 minute gap between removing power cable and system notifying of event Status in Ubuntu GNOME: New Status in Upower: Unknown Status in upower package in Ubuntu: New Bug description: I have noticed something very strange after upgrading to Ubuntu GNOME 16.10 with GNOME 3.22, and that is that if: - My laptop is fully charged and I remove the power cable: 1. The indicator in the top right hand side of the screen changes from the icon indicating that it is fully charged to the icon indicating that it is charging, but not fully charged. 2. In about 3-5 minutes (longer if I suspend my machine mid way during this time span) I will hear the noise which signifies that my machine has disconnected from the power cable and the icon will change to the normal one which indicates that the machine does not have a power cable attached to it (the time indicator will also show how long until the battery runs out instead of how long until it is fully charged). - My laptop is not fully charged and I remove the power cable: 1. The same happens as for the previous bullet point, however step 1 is skipped as it is not fully charged yet. - Either or the above bullet points, however I attach the power cable instead of removing it: 1. All of the expected (the noise and the icon change) happen immediately. I have described this with the Adwaita icon theme, however it is icon theme independent. Related: Bug #1643190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1642718/+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 1752053] Re: nvidia-390 fails to boot graphical display
Hello, The GUI (graphicc user interface)!dose not start If i have no internet connection (offline ) An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04 Have the same probkeme The internet must connect at start (Ethernet or WiFi) Same problem whith the live dvd ? Why this internet connection deprndence Why the GUI coud’nt Start ofline Could you confirme this and help me to fix this issue Thanks for your supporters Best regards Battant -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
Dear Thadeu, I tested your patch and it seems to be working well on my i386 system it reduced initrd from 8.1 to 2.9 MB but does it have a chance to be integrated into Ubuntu 18.04 Bionic ? Or I should wait for Ubuntu 20.04 ? Now it is not even integrated into Ub. 18.10 Cosmic -- 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/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1776013] [NEW] systemd-networkd: DHCP lease lost (Ubuntu 18.04)
Public bug reported: I have a Linux router whose external Ethernet interface is configured from ISP's DHCP server. After its migration from Ubuntu 16.04 + ifupdown + isc-dhcp-client to Ubuntu 18.04 + netplan.io + systemd-networkd, I noticed that systemd-networkd plays overly fairly when it can not get a timely renew response from ISP's DHCP server: it honestly removes the dynamic IP from the interface and restores (often the same) IP only when ISP's DHCP server gives it a proper response again. Which causes 1..5-minute pauses in Internet availability since my ISP's DHCP server is for some reason flaky, i.e. it can become unresponsive for some periods of time. I never noticed this problem with isc-dhcp-client, and started noticing it only after migrating DHCP client role to systemd-networkd. The question is, can I (or you) make systemd-networkd DHCP client behave more relaxedly ? I know that most DHCP clients (isc-, pump, dhcpcd) at some stage of their development decided to implement such relaxed logic, i.e. to keep last-configured dynamic IP on the interface despite the lack of responses from DHCP server. As this is easier to implement than to make ISP staff fix their services, I would suppose there should be some knob in systemd-networkd settings. Or, at least, an idea to implement something similar in the future. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1776013 Title: systemd-networkd: DHCP lease lost (Ubuntu 18.04) Status in systemd package in Ubuntu: New Bug description: I have a Linux router whose external Ethernet interface is configured from ISP's DHCP server. After its migration from Ubuntu 16.04 + ifupdown + isc-dhcp-client to Ubuntu 18.04 + netplan.io + systemd-networkd, I noticed that systemd-networkd plays overly fairly when it can not get a timely renew response from ISP's DHCP server: it honestly removes the dynamic IP from the interface and restores (often the same) IP only when ISP's DHCP server gives it a proper response again. Which causes 1..5-minute pauses in Internet availability since my ISP's DHCP server is for some reason flaky, i.e. it can become unresponsive for some periods of time. I never noticed this problem with isc-dhcp-client, and started noticing it only after migrating DHCP client role to systemd-networkd. The question is, can I (or you) make systemd-networkd DHCP client behave more relaxedly ? I know that most DHCP clients (isc-, pump, dhcpcd) at some stage of their development decided to implement such relaxed logic, i.e. to keep last-configured dynamic IP on the interface despite the lack of responses from DHCP server. As this is easier to implement than to make ISP staff fix their services, I would suppose there should be some knob in systemd-networkd settings. Or, at least, an idea to implement something similar in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+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 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)
ok, I installed netplan.io 0.37.1 from Ubuntu Cosmic and set 'critical: true' for my ISP connection will check how it will be going after that. -- 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/1776013 Title: systemd-networkd: DHCP lease lost (Ubuntu 18.04) Status in systemd package in Ubuntu: New Bug description: I have a Linux router whose external Ethernet interface is configured from ISP's DHCP server. After its migration from Ubuntu 16.04 + ifupdown + isc-dhcp-client to Ubuntu 18.04 + netplan.io + systemd-networkd, I noticed that systemd-networkd plays overly fairly when it can not get a timely renew response from ISP's DHCP server: it honestly removes the dynamic IP from the interface and restores (often the same) IP only when ISP's DHCP server gives it a proper response again. Which causes 1..5-minute pauses in Internet availability since my ISP's DHCP server is for some reason flaky, i.e. it can become unresponsive for some periods of time. I never noticed this problem with isc-dhcp-client, and started noticing it only after migrating DHCP client role to systemd-networkd. The question is, can I (or you) make systemd-networkd DHCP client behave more relaxedly ? I know that most DHCP clients (isc-, pump, dhcpcd) at some stage of their development decided to implement such relaxed logic, i.e. to keep last-configured dynamic IP on the interface despite the lack of responses from DHCP server. As this is easier to implement than to make ISP staff fix their services, I would suppose there should be some knob in systemd-networkd settings. Or, at least, an idea to implement something similar in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+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 1775043] Re: bash completion not working: uses deprecated have()
Thank you for reporting this. I'll get it fixed in upstream ufw, Debian and Ubuntu 18.10. I'll then do an SRU for 18.04 LTS. ** Also affects: ufw Importance: Undecided Status: New ** Changed in: ufw Status: New => In Progress ** Changed in: ufw Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Also affects: ufw (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ufw (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ufw (Ubuntu Bionic) Status: New => Triaged ** Changed in: ufw (Ubuntu Cosmic) Status: New => Triaged ** Changed in: ufw (Ubuntu Bionic) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: ufw (Ubuntu Cosmic) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1775043 Title: bash completion not working: uses deprecated have() Status in ufw: In Progress Status in ufw package in Ubuntu: Triaged Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Triaged Bug description: bash completion, defined in /usr/share/bash- completion/completions/ufw, doesn't work: the completion is not dynamically loaded, because it uses deprecated helper function have(). According to /usr/share/bash-completions/bash_completion, which defines the helper functions: # Backwards compatibility for compat completions that use have(). # @deprecated should no longer be used; generally not needed with dynamically # loaded completions, and _have is suitable for runtime use. and at the end of the file: unset -f have unset have which means: function have() is not available for usage. The bash completion for ufw conditionally defines _ufw and the comspec: have ufw && _ufw() ... [ "$have" ] && complete -F _ufw ufw These should be changed to: _have ufw && _ufw() ... _have ufw && complete -F _ufw ufw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 4 14:34:11 2018 InstallationDate: Installed on 2018-04-28 (37 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1775043/+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 1774417] Re: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted
Hello everybody, I just wanted to add that this bug does not only causes 25s long login times, but at least for Xubuntu also causes that: - users authenticated via nis are unable to play sound, because pulseaudio (in non-system mode) doesn't list any sound cards besides the dummy device - users authenticated via nis are unable to mount usb-harddrives via thunar because of missing permissions -- 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/1774417 Title: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Confirmed Bug description: See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss- nis and suchlike) [1]. Logging in takes a long time. May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted May 30 13:26:50 ubuntu1804 sshd[3446]: pam_systemd(sshd:session): Failed to create session: Connection timed out Conclusion: > Please ask your downstream distribution to either: > > 1. include a systemd-logind.service.d/ snippet in your nss-nis package that turns off the IP firewalling logic for logind > 2. or patching systemd-logind.service for everybody to disable it distro-wide (which I'd really not recommend though, compromising the security for everybody just because for compat of a nowadays pretty niche nss module that does some very questionnable things doesn't sound like the best way out to me) [1] https://github.com/systemd/systemd/issues/7074 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1774417/+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 1776040] [NEW] bug report
Public bug reported: fingerprint gui not responding ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 9 23:35:24 2018 DistUpgraded: 2018-04-30 10:23:22,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2017-12-07 (184 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 23252EG ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=1c2e9f65-bfb0-4a84-98a0-3affb346ef44 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-30 (40 days ago) dmi.bios.date: 09/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA7WW (2.67 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252EG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA7WW(2.67):bd09/09/2016:svnLENOVO:pn23252EG:pvrThinkPadX230:rvnLENOVO:rn23252EG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23252EG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Apr 30 01:11:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1776040 Title: bug report Status in xorg package in Ubuntu: New Bug description: fingerprint gui not responding ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 9 23:35:24 2018 DistUpgraded: 2018-04-30 10:23:22,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2017-12-07 (184 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 23252EG ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=1c2e9f65-bfb0-4a84-98a0-3affb346ef44 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-30 (40 days ago) dmi.bios.date: 09/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA7WW (2.67 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252EG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA7WW(2.67):bd09/09/2016:svnLENOVO:pn23252EG:pvrThinkPadX230:rvnLENOVO:rn23252EG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23252EG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I tried the PPA solution of #47, with and old Assaultcube and ePSXe binaries. At the moment, everything seems fine, so I will update in case something fails or don't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Is it possible to backport fix which recently landed for bionic to xenial? -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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
