[Bug 1970090] Re: Backintime not launching because of python error
The fix is in this commit: https://github.com/bit- team/backintime/commit/e1ae23ddc0b4229053e3e9c6c61adcb7f3d8e9b3 Which is the only essential difference in 1.3.2. https://github.com/bit-team/backintime/compare/1.3.1...v1.3.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970090 Title: Backintime not launching because of python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970090] Re: Backintime not launching because of python error
I think, 22.04 being an LTS release, must have a working backup software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970090 Title: Backintime not launching because of python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973430] [NEW] backintime is broken with python 3.10
Public bug reported: Starting backintime fails with the following output: Traceback (most recent call last): File "/usr/share/backintime/common/backintime.py", line 27, in import config File "/usr/share/backintime/common/config.py", line 32, in import tools File "/usr/share/backintime/common/tools.py", line 1802, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' backintime-qt also fails with a similar error. This is because backintime is incompatible with Python 3.10, which is used in Ubuntu 22.04. This is referenced upstream: https://github.com/bit-team/backintime/issues/1175 The fix is available here: https://github.com/bit- team/backintime/commit/e1ae23ddc0b4229053e3e9c6c61adcb7f3d8e9b3 Please, update backintime to version 1.3.2. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-lowlatency 5.15.30 Uname: Linux 5.15.0-30-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 14 21:01:48 2022 InstallationDate: Installed on 2015-05-01 (2569 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-05-14 (0 days ago) ** Affects: backintime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973430 Title: backintime is broken with python 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1973430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926092] Re: lbzip2 package is empty in hirsute
The fix is released in Debian unstable, not in Ubuntu (not even jammy). ** Changed in: lbzip2 (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926092 Title: lbzip2 package is empty in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbzip2/+bug/1926092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948881] Re: XSane plugin not available in GIMP File menu
** Summary changed: - XSane plugin not available in File menu + XSane plugin not available in GIMP File menu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948881 Title: XSane plugin not available in GIMP File menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1948881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948881] [NEW] XSane plugin not available in File menu
Public bug reported: Description of the bug On the initial startup, GIMP initializes plugins, including xsane. Initializing xsane takes a long time on my system (perhaps, around 20 seconds), and after that the startup completes. However, there is no option in File->Create menu to create an image from scanner. On subsequent GIMP restarts, it no longer initializes plugins, including xsane, but the option is still missing. Starting xsane on its own works, it hangs for some time (perceptively, also around 20 seconds) while "scanning for devices", then starts, and the scanner is working as expected there. Reproduction Is the bug reproducible? Yes, always. Reproduction steps: 0. If you've already started GIMP before, touch /usr/lib/gimp/2.0/plug-ins/xsane/xsane. 1. Start GIMP. See that xsane plugin gets initialized. 2. Go to File->Create menu to see if xsane option is there. Expected result: There should be an option to obtain an image from scanner via xsane. Actual result: There is no option. Additional information My scanner is Canon LiDE 210, connected over USB. xsane 0.999-11ubuntu1 This started happening after upgrading from Kubuntu 21.04 to 21.10. In 21.04, with GIMP 2.10.22 and xsane 0.999-10ubuntu1, the xsane option was present. I've also created an upstream bug here: https://gitlab.gnome.org/GNOME/gimp/-/issues/7422 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gimp 2.10.24-2 ProcVersionSignature: Ubuntu 5.13.0-20.20-lowlatency 5.13.14 Uname: Linux 5.13.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:26:26 2021 InstallationDate: Installed on 2015-05-01 (2370 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gimp UpgradeStatus: Upgraded to impish on 2021-10-22 (4 days ago) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Affects: xsane (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Also affects: xsane (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948881 Title: XSane plugin not available in File menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1948881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926092] [NEW] lbzip2 package is empty in hirsute
Public bug reported: lbzip2 package does not contain any binaries in hirsute. Here is the list of files in groovy: /usr/bin/lbunzip2 /usr/bin/lbzcat /usr/bin/lbzip2 /usr/share/doc/lbzip2/changelog.Debian.gz /usr/share/doc/lbzip2/copyright /usr/share/man/man1/lbunzip2.1.gz /usr/share/man/man1/lbzcat.1.gz /usr/share/man/man1/lbzip2.1.gz https://packages.ubuntu.com/groovy/amd64/lbzip2/filelist And here is in hirsute: /usr/share/doc/lbzip2/changelog.Debian.gz /usr/share/doc/lbzip2/copyright https://packages.ubuntu.com/hirsute/amd64/lbzip2/filelist Package description does not indicate that the package is replaced by some other package. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lbzip2 2.5-2.1build1 ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12 Uname: Linux 5.11.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 25 21:24:12 2021 Dependencies: InstallationDate: Installed on 2015-05-01 (2185 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lbzip2 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (0 days ago) ** Affects: lbzip2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: lbzip2 package does not contain any binaries in hirsute. Here is the list of files in groovy: /usr/bin/lbunzip2 /usr/bin/lbzcat /usr/bin/lbzip2 /usr/share/doc/lbzip2/changelog.Debian.gz /usr/share/doc/lbzip2/copyright /usr/share/man/man1/lbunzip2.1.gz /usr/share/man/man1/lbzcat.1.gz /usr/share/man/man1/lbzip2.1.gz https://packages.ubuntu.com/groovy/amd64/lbzip2/filelist And here is in hirsute: /usr/share/doc/lbzip2/changelog.Debian.gz /usr/share/doc/lbzip2/copyright + https://packages.ubuntu.com/hirsute/amd64/lbzip2/filelist + + Package description does not indicate that the package is replaced by + some other package. + ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lbzip2 2.5-2.1build1 ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12 Uname: Linux 5.11.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 25 21:24:12 2021 Dependencies: - + InstallationDate: Installed on 2015-05-01 (2185 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lbzip2 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926092 Title: lbzip2 package is empty in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbzip2/+bug/1926092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924939] Re: Intel GPU lockups and graphical glitches in KDE
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 It seems, it started happening with kernel version 5.8.0-49. With 5.8.0-48 I can't reproduce this behavior, at least not as easily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924939 Title: Intel GPU lockups and graphical glitches in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924939] [NEW] Intel GPU lockups and graphical glitches in KDE
Public bug reported: After a recent package update (at this point, I believe it was a kernel package upgrade) I began experiencing Intel GPU hangs and graphical glitches, such as blinking or corrupt textures in the panels and windows. In dmesg I can see messages like these: [ 24.825956] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:86d2bff9, in plasmashell [1625] [ 24.826005] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 24.927993] i915 :00:02.0: [drm] plasmashell[1625] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-lowlatency 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-lowlatency 5.8.18 Uname: Linux 5.8.0-50-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 1319 F pulseaudio /dev/snd/controlC1: lastique 1319 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 19 02:18:39 2021 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2013-10-11 (2746 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-lowlatency root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-lowlatency N/A linux-backports-modules-5.8.0-50-lowlatency N/A linux-firmware 1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-21 (148 days ago) WifiSyslog: dmi.bios.date: 11/19/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924939 Title: Intel GPU lockups and graphical glitches in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
The updated packages don't work for me on groovy. $ apt policy ubuntu-keyring ubuntu-dbgsym-keyring ubuntu-keyring: Installed: 2020.06.17.3 Candidate: 2020.06.17.3 Version table: *** 2020.06.17.3 500 500 http://ru.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu groovy-updates/main i386 Packages 100 /var/lib/dpkg/status 2020.06.17.1 500 500 http://ru.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu groovy/main i386 Packages ubuntu-dbgsym-keyring: Installed: 2020.06.17.3 Candidate: 2020.06.17.3 Version table: *** 2020.06.17.3 500 500 http://ru.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu groovy-updates/main i386 Packages 100 /var/lib/dpkg/status 2020.06.17.1 500 500 http://ru.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu groovy/main i386 Packages $ sudo apt update Get:1 file:/mnt/g/packages ubuntu-groovy InRelease Ign:1 file:/mnt/g/packages ubuntu-groovy InRelease Get:2 file:/mnt/g/packages ubuntu-groovy Release [3044 B] Get:2 file:/mnt/g/packages ubuntu-groovy Release [3044 B] Get:3 file:/mnt/g/packages ubuntu-groovy Release.gpg Ign:3 file:/mnt/g/packages ubuntu-groovy Release.gpg Hit:4 http://ru.archive.ubuntu.com/ubuntu groovy InRelease Hit:5 http://ru.archive.ubuntu.com/ubuntu groovy-updates InRelease Hit:6 http://dl.google.com/linux/chrome/deb stable InRelease Hit:7 http://ru.archive.ubuntu.com/ubuntu groovy-backports InRelease Hit:8 http://archive.canonical.com/ubuntu groovy InRelease Hit:9 http://ppa.launchpad.net/lutris-team/lutris/ubuntu groovy InRelease Hit:10 http://security.ubuntu.com/ubuntu groovy-security InRelease Ign:11 http://ddebs.ubuntu.com groovy InRelease Hit:12 https://wire-app.wire.com/linux/debian stable InRelease Ign:13 http://ddebs.ubuntu.com groovy-updates InRelease Hit:14 https://dl.winehq.org/wine-builds/ubuntu groovy InRelease Hit:15 https://repo.skype.com/deb stable InRelease Get:16 http://ddebs.ubuntu.com groovy Release [40.4 kB] Get:17 http://ddebs.ubuntu.com groovy-updates Release [40.5 kB] Get:18 http://ddebs.ubuntu.com groovy Release.gpg [819 B] Get:19 http://ddebs.ubuntu.com groovy-updates Release.gpg [819 B] Hit:20 https://download.sublimetext.com apt/stable/ InRelease Ign:18 http://ddebs.ubuntu.com groovy Release.gpg Ign:19 http://ddebs.ubuntu.com groovy-updates Release.gpg Reading package lists... Done W: GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed. N: Updating from such a repository
[Bug 1922553] [NEW] libnss3 package contains invalid library paths
Public bug reported:
libnss3 package installs these files:
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}
Here, ${DEB_HOST_MULTIARCH} is the literal name of the directory created
in the filesystem. Presumably, this is caused by incorrect syntax of the
variable used in the packaging scripts.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-48.54-lowlatency 5.8.18
Uname: Linux 5.8.0-48-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 5 14:19:22 2021
InstallationDate: Installed on 2015-05-01 (2165 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: nss
UpgradeStatus: Upgraded to groovy on 2020-11-22 (134 days ago)
** Affects: nss (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922553
Title:
libnss3 package contains invalid library paths
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1922553/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905168] [NEW] PipeWire conflicts with PulseAudio and hides audio devices
Public bug reported: After upgrading from Kubuntu 20.04 to 20.10, PipeWire gets installed and started along with PulseAudio. As a result, upon system startup some audio output and input devices are not visible in PulseAudio. For example, a Builtin audio device might not have analog output or duplex modes - only digital output. Another audio device might not have 5.1 analog output + analog stereo input mode, but have other modes (e.g. stereo duplex or digital output). This may not happen the same way every time - on some start ups some of the devices may be fully visible in PulseAudio, on others - not. Presumably, PulseAudio cannot access these devices fully because PipeWire grabs these devices on startup. The problem is solved if pipewire and dependent packages are purged from system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pipewire (not installed) ProcVersionSignature: Ubuntu 5.8.0-29.31-lowlatency 5.8.14 Uname: Linux 5.8.0-29-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Nov 22 15:06:10 2020 InstallationDate: Installed on 2015-05-01 (2031 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pipewire UpgradeStatus: Upgraded to groovy on 2020-11-22 (0 days ago) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905168 Title: PipeWire conflicts with PulseAudio and hides audio devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1905168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879481] Re: update gcc-9 and gcc-10 packages for focal
At this point it might be worth updating gcc-10 to 10.2. I'm particularly interested in gcc-10 upgrade because I might be affected by a g++ bug that is already fixed in a more recent version of gcc-10. I cannot upgrade locally because the problem appears in a public Travis CI instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879481 Title: update gcc-9 and gcc-10 packages for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1879481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
The workaround is to blacklist hid_logitech_hidpp and hid_logitech_dj modules by adding /etc/modprobe.d/blacklist-hid_logitech.conf with this content: ``` blacklist hid_logitech_hidpp blacklist hid_logitech_dj ``` and running `update-initramfs -u -k all`. After reboot, the buttons start working as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
** Attachment added: "Output of `libinput list-devices` when the mouse is wireless" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+attachment/5361705/+files/libinput_wireless.txt ** Description changed: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. + + This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not + present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC3: lastique 2015 F pulseaudio - /dev/snd/controlC0: lastique 2015 F pulseaudio - /dev/snd/controlC2: lastique 2015 F pulseaudio - /dev/snd/controlC1: lastique 2015 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC3: lastique 2015 F pulseaudio + /dev/snd/controlC0: lastique 2015 F pulseaudio + /dev/snd/controlC2: lastique 2015 F pulseaudio + /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: - # Prevents "gave up waiting for suspend/resume device" timeout on boot - RESUME=none + # Prevents "gave up waiting for suspend/resume device" timeout on boot + RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-26-lowlatency N/A - linux-backports-modules-5.4.0-26-lowlatency N/A - linux-firmware 1.187 + linux-restricted-modules-5.4.0-26-lowlatency N/A + linux-backports-modules-5.4.0-26-lowlatency N/A + linux-firmware 1.187 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875408] [NEW] Logitech G700s extra G buttons don't work in wireless mode
Public bug reported: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2015 F pulseaudio /dev/snd/controlC0: lastique 2015 F pulseaudio /dev/snd/controlC2: lastique 2015 F pulseaudio /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-lowlatency N/A linux-backports-modules-5.4.0-26-lowlatency N/A linux-firmware 1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
** Attachment added: "Output of `libinput list-devices` when the mouse is wired" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+attachment/5361704/+files/libinput_wired.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] Re: DualShock 4 over Bluetooth does not work
Fixed in 5.3.0-24. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850443] Re: Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
This bug duplicates https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850443 Title: Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] Re: DualShock 4 over Bluetooth does not work
The bug is still present in 5.3.0-22. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] Re: DualShock 4 over Bluetooth does not work
I can confirm that the patch[1] in the upstream bug indeed fixes the problem for me. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth /bluetooth-next.git/commit/?id=8bb3537095f107ed55ad51f6241165b397aaafac -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] Re: DualShock 4 over Bluetooth does not work
Upon connecting the gamepad, kern.log contains the following lines: Nov 3 12:03:00 lastique-pc kernel: [ 189.682027] sony 0005:054C:05C4.0009: unknown main item tag 0x0 Nov 3 12:03:00 lastique-pc kernel: [ 189.682133] sony 0005:054C:05C4.0009: DualShock 4 calibration report's CRC check failed, received crc 0x0 != 0x2666b240 Nov 3 12:03:00 lastique-pc kernel: [ 189.682135] sony 0005:054C:05C4.0009: Retrying DualShock 4 get calibration report request Nov 3 12:03:00 lastique-pc kernel: [ 189.682137] sony 0005:054C:05C4.0009: DualShock 4 calibration report's CRC check failed, received crc 0x0 != 0x2666b240 Nov 3 12:03:00 lastique-pc kernel: [ 189.682138] sony 0005:054C:05C4.0009: Retrying DualShock 4 get calibration report request Nov 3 12:03:00 lastique-pc kernel: [ 189.682142] sony 0005:054C:05C4.0009: DualShock 4 calibration report's CRC check failed, received crc 0x0 != 0x2666b240 Nov 3 12:03:00 lastique-pc kernel: [ 189.682144] sony 0005:054C:05C4.0009: Failed to get calibration data from Dualshock 4 Nov 3 12:03:00 lastique-pc kernel: [ 189.682212] sony 0005:054C:05C4.0009: hidraw8: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 5c:f3:70:69:51:4e Nov 3 12:03:00 lastique-pc kernel: [ 189.682214] sony 0005:054C:05C4.0009: failed to claim input ** Bug watch added: Linux Kernel Bug Tracker #204877 https://bugzilla.kernel.org/show_bug.cgi?id=204877 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] Re: DualShock 4 over Bluetooth does not work
Possible upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=204877 The bug contains a link with a fix. Please, backport. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] [NEW] DualShock 4 over Bluetooth does not work
Public bug reported: Connecting Sony DualShock 4 over Bluetooth does not work on kernel 5.3. After pressing the PS button on the gamepad, the LED blinks for a few seconds while connecting and then stays constantly lit when Bluetooth connection is established. However, while "connected", lsusb doesn't show the gamepad and it doesn't work in games. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-lowlatency 5.3.0.19.22 ProcVersionSignature: Ubuntu 5.3.0-19.20-lowlatency 5.3.1 Uname: Linux 5.3.0-19-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2092 F pulseaudio /dev/snd/controlC0: lastique 2092 F pulseaudio /dev/snd/controlC2: lastique 2092 F pulseaudio /dev/snd/controlC1: lastique 2092 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 26 23:55:45 2019 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1639 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-lowlatency N/A linux-backports-modules-5.3.0-19-lowlatency N/A linux-firmware 1.183.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849993] Re: DualShock 4 over Bluetooth does not work
The problem exists in the mainline kernel 5.3.7 and does NOT exist with 5.2.21. I cannot test 5.4-rc4 because Nvidia driver doesn't compile for this kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849993 Title: DualShock 4 over Bluetooth does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793640] Re: Pulseaudio fails to detect sound card, while timidity is installed
Sending email to 901...@bugs.debian.org bounces because the bug is archived and cannot be modified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793640 Title: Pulseaudio fails to detect sound card, while timidity is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793640] Re: Pulseaudio fails to detect sound card, while timidity is installed
I have tested on Kubuntu 19.04: 1. After installing timidity-daemon, the timidity user is automatically created and added to the audio group. After reboot, the primary audio output device is inaccessible in PulseAudio. 2. After removing timidity user from audio group and rebooting, PulseAudio is able to use all audio output devices, as expected. I don't know how to test whether timidity works. 3. Purging timidity-daemon and timidity packages does *not* remove the timidity user. So, if the packages were installed before, after purging the user stays in the system and in the audio group. You have to manually remove the user (either completely or just from the audio group) using deluser. I think, that the user stays in the system may be a bug on its own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793640 Title: Pulseaudio fails to detect sound card, while timidity is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793640] Re: Pulseaudio fails to detect sound card, while timidity is installed
A user in that bug already verified that it works. What I'm pointing out is that the user/group fix is not implemented in the Debian or Ubuntu package, and as long as that bug is closed it's not likely become implemented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793640 Title: Pulseaudio fails to detect sound card, while timidity is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793640] Re: Pulseaudio fails to detect sound card, while timidity is installed
Can the Debian bug be reopened? Otherwise, I'm afraid, we'll never see it fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793640 Title: Pulseaudio fails to detect sound card, while timidity is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713615] Re: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden
I tried it multiple times, it didn't work, although it failed on different files. Debian package succeeded from the first attempt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713615 Title: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713615] Re: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden
This workaround: sudo apt purge ttf-mscorefonts-installer && sudo apt install --reinstall ttf-mscorefonts-installer does *not* fix the installation on Disco for me. I'm assuming it may fix the problem for some if the redirection from https to http does not happen for some reason. I'm able to install the Debian package from here: https://packages.debian.org/buster/ttf-mscorefonts-installer The bug is present in at least 2 Ubuntu releases while the fix in Debian is available for all this time. This is... disappointing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713615 Title: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793640] Re: Pulseaudio fails to detect sound card, while timidity is installed
>From the discussion in bug 210472 and in the Debian bug, it looks more like a configuration or intergration issue in timidity packages rather than a genuine upstream bug. Also, forums and mailing lists are a way to report bugs, too. Even though not as convenient as bug trackers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793640 Title: Pulseaudio fails to detect sound card, while timidity is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV
I've upgraded to upower 0.99.8-2ubuntu0.1 and it seems to have fixed the problem. Keyboard backlight is working now. Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800164 Title: Keyboard backlight control doesn't work on Asus N550JV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV
The keyboard backlight control doesn't work in 4.18.16. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800164 Title: Keyboard backlight control doesn't work on Asus N550JV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV
I tested with the mainline Linux kernel 4.19 and the key combinations work. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800164 Title: Keyboard backlight control doesn't work on Asus N550JV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800164] [NEW] Keyboard backlight control doesn't work on Asus N550JV
Public bug reported: Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase or decrease keyboard backlight brightness, respectively) doesn't do anything, the keyboard backlight stays off. Other key combinations, like adjusting display brightness or audio volume, do work. Keyboard backlight control worked in Kubuntu 18.04 on the same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 2820 F pulseaudio /dev/snd/controlC1: lastique 2820 F pulseaudio CurrentDesktop: KDE Date: Fri Oct 26 17:40:24 2018 InstallationDate: Installed on 2013-10-11 (1840 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (6 days ago) WifiSyslog: dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic kernel-fixed-upstream ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800164 Title: Keyboard backlight control doesn't work on Asus N550JV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210472] Re: Timidity daemon doesn't play nice with pulse audio
As described in bug https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1799541 starting timidity system daemon can prevent PulseAudio from gaining access to one of the sound cards in ALSA. I think, a better solution would be to change timidity to run as a user- specific service, instead of system-wide, and depend on pulseaudio or pulseaudio.socket to start first. This way we should have PulseAudio running in user mode and starting before timidity. Timidity will grab the default ALSA device, which is an alias for the pulse loopback when pulseaudio is running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/210472 Title: Timidity daemon doesn't play nice with pulse audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/210472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
I think I found the source of the problem. Apparently, I had running the timidity daemon, which grabbed the ALSA PCM device and caused the "Device or resource busy" error. The "fuser -v /dev/snd/*" command didn't show this as I ran it as an unprivileged user and the daemon runs under a different "timidity" user. When I stopped the daemon and restarted pulseaudio, it recognized the D2X card. I'm sure I didn't install timidity manually, so I guess it is preinstalled either by default Ubuntu installation or it was added during the upgrade to 18.10. Or it was configured previously so that it didn't cause the conflict with PulseAudio. In any case, I think this conflict needs to be resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
I can add that I've also tried with the kernel 4.15.0-36.39 from Ubuntu 18.04 and the problem also reproduced. Right now I also suspect systemd/udev or userspace ALSA components because, although I can play sounds on the "default" and "sysdefault" devices, I cannot play on "D2X" or "surround51" devices: $ aplay -D hw:D2X /usr/share/sounds/alsa/Front_Center.wav aplay: main:828: audio open error: Device or resource busy I know no application is using the sound device, "fuser -v /dev/snd/*" output is empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
The problem reproduces with generic kernel 4.19.0. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204674/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204677/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204679/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204678/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204681/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204680/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204682/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204675/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204676/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204671/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204673/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204672/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204670/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
nd output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=PCH,DEV=0 HDA Intel PCH, HDMI 0 HDMI Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Direct sample mixing device dmix:CARD=PCH,DEV=1 HDA Intel PCH, ALC892 Digital Direct sample mixing device dmix:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=1 HDA Intel PCH, ALC892 Digital Direct sample snooping device dsnoop:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=1 HDA Intel PCH, ALC892 Digital Direct hardware device without any conversions hw:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=1 HDA Intel PCH, ALC892 Digital Hardware device with all software conversions plughw:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Hardware device with all software conversions ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lastique 12503 F pulseaudio /dev/snd/controlC2: lastique 12503 F pulseaudio CurrentDesktop: KDE Date: Tue Oct 23 20:13:43 2018 InstallationDate: Installed on 2015-05-01 (1270 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-20 (3 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-08-27T17:20:33.914988 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: lastique 6439 F pulseaudio + /dev/snd/controlC2: lastique 6439 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2015-05-01 (1271 days ago) + InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-10-generic N/A + linux-backports-modules-4.18.0-10-generic N/A + linux-firmware 1.175 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: cosmic + Uname: Linux 4.18.0-10-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-10-20 (3 days ago) + UserGroups: adm audio autologin cdrom davfs2 debian-tor dip libvirt libvirtd lpadmin netdev plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 11/09/2012 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 3603 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8Z68-V PRO + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204669/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799541] [NEW] ASUS Xonar D2X not detected in PulseAudio
2" sysfs.path = "/devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/sound/card1" udev.id = "usb-046d_HD_Pro_Webcam_C920_8E2D0CCF-02" device.bus = "usb" device.vendor.id = "046d" device.vendor.name = "Logitech, Inc." device.product.id = "082d" device.product.name = "HD Pro Webcam C920" device.serial = "046d_HD_Pro_Webcam_C920_8E2D0CCF" device.form_factor = "webcam" device.string = "front:1" device.buffering.buffer_size = "256000" device.buffering.fragment_size = "128000" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "HD Pro Webcam C920 Analog Stereo" alsa.mixer_name = "USB Mixer" alsa.components = "USB046d:082d" module-udev-detect.discovered = "1" device.icon_name = "camera-web-usb" Ports: analog-input-mic: Microphone (priority: 8700) Active Port: analog-input-mic Formats: pcm $ cat /proc/asound/cards 0 [D2X]: AV200 - Xonar D2X Asus Virtuoso 200 at 0xe000, irq 16 1 [C920 ]: USB-Audio - HD Pro Webcam C920 HD Pro Webcam C920 at usb-:00:1d.0-1.4, high speed 2 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7f2 irq 45 $ aplay -L default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) pulse PulseAudio Sound Server sysdefault:CARD=D2X Xonar D2X, Multichannel Default Audio Device front:CARD=D2X,DEV=0 Xonar D2X, Multichannel Front speakers surround21:CARD=D2X,DEV=0 Xonar D2X, Multichannel 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=D2X,DEV=0 Xonar D2X, Multichannel 4.0 Surround output to Front and Rear speakers surround41:CARD=D2X,DEV=0 Xonar D2X, Multichannel 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=D2X,DEV=0 Xonar D2X, Multichannel 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=D2X,DEV=0 Xonar D2X, Multichannel 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=D2X,DEV=0 Xonar D2X, Multichannel 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=D2X,DEV=0 Xonar D2X, Multichannel IEC958 (S/PDIF) Digital Audio Output dmix:CARD=D2X,DEV=0 Xonar D2X, Multichannel Direct sample mixing device dmix:CARD=D2X,DEV=1 Xonar D2X, Digital Direct sample mixing device dsnoop:CARD=D2X,DEV=0 Xonar D2X, Multichannel Direct sample snooping device dsnoop:CARD=D2X,DEV=1 Xonar D2X, Digital Direct sample snooping device hw:CARD=D2X,DEV=0 Xonar D2X, Multichannel Direct hardware device without any conversions hw:CARD=D2X,DEV=1 Xonar D2X, Digital Direct hardware device without any conversions plughw:CARD=D2X,DEV=0 Xonar D2X, Multichannel Hardware device with all software conversions plughw:CARD=D2X,DEV=1 Xonar D2X, Digital Hardware device with all software conversions sysdefault:CARD=PCH HDA Intel PCH, ALC892 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=PCH,DEV=0 HDA Intel PCH, HDMI 0 HDMI Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Direct sample mixing device dmix:CARD=PCH,DEV=1 HDA Intel PCH, ALC892 Digital Direct sample mixing device dmix:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Direct
[Bug 1798979] Re: Hama "Slim" USB 3.0 Multi Card Reader doesn't work
> Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? As said in the description, it started happening after upgrading from Kubuntu 18.04 to 18.10. 18.04 has kernel 4.15. > Would it be possible for you to test the latest upstream kernel? The problem reproduces with kernel 4.19 rc8. The is the dmesg lines that start appearing when the problem happens: [ 136.161611] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 136.161615] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 136.293090] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 166.865743] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 166.865747] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 167.001317] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798979] [NEW] Hama "Slim" USB 3.0 Multi Card Reader doesn't work
Public bug reported: I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi-card- reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening: [ 147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [ 147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? [ 220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [ 314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd and so on. No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 3112 F pulseaudio /dev/snd/controlC1: lastique 3112 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 20 19:31:35 2018 InstallationDate: Installed on 2015-05-01 (1267 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798979 Title: Hama "Slim" USB 3.0 Multi Card Reader doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713615] Re: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden
Happens when upgrading from Kubuntu 18.04 to 18.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713615 Title: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574746] Re: Enable support for libsoxr
Yay, finally! Thank you Daniel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574746 Title: Enable support for libsoxr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783822] Re: [netem] Incorrect jitter delays
> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? I don't know when this started to happen. But the same netem rules worked as expected in Ubuntu 17.10. I've tested kernel version 4.18.0-041800rc6.201807221830, as you suggested. The problem does not appear with it: $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=101 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=76.3 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=105 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=95.0 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=128 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=75.9 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=84.5 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=130 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=94.6 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=106 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=76.2 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=108 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=118 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=142 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=96.5 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=80.6 ms ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783822 Title: [netem] Incorrect jitter delays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783822] [NEW] [netem] Incorrect jitter delays
Public bug reported: If I configure a netem rule with a delay and jitter, the actual network delay jitter is significantly different from the configured value. With no netem rules: $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=3.06 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=2.88 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=3.01 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=2.86 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=2.94 ms With netem rule with delay and jitter: $ sudo tc qdisc add dev wlp4s0 root netem delay 100ms 40ms $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=106 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=111 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=115 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=124 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=136 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=120 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=4371 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=1487 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=5513 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=457 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=137 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=4367 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=111 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=4366 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=4378 ms 64 bytes from 192.168.1.2: icmp_seq=18 ttl=64 time=132 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=4373 ms 64 bytes from 192.168.1.2: icmp_seq=21 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=64 time=4375 ms 64 bytes from 192.168.1.2: icmp_seq=23 ttl=64 time=112 ms 64 bytes from 192.168.1.2: icmp_seq=19 ttl=64 time=4502 ms Delays >4 seconds are unexpected, the expected delays are approximately 60 - 140 ms. With netem rule with delay and *no* jitter: $ sudo tc qdisc add dev wlp4s0 root netem delay 100ms $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=64 time=103 ms In this case the delays are as expected. The 192.168.1.2 host is a machine in the local network. The problem appears with different network interfaces, including loopback (in which case the delays are doubled) and on multiple machines. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 2087 F pulseaudio /dev/snd/controlC1: lastique 2087 F pulseaudio CurrentDesktop: KDE Date: Thu Jul 26 19:31:25 2018 InstallationDate: Installed on 2013-10-11 (1748 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 acpi_osi= acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-05 (82 days ago) WifiSyslog: dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pn
[Bug 1769385] [NEW] "text" errors when running Apport
Public bug reported: When reporting a bug against SDDM (ubuntu-bug sddm) Apport displayed an error dialog box with only "text" message. See the screenshot. The error should be more descriptive. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ERROR: apport (pid 5672) Sat May 5 16:51:48 2018: host pid 1566 crashed in a separate mount namespace, ignoring ERROR: apport (pid 30302) Sat May 5 17:41:20 2018: called for pid 3084, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 30302) Sat May 5 17:41:20 2018: executable was modified after program start, ignoring ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 5 20:23:29 2018 InstallationDate: Installed on 2015-05-01 (1099 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot of an unknown error" https://bugs.launchpad.net/bugs/1769385/+attachment/5134476/+files/apport_error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769385 Title: "text" errors when running Apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1769385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769384] Re: SDDM does not unlock gnome-keyring on login
Note that the attached modified pam.d/sddm and pam.d/sddm-autologin files are the result of my attempts to fix the problem. The problem exists with the original files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769384 Title: SDDM does not unlock gnome-keyring on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1769384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769385] Re: "text" errors when running Apport
This error dialog box appeared twice - first, when Apport was collecting information and second right after I pressed Yes on the first one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769385 Title: "text" errors when running Apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1769385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769384] [NEW] SDDM does not unlock gnome-keyring on login
Public bug reported: On automatic login, SDDM does not unlock gnome-keyring, which suspends the boot process and asks for a password. The boot process blocks until the password is entered. Apparently, the boot process stops because Pidgin is in the autostart list and it requires access to the keyring. The default keyring has a password that is the same as the password of the user that logs in automatically. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sddm 0.17.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 5 20:08:59 2018 InstallationDate: Installed on 2015-05-01 (1099 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: sddm UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago) mtime.conffile..etc.pam.d.sddm: 2018-05-05T20:03:52.840372 mtime.conffile..etc.pam.d.sddm-autologin: 2018-05-05T20:04:23.052211 ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769384 Title: SDDM does not unlock gnome-keyring on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1769384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
For me this problem appeared after I upgraded from 17.10 to 18.04 two of my machines. Both machines increased their boot times substantially (by around 30 seconds). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] Re: tcp_fastretrans_alert kernel warnings
Just for the record, I have found the problem that caused the lockups. It was the nvidia driver ForceCompositionPipeline parameter in xorg.conf. Without it the hangs no longer happen, but the warnings are still present in the log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744379 Title: tcp_fastretrans_alert kernel warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] Re: tcp_fastretrans_alert kernel warnings, possible system hardlock
The errors in the kernel log don't appear with kernel version 4.10.17. However, I still get lockups with that kernel as well. At this point I think the lockups are probably not related to the warnings and are possibly caused by a hardware failure. The errors in the log are still a valid issue, IMHO. ** Summary changed: - tcp_fastretrans_alert kernel warnings, possible system hardlock + tcp_fastretrans_alert kernel warnings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744379 Title: tcp_fastretrans_alert kernel warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] Re: tcp_fastretrans_alert kernel warnings, possible system hardlock
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744379 Title: tcp_fastretrans_alert kernel warnings, possible system hardlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] Re: tcp_fastretrans_alert kernel warnings, possible system hardlock
Is it possible that the lockups are caused by the buggy microcode update from Intel? Did Canonical revert the microcode update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744379 Title: tcp_fastretrans_alert kernel warnings, possible system hardlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] Re: tcp_fastretrans_alert kernel warnings, possible system hardlock
I tried kernel 4.15.0-rc9 and had the same kind of hard lockup. The system wouldn't react to mouse or keypresses after some idle time. The log is attached (the kernel was upgraded on Jan 24-th). There are many errors about soft lockups in the log, although the backtraces are different from 4.13. ** Attachment added: "Kernel 4.15.0-rc9 log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+attachment/5042206/+files/kern_4.15.0rc9.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744379 Title: tcp_fastretrans_alert kernel warnings, possible system hardlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] Re: tcp_fastretrans_alert kernel warnings, possible system hardlock
> Did this issue start happening after an update/upgrade? I did not have hard lockups before upgrading to 4.13.0-25. The lockup happened once, after several days past the upgrade. I did not look in the logs until after the lockup, so I can't tell if the tcp_fastretrans_alert errors were there with older kernels. > Would it be possible for you to test the latest upstream kernel? Given that I had only one lockup so far and tcp_fastretrans_alert errors happen at unknown points, I can only see if such errors appear in logs after a few days of use. I cannot be sure if it fixes the lockup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744379 Title: tcp_fastretrans_alert kernel warnings, possible system hardlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744379] [NEW] tcp_fastretrans_alert kernel warnings, possible system hardlock
Public bug reported: I have experienced a full system lockup, not even SysRq+REISUB could reboot the system. In the kernel logs I noticed multiple tcp_fastretrans_alert warnings and the upstream bug (https://bugzilla.kernel.org/show_bug.cgi?id=195835, https://bugzilla.kernel.org/show_bug.cgi?id=60779) seems to indicate this may be the reason. In the attached kernel log, the hang happened immediately before the last reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 3183 F pulseaudio /dev/snd/controlC1: lastique 3183 F pulseaudio /dev/snd/controlC2: lastique 3183 F pulseaudio /dev/snd/controlC0: lastique 3183 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 19 22:26:36 2018 InstallationDate: Installed on 2015-05-01 (993 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (76 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Kernel log" https://bugs.launchpad.net/bugs/1744379/+attachment/5039732/+files/kern.log ** Description changed: I have experienced a full system lockup, not even SysRq+REISUB could reboot the system. In the kernel logs I noticed multiple tcp_fastretrans_alert warnings and the upstream bug - (https://bugzilla.kernel.org/show_bug.cgi?id=60779) seems to indicate + (https://bugzilla.kernel.org/show_bug.cgi?id=195835) seems to indicate this may be the reason. In the attached kernel log, the hang happened immediately before the last reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC3: lastique 3183 F pulseaudio - /dev/snd/controlC1: lastique 3183 F pulseaudio - /dev/snd/controlC2: lastique 3183 F pulseaudio - /dev/snd/controlC0: lastique 3183 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC3: lastique 3183 F pulseaudio + /dev/snd/controlC1: lastique 3183 F pulseaudio + /dev/snd/controlC2: lastique 3183 F pulseaudio + /dev/snd/controlC0: lastique 3183 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 19 22:26:36 2018 InstallationDate: Installed on 2015-05-01 (993 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: - linux-restricted-modules-4.13.0-25-generic N/A - linux-backports-modules-4.13.0-25-generic N/A - linux-firmware 1.169.1 + linux-restricted-modules-4.13.0-25-generic N/A + linux-backports-modules-4.13.0-25-generic N/A + linux-firmware 1.169.1 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStat
[Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
I have fixed the problem by installing nvidia driver 390.12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742310] [NEW] No network in recovery mode (systemd-resolved does not start)
Public bug reported: When booting into recovery mode and enabling networking, networking does not get enabled. DNS lookup doesn't work because systemd-resolved does not start and /etc/resolv.conf is a broken symlink. Steps to reproduce: 1. Reboot. 2. In the grub menu, select "Advanced options for Ubuntu" and then select boot in recovery mode. 3. When the menu appears, select "networking". In the console you may notice a few errors that /etc/resolv.conf file not found. 4. Select "drop to root" console. 5. Try pinging some hosts, like "ping ubuntu.com". You will see that name resolution doesn't work. 6. You can check that the network interface is up, "ip addr" displays valid info and the interface has an assigned local IP. 7. You can check that /etc/resolv.conf is in fact a dangling link to ../run/resolvconf/resolv.conf. 8. You can see that systemd-resolved is not running: "systemctl status systemd-resolved" shows the service is dead. 9. Invoking "systemctl start systemd-resolved" hangs indefinitely, the service not starting. The workaround to get DNS working is to replace /etc/resolv.conf with a valid link or a file with a DNS server. The DNS lookup and networking in general works fine if the system is booted normally. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jan 10 02:18:14 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [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 3 overridden configuration files found. UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742310 Title: No network in recovery mode (systemd-resolved does not start) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742302] [NEW] Kernel 4.13.0-25 broke nvidia driver
Public bug reported: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "nvidia driver build log" https://bugs.launchpad.net/bugs/1742302/+attachment/5033818/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574746] Re: Enable support for libsoxr
I've created a MIR ticket for libsoxr: https://bugs.launchpad.net/ubuntu/+source/libsoxr/+bug/1702558 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574746 Title: Enable support for libsoxr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702558] [NEW] [MIR] libsoxr
Public bug reported: [Availability] libsoxr is in "universe", it compiles for all target architectures: https://launchpad.net/ubuntu/+source/libsoxr/0.1.2-2 [Rationale] I would like libsoxr to be moved to "main" so that it can be used in PulseAudio as an audio resampler backend (see https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574746). The library provides improved quality and performance over the currently used speex resamplers. [Security] The library is used for raw audio processing. Its input and output data is produced and consumed by PulseAudio server. The library builds into two library packages: libsoxr0 and libsoxr-lsr0. The library does not use network or external strings. Library from libsoxr-lsr0 uses environment variables to control some aspects of its behavior, but this library will not be used in PulseAudio (only libsoxr0 will). The environment variables are: SOXR_LSR_NUM_THREADS, SOXR_LSR_STRICT, see src/lsr.c. There were no CVE found for libsoxr: http://cve.mitre.org/cve/cve.html https://www.google.com/search?client=ubuntu=fs=site%3Awww.openwall.com%2Flists%2Foss-security+libsoxr=utf-8=utf-8_rd=cr=gz9dWYW3DMf37gSm-JrYCg#newwindow=1=fs=site:www.openwall.com/lists/oss-security+libsoxr http://people.canonical.com/~ubuntu-security/cve/universe.html Package build scripts enable hardening. Overall I consider this library to have low security risk. [Quality assurance] The package build scripts automatically run library tests. There are currently no open bug reports for the package in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libsoxr There are couple of bugs in Debian: https://bugs.debian.org/src:libsoxr There are no bugs in the upstream bug tracker: https://sourceforge.net/p/soxr/tickets/?source=navbar Recent discussion is happening on the project forum: https://sourceforge.net/p/soxr/discussion/general/ Package installation does not require any manual configuration. There is a debian/watch file. [Dependencies] The library depends only on libc6 and libgomp1, both of which are in "main". [Standards compliance] AFAICS, FHS and Debian policy are fulfilled. [Maintenance] The package is currently maintained by Debian Multimedia Maintainers. [Background information] Package description adequately describe the purpose of the library. I have been building PulseAudio locally with support for libsoxr and have been using it for a few years now, without problem. I used libsoxr in other projects as well. This is a fast library that produces audio of a very good quality. ** Affects: libsoxr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702558 Title: [MIR] libsoxr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoxr/+bug/1702558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688735] Re: mpv: vdpau-copy does not work
I don't see 3.2.5-1 packages in Zesty, only 7:3.2.4-1build2. ** Changed in: ffmpeg (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688735 Title: mpv: vdpau-copy does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1688735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691996] [NEW] DNS and search domain is not pushed to systemd-resolved sometimes
Public bug reported: I have an OpenVPN connection with statically configured DNS server address and the search domain. When this connection is established, there is a high chance that the DNS address and the search domain are not pushed to systemd-resolved for this connection. The problem does not reproduce reliably, sometimes the parameters are pushed. When the parameters are not pushed, 'systemd-resolve --status' reports no DNS servers or DNS domain for the VPN connection, and name resolution does not work. This bug has been reportedly fixed upstream in NetworkManager 1.8. The upstream bug reports are: https://bugzilla.gnome.org/show_bug.cgi?id=782597 https://bugzilla.gnome.org/show_bug.cgi?id=779087 Please, update NetworkManager shipped with Ubuntu or backport the fix. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 19 13:35:42 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-01 (748 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-05-11T15:26:12.449289 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH virbr0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 virbr0 a80bff56-e5d6-4fa4-b544-89cb3c389e3b /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 44a70bab-e44e-3942-8259-e96eb6f3fe5b /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tun unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691996 Title: DNS and search domain is not pushed to systemd-resolved sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1691996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683860] Re: Search domains are not considered for split-tunnelling connections
I have reported the bug upstream: https://bugzilla.gnome.org/show_bug.cgi?id=782469. ** Bug watch added: GNOME Bug Tracker #782469 https://bugzilla.gnome.org/show_bug.cgi?id=782469 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683860 Title: Search domains are not considered for split-tunnelling connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1683860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688735] [NEW] mpv: vdpau-copy does not work
Public bug reported: When vdpau-copy hardware decoder is used, mpv displays an error such as this: The linesize 1280 cannot be represented as uint32 The problem is a bug in ffmpeg that was fixed in 3.3.0 but is present in 3.2.4 which is released in Ubuntu 17.04. I'm attaching the patch that fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ffmpeg 7:3.2.4-1build2 Uname: Linux 4.10.0-14.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 6 17:11:41 2017 InstallationDate: Installed on 2015-05-01 (735 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: ffmpeg UpgradeStatus: Upgraded to zesty on 2017-04-16 (20 days ago) ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty ** Attachment added: "A patch that fixes the problem" https://bugs.launchpad.net/bugs/1688735/+attachment/4872615/+files/01_fix_vdpau_transfer_data.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688735 Title: mpv: vdpau-copy does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1688735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
> And if you had a look at the upstream bug you'd see that the patch doesn't work. I can see that someone reported it to not work for one-key combinations (e.g. Ctrl). I believe, the previous patch that was removed had the same limitation, and it was "good enough". We need to see if it works for two-key combinations (e.g. Ctrl+Alt or Alt+Shift). > It needs to get upstream first anyway. It's unlikely to be accepted into XKb for the same reasons as the previous patch. This ticket is a request to add the patch to Ubuntu packages because this is a real problem that affects people. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1683383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683860] [NEW] Search domains are not considered for split-tunnelling connections
Public bug reported: For split-tunnelling VPN connections (i.e. when the "Use only for resources on this connection" checkbox is set in the IPv4 -> Routes menu), the IPv4 -> Search Domains field has no effect. For example, my VPN connection has the following parameters: [ipv4] dns=xxx.xxx.xxx.xxx; dns-search=mydomain.net; ignore-auto-dns=true method=auto never-default=true After connecting, `systemd-resolve --status` shows for this connection: Link 5 (tun0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes DNS Servers: xxx.xxx.xxx.xxx DNS Domain: ~mydomain.net Note that there is a ~ character before the domain name, which has a special semantics in systemd-resolved (as I understand, such entries are not used as search names). As a result, the search name is not used to complete simple names: systemd-resolve foo foo: resolve call failed: All attempts to contact name servers or networks failed ping foo ping: foo: Name or service not known ping foo.mydomain.net 64 bytes from xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): icmp_seq=1 ttl=62 time=5.33 ms Note that the search domains work if the VPN connection is configured as non-split-tunnelling connection. In this case `systemd-resolve --status` shows "DNS Domain: mydomain.net" (without ~) and `systemd-resolve foo` and `ping foo` work as expected. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 18 18:46:53 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-01 (717 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-18T18:41:39.752743 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683860 Title: Search domains are not considered for split-tunnelling connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1683860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
Since this bug is marked as resolved for xorg-server, I've created a new one: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1683383. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683383] [NEW] Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
Public bug reported: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1683383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610361] Re: /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
I've changed this to Confirmed because it broke the upgrade from Yakkety to Zesty for me. The upgrade process stopped after the package updating step, with this message: Upgrade complete The upgrade has completed but there were errors during the upgrade process. It didn't offer to remove obsolete packages or reboot. ** Changed in: samba (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610361 Title: /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba- ad-dc.service: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1610361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610361] Re: /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
I'll add that apparently the upgrading process did not fully complete either because `apt-get dist-upgrade` still had lots of packages left to upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610361 Title: /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba- ad-dc.service: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1610361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640450] Re: Missing debug symbols package for plasma-workspace
I'm not sure what that link points to but neither plasma-workspace-dbg nor plasma-workspace-dbgsym is installable on my system. Neither of these packages is found at http://packages.ubuntu.com/ in yakkety (search by package names). I've attached my /etc/apt/sources.list. ** Changed in: plasma-workspace (Ubuntu) Status: Invalid => New ** Attachment added: "/etc/apt/sources.list" https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640450/+attachment/4781386/+files/sources.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640450 Title: Missing debug symbols package for plasma-workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640450] [NEW] Missing debug symbols package for plasma-workspace
Public bug reported: There is no plasma-workspace-dbg package for Kubuntu 16.10 (and 17.04), which makes it difficult to diagnose problems related to plasmashell. The package is present for 16.04. Please, add the package for other releases as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: plasma-workspace 4:5.7.5-0ubuntu1 [modified: usr/bin/plasmashell] ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Nov 9 14:15:49 2016 InstallationDate: Installed on 2015-05-01 (557 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to yakkety on 2016-10-29 (11 days ago) ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety ** Description changed: There is no plasma-workspace-dbg package for Kubuntu 16.10 (and 17.04), which makes it difficult to diagnose problems related to plasmashell. The package is present for 16.04. Please, add the package for other - release as well. + releases as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: plasma-workspace 4:5.7.5-0ubuntu1 [modified: usr/bin/plasmashell] ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Nov 9 14:15:49 2016 InstallationDate: Installed on 2015-05-01 (557 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to yakkety on 2016-10-29 (11 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640450 Title: Missing debug symbols package for plasma-workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1640450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574746] [NEW] Enable support for libsoxr
Public bug reported:
I'd like to ask to enable support for libsoxr-based resamplers in the official
Ubuntu packages for pulseaudio. The upstream already supports libsoxr and
automatically detects its availability, so the only change really needed is to
add the build dependency to debian/control.
The resamplers based in libsoxr offer better quality and better performace
while introducing more delay compared to the speex resamplers that are used by
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu
16.04 but unfortunately are not enabled at build time ('pulseaudio
--dump-resample-methods' doesn't list them). I've built local packages with
libsoxr and verified that the resampler works as expected.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574746
Title:
Enable support for libsoxr
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574746/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511968] [NEW] xfce4-volumed can't bind XF86AudioRaiseVolume key
Public bug reported: When starting xfce4-volumed from the command line in non-daemon mode it fails to bind the "increase volume" multimedia key with the following error: ** (xfce4-volumed:5338): WARNING **: Binding 'XF86AudioRaiseVolume' failed! At the same time it binds the "decrease volume" key. As a result the volume can only be decreased but not increased from keyboard. xfce4-volumed is started with the following command line: xfce4-volumed --no-daemon ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xfce4-volumed 0.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 31 18:19:31 2015 InstallationDate: Installed on 2015-05-01 (182 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xfce4-volumed UpgradeStatus: Upgraded to wily on 2015-10-30 (0 days ago) ** Affects: xfce4-volumed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511968 Title: xfce4-volumed can't bind XF86AudioRaiseVolume key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1511968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
I'm having the problem in wily with xfce4-volumed - it doesn't react to multimedia volume keys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1347272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471791] Re: Thunderbird package is outdated
Yes, thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471791 Title: Thunderbird package is outdated To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1471791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471791] [NEW] Thunderbird package is outdated
Public bug reported:
Thunderbird version shipped with Ubuntu is 31.7.0, which is much older
than the current version 38.0.1 released by Mozilla. The package version
is the same in 15.04 and 15.10. Please, update the package to a more
recent Thunderbird version.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: thunderbird 1:31.7.0+build1-0ubuntu0.15.04.1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
BuildID: 20150511105107
Channel: Unavailable
CurrentDesktop: XFCE
Date: Mon Jul 6 15:23:51 2015
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini
or extensions.sqlite)
InstallationDate: Installed on 2015-05-01 (65 days ago)
InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
IpRoute:
default via 192.168.1.1 dev eth0 proto static metric 1024
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
Plugins:
Shockwave Flash - /usr/lib/mozilla/plugins/libfreshwrapper-pepperflash.so
(freshplayerplugin)
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Java(TM) Plug-in 10.80.2 - /usr/lib/jvm/java-7-oracle/jre/lib/amd64/libnpjp2.so
PrefSources:
prefs.js
[Profile]/extensions/{9533f794-00b4-4354-aa15-c2bbda6989f8}/defaults/preferences/prefs.js
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=38.0.1/20150608103712 (Out of date)
RelatedPackageVersions: freshplayerplugin 0.3.0+git20150629~webupd8~vivid
RfKill:
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471791
Title:
Thunderbird package is outdated
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1471791/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455915] Re: Windows keys not working with Logitech G15 keyboard
I have solved the problem. Apparently, the keys were disabled in the keyboard by a hardware switch, and I didn't notice that. Sorry for the noise. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455915 Title: Windows keys not working with Logitech G15 keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455915] Re: Windows keys not working with Logitech G15 keyboard
I tried the 4.1.0-040100rc6-generic and it still doesn't work. I'm attaching the output of evtest. ** Attachment added: The output of evtest. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+attachment/4410852/+files/event4.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1-rc6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455915 Title: Windows keys not working with Logitech G15 keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455915] Re: Windows keys not working with Logitech G15 keyboard
** Attachment added: xkbcomp -xkb :0 - output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+attachment/4398944/+files/xkbcomp.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455915 Title: Windows keys not working with Logitech G15 keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455915] [NEW] Windows keys not working with Logitech G15 keyboard
Public bug reported: Neither Windows key nor Context menu key work on Logitech G15 keyboard (Russian layout). I tried running xev and evtest but neither of these tools output anything when I press these keys (they do produce output when I press other keys). The keys are physically working, I verified that in Windows. Other keys, including the multimedia keys, are working. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lastique 2083 F pulseaudio /dev/snd/controlC1: lastique 2083 F pulseaudio /dev/snd/controlC3: lastique 2083 F pulseaudio /dev/snd/controlC0: lastique 2083 F pulseaudio CurrentDesktop: KDE Date: Sun May 17 16:52:05 2015 InstallationDate: Installed on 2015-05-01 (15 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug g15 logitech third-party-packages vivid winkeys ** Attachment added: dmesg log https://bugs.launchpad.net/bugs/1455915/+attachment/4398908/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455915 Title: Windows keys not working with Logitech G15 keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455915] Re: Windows keys not working with Logitech G15 keyboard
** Attachment added: setxkbmap -print output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+attachment/4398947/+files/xkbmap.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455915 Title: Windows keys not working with Logitech G15 keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
