[Bug 1976313] [NEW] GPG Key Expired
Public bug reported: I get the following error when trying to run `sudo apt update`: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal-updates Release: The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/Release.gpg The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: Some index files failed to download. They have been ignored, or old ones used instead. I'm using Ubuntu 20.04.4 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-dbgsym-keyring 2020.02.11.4 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue May 31 00:32:43 2022 Dependencies: InstallationDate: Installed on 2020-05-11 (749 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyring (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/1976313 Title: GPG Key Expired To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1976313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957992] [NEW] fcitx-dbus-watcher crashed with SIGSEGV in dbus_watch_get_enabled()
Public bug reported:
I'm using Lubuntu 20.04 Full crash report here:
https://errors.ubuntu.com/oops/4d12ba38-7579-11ec-824e-fa163ee63de6
== Stacktrace =
#0 0x7fd20b1ad0a9 in dbus_watch_get_enabled () from
/lib/x86_64-linux-gnu/libdbus-1.so.3
No symbol table info available.
#1 0x56137d9b3985 in ?? ()
No symbol table info available.
#2 0x56137d9b361d in ?? ()
No symbol table info available.
#3 0x7fd20af9f0b3 in __libc_start_main (main=0x56137d9b3400, argc=3,
argv=0x7ffde1a72068, init=, fini=,
rtld_fini=, stack_end=0x7ffde1a72058) at ../csu/libc-start.c:308
self =
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {94641711692720,
3739136921760942169, 94641711691360, 140728389279840, 0, 0,
-3738033363213367207, -3728979616013629351}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x3, 0x7ffde1a72068}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 3}}}
not_first_call =
#4 0x56137d9b368e in ?? ()
No symbol table info available.
== StacktraceAddressSignature =
/usr/bin/fcitx-dbus-watcher:11:/usr/lib/x86_64-linux-gnu/libdbus-1.so.3.19.11+220a9:/usr/bin/fcitx-dbus-watcher+985:/usr/bin/fcitx-dbus-watcher+61d:/usr/lib/x86_64-linux-gnu/libc-2.31.so+20b3:/usr/bin/fcitx-dbus-watcher+68e
== StacktraceTop =
dbus_watch_get_enabled () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? ()
?? ()
__libc_start_main (main=0x56137d9b3400, argc=3, argv=0x7ffde1a72068,
init=, fini=, rtld_fini=,
stack_end=0x7ffde1a72058) at ../csu/libc-start.c:308
?? ()
** Affects: fcitx (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/1957992
Title:
fcitx-dbus-watcher crashed with SIGSEGV in dbus_watch_get_enabled()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1957992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928580] [NEW] GIMP assertion error
Public bug reported:
```
GNU Image Manipulation Program version 2.10.18
git-describe: GIMP_2_10_16-38-gde7f04567d
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
9.3.0-8ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-offload-targets=nvptx-none,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
# Libraries #
using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.6 (compiled against version 2.64.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.44.7)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> GIMP-CRITICAL: gimp_widget_blink: assertion 'GTK_IS_WIDGET (widget)' failed
Stack trace:
```
# Stack traces obtained from PID 4251 - Thread 4251 #
[New LWP 4254]
[New LWP 4255]
[New LWP 4256]
[New LWP 4257]
[New LWP 4258]
[New LWP 4259]
[New LWP 4271]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x77a99020, fd=14) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7fb03030f340 (LWP 4251) "gimp-2.10" __libc_read (nbytes=256,
buf=0x77a99020, fd=14) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7fb02fba7700 (LWP 4254) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7fb02f3a6700 (LWP 4255) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7fb02eba5700 (LWP 4256) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7fb02cff6700 (LWP 4257) "gmain" 0x7fb031149aff in
__GI___poll (fds=0x55e4f18a12c0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7fb01700 (LWP 4258) "gdbus" 0x7fb031149aff in
__GI___poll (fds=0x55e4f18de770, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7fb00e53e700 (LWP 4259) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7fb007fff700 (LWP 4271) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (Thread 0x7fb007fff700 (LWP 4271)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fb03143f623 in g_cond_wait () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fb03193faad in () at /lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3 0x7fb03141bad1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fb03122f609 in start_thread (arg=) at
pthread_create.c:477
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140394025187072,
-7242239545136323413, 140737348470606, 140737348470607, 140737348470752,
140394025183360, 7214320746692928683, 7214212195226150059}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#5 0x7fb031156293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 7 (Thread 0x7fb00e53e700 (LWP 4259)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fb03143f623 in g_cond_wait () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x55e4f10c8d84 in
gimp_parallel_run_async_thread_func(GimpParallelRunAsyncThread*)
(thread=0x55e4f1651040 ) at
gimp-parallel.cc:378
task =
#3 0x7fb03141bad1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fb03122f609 in start_thread (arg=) at
pthread_create.c:477
[Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
I have a similar error Ign:16 http://ddebs.ubuntu.com focal-updates Release.gpg Err:17 http://ddebs.ubuntu.com focal Release.gpg The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Err:19 http://ddebs.ubuntu.com focal-proposed Release.gpg The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Hit:18 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease Reading package lists... Done E: The repository 'http://ddebs.ubuntu.com focal-updates Release' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916497] Re: PCManFM-Qt does not respect systemw-wide Qt widget style
WAIT: When I turned my computer on today, everything had the correct theme!?!?! Can anyone still reproduce this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916497 Title: PCManFM-Qt does not respect systemw-wide Qt widget style To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1916497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916497] Re: PCManFM-Qt does not respect systemw-wide Qt widget style
I changed it. Actually lximage-qt also doesn't respect the theme. ** Description changed: I wanted to have a dark theme for Lubuntu. I installed a custom GTK theme called Ultimate-Plata-Dark-3.36 which is quite dark. This only affected apps that used GTK. As per the instructions in the LXQt Appearance Configuration window, I selected the 'gtk2' Qt style after install qt5-style-plugins. Afterwards, apps such as qpdfview adopted the GTK theme. - *EXCEPT* PCManFM, which stubbornly persists in its original light theme. + *EXCEPT* PCManFM-Qt, which stubbornly persists in its original light + theme. - How do I make PCManFM respect the system Qt Widget style? + How do I make PCManFM-Qt respect the system Qt Widget style? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcmanfm-qt 0.14.1-0ubuntu3 Uname: Linux 5.9.3-050903-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Feb 22 15:52:08 2021 InstallationDate: Installed on 2020-05-11 (286 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcmanfm-qt UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916497 Title: PCManFM-Qt does not respect systemw-wide Qt widget style To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1916497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916497] [NEW] PCManFM-Qt does not respect systemw-wide Qt widget style
Public bug reported: I wanted to have a dark theme for Lubuntu. I installed a custom GTK theme called Ultimate-Plata-Dark-3.36 which is quite dark. This only affected apps that used GTK. As per the instructions in the LXQt Appearance Configuration window, I selected the 'gtk2' Qt style after install qt5-style-plugins. Afterwards, apps such as qpdfview adopted the GTK theme. *EXCEPT* PCManFM, which stubbornly persists in its original light theme. How do I make PCManFM respect the system Qt Widget style? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcmanfm-qt 0.14.1-0ubuntu3 Uname: Linux 5.9.3-050903-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Feb 22 15:52:08 2021 InstallationDate: Installed on 2020-05-11 (286 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcmanfm-qt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcmanfm-qt (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/1916497 Title: PCManFM-Qt does not respect systemw-wide Qt widget style To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1916497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902896] Re: Thunderbolt dock no longer works
Sorry I realised my thunderbolt dock probably broke. Stupid dell thing is low quality. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902896 Title: Thunderbolt dock no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1902896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902896] [NEW] Thunderbolt dock no longer works
Public bug reported: I'm using Lubuntu 20.04 on Dell XPS 13 9360. Somehow thunderbolt stopped working. I've attached the relevant output from /var/syslog. I'm using 5.4.0-52-generic. I've updated all my firmware through fwupdmgr. Briefly, the kernel complains kernel: pci :01:00.0: BAR 13: no space for [io size 0x3000] kernel: pci :01:00.0: BAR 13: failed to assign [io size 0x3000] then kernel: usb 3-1.3: config 1 has no interfaces? then kernel: xhci_hcd :39:00.0: xHCI host controller not responding, assume dead kernel: r8152 4-1.4:1.0 enxd481d70b2831: Stop submitting intr, status -108 kernel: xhci_hcd :39:00.0: HC died; cleaning up then kernel: xhci_hcd :39:00.0: Host halt failed, -19 kernel: xhci_hcd :39:00.0: Host not accessible, reset failed. then kernel: pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) kernel: pcieport :00:1c.0: AER: device [8086:9d10] error status/mask=0001/2000 kernel: pcieport :00:1c.0: AER:[ 0] RxErr ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Nov 4 16:07:31 2020 Dependencies: InstallationDate: Installed on 2020-05-11 (176 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=95de7ebe-d429-45d7-9548-0d5af627a560 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1902896/+attachment/5431066/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902896 Title: Thunderbolt dock no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1902896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891653] Re: GIMP crashes with CTRL+X in layers window
Here is a crash report: 19e0d6e4-f45a-11ea-b5cc-fa163ee63de6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891653 Title: GIMP crashes with CTRL+X in layers window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1891653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891800] Re: gnome-keyring-daemon crashes; assertion failed; (permission denied?)
Hi sebastian, I deleted the .crash file for security reasons, as you said. My error report I will send you by email. ** Attachment removed: "_usr_bin_gnome-keyring-daemon.0.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1891800/+attachment/5401943/+files/_usr_bin_gnome-keyring-daemon.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891800 Title: gnome-keyring-daemon crashes; assertion failed; (permission denied?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1891800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891800] Re: gnome-keyring-daemon crashes; assertion failed; (permission denied?)
** Description changed: + This error occurs when I first open Skype. Skype loads, but not prompt + for the keyring password occurs. After killing skype from the command + line and starting it again, everything works and I am prompted for the + keyring passw. + + (Also reported upstream here: https://gitlab.gnome.org/GNOME/gnome- + keyring/-/issues/64) + From journalctl: gnome-keyring-daemon[803]: ** - ERROR:daemon/dbus/gkd-secret-unlock.c:243:perform_next_unlock: assertion failed: (!self->current) + ERROR:daemon/dbus/gkd-secret-unlock.c:243:perform_next_unlock: assertion failed: (!self->current) From /var/crash: ProblemType: Crash Architecture: amd64 Date: Sun Aug 16 12:08:08 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/bin/gnome-keyring-daemon ExecutableTimestamp: 1583917570 ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' (full file attached) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.36.0-1ubuntu1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Aug 16 13:47:41 2020 InstallationDate: Installed on 2020-05-11 (96 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891800 Title: gnome-keyring-daemon crashes; assertion failed; (permission denied?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1891800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891800] Re: gnome-keyring-daemon crashes; assertion failed; (permission denied?)
** Summary changed: - gnome-keyring-daemon crashes (permission denied?) + gnome-keyring-daemon crashes; assertion failed; (permission denied?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891800 Title: gnome-keyring-daemon crashes; assertion failed; (permission denied?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1891800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891800] [NEW] gnome-keyring-daemon crashes; assertion failed; (permission denied?)
Public bug reported: >From journalctl: gnome-keyring-daemon[803]: ** ERROR:daemon/dbus/gkd-secret-unlock.c:243:perform_next_unlock: assertion failed: (!self->current) >From /var/crash: ProblemType: Crash Architecture: amd64 Date: Sun Aug 16 12:08:08 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/bin/gnome-keyring-daemon ExecutableTimestamp: 1583917570 ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' (full file attached) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.36.0-1ubuntu1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Aug 16 13:47:41 2020 InstallationDate: Installed on 2020-05-11 (96 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "_usr_bin_gnome-keyring-daemon.0.crash" https://bugs.launchpad.net/bugs/1891800/+attachment/5401943/+files/_usr_bin_gnome-keyring-daemon.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891800 Title: gnome-keyring-daemon crashes; assertion failed; (permission denied?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1891800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891799] [NEW] upowerd: did not recognise USB path
Public bug reported: >From my jouranlctl upowerd[1045]: did not recognise USB path /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy- USBC000:001, please report ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Aug 16 13:41:47 2020 InstallationDate: Installed on 2020-05-11 (96 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (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/1891799 Title: upowerd: did not recognise USB path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1891799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1882968] Re: ath10k_pci failed to wake target for write32
Hi Alexandre, Try it! But download the linux-firmware.deb package in case it doesn't work, Then you can just re-install the older firmware. From thedoctar On 15/8/20 8:38 pm, Alexandre Anoutchine wrote: > @thedoctar Thank you for the suggestion! > I don't really want install the newest kernel, do you think it can work > without (5.4.0-42-generic)? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891653] Re: GIMP crashes with CTRL+X in layers window
** Description changed: - I am editing a gimp .xcf file with multiple layers. When I use the - keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. I can - reliably reproduce this bug. - + I am editing a gimp .xcf file with multiple layers. When I use the keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. I can reliably reproduce this bug. + -- Here is what I get when I run gimp --debug-handlers: - using gegl copy - gimp: GEGL-WARNING: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) - eEeek! 1 GeglBuffers leaked + using gegl copy + gimp: GEGL-WARNING: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) + eEeek! 1 GeglBuffers leaked + -- + Here is what I get when I run gimp --debug-handlers --stack-trace-mode always --sync + using gegl copy + The program 'gimp' received an X Window System error. + This probably reflects a bug in the program. + The error was 'BadWindow (invalid Window parameter)'. + (Details: serial 43590 error_code 3 request_code 18 minor_code 0) + (Note to programmers: normally, X errors are reported asynchronously; +that is, you will receive the error a while after causing it. +To debug your program, run it with the --sync command line +option to change this behavior. You can then get a meaningful +backtrace from your debugger if you break on the gdk_x_error() function.) + + (script-fu:19365): LibGimpBase-WARNING **: 20:33:24.529: script-fu: + gimp_wire_read(): error + + -- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri Aug 14 15:51:01 2020 InstallationDate: Installed on 2020-05-11 (94 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891653 Title: GIMP crashes with CTRL+X in layers window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1891653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891653] Re: GIMP crashes with CTRL+X in layers window
** Description changed: I am editing a gimp .xcf file with multiple layers. When I use the keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. I can reliably reproduce this bug. + + Here is what I get when I run gimp --debug-handlers: + + `using gegl copy + gimp: GEGL-WARNING: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) + eEeek! 1 GeglBuffers leaked` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri Aug 14 15:51:01 2020 InstallationDate: Installed on 2020-05-11 (94 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I am editing a gimp .xcf file with multiple layers. When I use the keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. I can reliably reproduce this bug. Here is what I get when I run gimp --debug-handlers: - `using gegl copy - gimp: GEGL-WARNING: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) - eEeek! 1 GeglBuffers leaked` + using gegl copy + gimp: GEGL-WARNING: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) + eEeek! 1 GeglBuffers leaked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri Aug 14 15:51:01 2020 InstallationDate: Installed on 2020-05-11 (94 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891653 Title: GIMP crashes with CTRL+X in layers window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1891653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] Re: ath10k_pci failed to wake target for write32
Hi Alexandre, Yes I manually installed the latest firmware from the link above. Just extract the contents to /lib/firmware and override. I also installed the latest kernel. (currently 5.8: https://kernel.ubuntu.com/~kernel-ppa/mainline/) Albert -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891653] [NEW] GIMP crashes with CTRL+X in layers window
Public bug reported: I am editing a gimp .xcf file with multiple layers. When I use the keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. I can reliably reproduce this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri Aug 14 15:51:01 2020 InstallationDate: Installed on 2020-05-11 (94 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: I am editing a gimp .xcf file with multiple layers. When I use the - keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. + keyboard shortcut CTRL+X which should cut the layer, GIMP crashes. I can + reliably reproduce this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri Aug 14 15:51:01 2020 InstallationDate: Installed on 2020-05-11 (94 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891653 Title: GIMP crashes with CTRL+X in layers window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1891653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] Re: ath10k_pci failed to wake target for write32
This seems to have disappeared with the latest firmware (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/) & kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884943] Re: Bookmarks don't save
I think this should be documented. I've contacted the developer to suggest even removing the option and saving bookmarks as a default. Can you document this? ** Changed in: qpdfview (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884943 Title: Bookmarks don't save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdfview/+bug/1884943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884943] Re: Bookmarks don't save
I noticed that in Edit > Settings > (Behaviour) Restore Bookmarks may fix this issue. Chris Guiver, can you confirm this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884943 Title: Bookmarks don't save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdfview/+bug/1884943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884943] [NEW] Bookmarks don't save
Public bug reported: I'm running qpdfview 0.4.18 on Lubuntu 20.04. When I create a new bookmark from the menu Bookmarks > Add New Bookmark Ctrl+B, save with Ctrl+S, close the pdf and reopen, the bookmark is not saved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qpdfview 0.4.18-1build1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 24 15:43:06 2020 InstallationDate: Installed on 2020-05-11 (43 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: qpdfview UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qpdfview (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/1884943 Title: Bookmarks don't save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdfview/+bug/1884943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1882968/+attachment/5382481/+files/ProcEnviron.txt ** 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/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882968/+attachment/5382480/+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/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] Re: ath10k_pci failed to wake target for write32
apport information ** Tags added: apport-collected focal ** Description changed: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: LXQt + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-11 (29 days ago) + InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: linux (not installed) + Tags: focal + Uname: Linux 5.6.11-050611-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882968/+attachment/5382478/+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/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1882968/+attachment/5382479/+files/ProcEnviron.txt ** Description changed: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: LXQt + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-11 (29 days ago) + InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: linux (not installed) + Tags: focal + Uname: Linux 5.6.11-050611-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882968] [NEW] ath10k_pci failed to wake target for write32
Public bug reported: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "log.txt" https://bugs.launchpad.net/bugs/1882968/+attachment/5382474/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869078] Re: dhclient then ath10k firmware crashes
It seems to have disappeared when I updated dhclient to 4.4.2 ** Changed in: isc-dhcp (Ubuntu) Status: New => 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/1869078 Title: dhclient then ath10k firmware crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1869078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869078] [NEW] dhclient then ath10k firmware crashes
Public bug reported:
I had to restart so not sure if automatically generated debug-info is
relevant.
In my journalctl I get this error:
Mar 25 21:17:10 dhclient[29542]: For info, please visit
https://www.isc.org/software/dhcp/
Mar 25 21:17:10 dhclient[29542]:
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45:
numeric minute expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45:
semicolon expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease {
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 79:
expecting numeric value.
Mar 25 21:17:10 dhclient[29542]: option routers 192.168.0lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 142:
unterminated lease declaration.
...
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: firmware crashed! (guid
9bfed658-d8c1-48ad-9172-538c9219d4df)
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: qca6174 hw3.2 target
0x0503 chip_id 0x00340aff sub 1a56:1535
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1
tracing 1 dfs 0 testmode 0
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: firmware ver
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32
29eb8ca1
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A
crc32 4ac0889b
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: htt-ver 3.60 wmi-op 4 htt-op
3 cal otp max-sta 32 raw 0 hwcrypto 1
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: failed to get memcpy hi
address for firmware address 4: -16
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: failed to read firmware dump
area: -16
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: Copy Engine register dump:
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [00]: 0x00034400 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [01]: 0x00034800 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [02]: 0x00034c00 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [03]: 0x00035000 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [04]: 0x00035400 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [05]: 0x00035800 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [06]: 0x00035c00 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [07]: 0x00036000 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to receive control
response completion, polling..
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
read32 at 0x0003: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00034830: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00035430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
read32 at 0x00035444: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00035430: -110
Mar 25 21:17:12 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00034830: -110
Mar 25 21:17:13 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110)
Mar 25 21:17:13 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110
Full debug log attached.
My system froze. I was watching a move and the video stopped, audio
skipped. Hence why there are alsa complaints in the debug.
The ath10k firmware crashed and I couldn't reload.
Ubuntu 18.04.4 LTS
Linux albert-XPS-13-9360 5.5.0-050500-generic #202001262030 SMP Mon Jan
27 01:33:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
*-network
description: Wireless interface
product: QCA6174 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@:3a:00.0
logical name: wlp58s0
version: 32
serial: 9c:b6:d0:d4:9b:33
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical
wireless
configuration: broadcast=yes driver=ath10k_pci
driverversion=5.5.0-050500-generic
[Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage
The issue came back, but I reported another bug here: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1856372 ** Changed in: linux (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/1853005 Title: Wifi drops out randomly and at large bandwidth usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856372] Re: Wifi drops, particularly under load
** Changed in: linux-firmware (Ubuntu) Status: Invalid => New ** Description changed: - EDIT: sorry i realise my firmware was downgraded when ubuntu "updated" its linux-firmware package so maybe this bug is invalid. - -- - On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card, internet drops out, particularly when downloading at speeds ~1MB/s say via P2P torrent. The wifi connection (at least reported by wicd) remains active, but I cannot ping the router or access the internet. No error message is logged in journalctl after the internet drops. Details on my card, firmware and dmesg given below I'm not the only one with this issue: https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load-disconnects-on-ubuntu-18-04-with-qualcomm-atheros + On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card, + internet drops out, particularly when downloading at speeds ~1MB/s say + via P2P torrent or ooka speedtest. The wifi connection (at least + reported by wicd) remains active, but I cannot ping the router or access + the internet. No error message is logged in journalctl after the + internet drops. Details on my card, firmware and dmesg given below I'm + not the only one with this issue: + https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load- + disconnects-on-ubuntu-18-04-with-qualcomm-atheros + + The issue DOES NOT occur with wired connection (ethernet). - *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless - configuration: broadcast=yes driver=ath10k_pci driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 + configuration: broadcast=yes driver=ath10k_pci driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00140-QCARMSWPZ-1 latency=0 link=no multicast=yes wireless=IEEE 802.11 + resources: irq:135 memory:dc00-dc1f - $ dmesg | grep ath10k [2.662000] ath10k_pci :3a:00.0: enabling device ( -> 0002) [2.665299] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [2.950979] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [2.950982] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [2.951390] ath10k_pci :3a:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [3.029754] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e [3.108957] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [3.128068] ath10k_pci :3a:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [3.216750] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 [3.828149] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 14.519059] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 15.014705] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 1054.860682] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 1055.385335] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 - $ dmesg | grep pcieport [0.959817] pcieport :00:1c.0: AER: enabled with IRQ 122 [0.960121] pcieport :00:1c.4: AER: enabled with IRQ 123 [0.960397] pcieport :00:1c.5: AER: enabled with IRQ 124 [0.960657] pcieport :00:1d.0: AER: enabled with IRQ 125 [6.644709] pcieport :02:01.0: bridge window [io 0x1000-0x0fff] to [bus 04-38] add_size 1000 [6.644711] pcieport :02:02.0: bridge window [io 0x1000-0x0fff] to [bus 39] add_size 1000 [6.644713] pcieport :02:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 [6.644716] pcieport :01:00.0: bridge window [io 0x1000-0x0fff] to [bus 02-39] add_size 3000 [6.644719] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [6.644721] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [6.644723] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [6.644724] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [6.644728] pcieport :02:02.0: BAR 15: no space
[Bug 1856372] Re: Wifi drops, particularly under load
** Description changed: + EDIT: sorry i realise my firmware was downgraded when ubuntu "updated" its linux-firmware package so maybe this bug is invalid. + -- On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card, internet drops out, particularly when downloading at speeds ~1MB/s say via P2P torrent. The wifi connection (at least reported by wicd) remains active, but I cannot ping the router or access the internet. No error message is logged in journalctl after the internet drops. Details on my card, firmware and dmesg given below I'm not the only one with this issue: https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load-disconnects-on-ubuntu-18-04-with-qualcomm-atheros - - *-network -description: Wireless interface -product: QCA6174 802.11ac Wireless Network Adapter -vendor: Qualcomm Atheros -physical id: 0 -bus info: pci@:3a:00.0 -logical name: wlp58s0 -version: 32 -serial: 9c:b6:d0:d4:9b:33 -width: 64 bits -clock: 33MHz -capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless -configuration: broadcast=yes driver=ath10k_pci driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 -resources: irq:135 memory:dc00-dc1f + *-network + description: Wireless interface + product: QCA6174 802.11ac Wireless Network Adapter + vendor: Qualcomm Atheros + physical id: 0 + bus info: pci@:3a:00.0 + logical name: wlp58s0 + version: 32 + serial: 9c:b6:d0:d4:9b:33 + width: 64 bits + clock: 33MHz + capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless + configuration: broadcast=yes driver=ath10k_pci driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 + resources: irq:135 memory:dc00-dc1f - $ dmesg | grep ath10k [2.662000] ath10k_pci :3a:00.0: enabling device ( -> 0002) [2.665299] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [2.950979] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [2.950982] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [2.951390] ath10k_pci :3a:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [3.029754] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e [3.108957] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [3.128068] ath10k_pci :3a:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [3.216750] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 [3.828149] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 14.519059] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 15.014705] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 1054.860682] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 1055.385335] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 - $ dmesg | grep pcieport [0.959817] pcieport :00:1c.0: AER: enabled with IRQ 122 [0.960121] pcieport :00:1c.4: AER: enabled with IRQ 123 [0.960397] pcieport :00:1c.5: AER: enabled with IRQ 124 [0.960657] pcieport :00:1d.0: AER: enabled with IRQ 125 [6.644709] pcieport :02:01.0: bridge window [io 0x1000-0x0fff] to [bus 04-38] add_size 1000 [6.644711] pcieport :02:02.0: bridge window [io 0x1000-0x0fff] to [bus 39] add_size 1000 [6.644713] pcieport :02:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 [6.644716] pcieport :01:00.0: bridge window [io 0x1000-0x0fff] to [bus 02-39] add_size 3000 [6.644719] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [6.644721] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [6.644723] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [6.644724] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [6.644728] pcieport :02:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [6.644729] pcieport :02:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [6.644731] pcieport :02:01.0: BAR 13: no space for [io
[Bug 1856372] [NEW] Wifi drops, particularly under load
Public bug reported: On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card, internet drops out, particularly when downloading at speeds ~1MB/s say via P2P torrent. The wifi connection (at least reported by wicd) remains active, but I cannot ping the router or access the internet. No error message is logged in journalctl after the internet drops. Details on my card, firmware and dmesg given below I'm not the only one with this issue: https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load-disconnects-on-ubuntu-18-04-with-qualcomm-atheros - *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f - $ dmesg | grep ath10k [2.662000] ath10k_pci :3a:00.0: enabling device ( -> 0002) [2.665299] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [2.950979] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [2.950982] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [2.951390] ath10k_pci :3a:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [3.029754] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e [3.108957] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [3.128068] ath10k_pci :3a:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [3.216750] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 [3.828149] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 14.519059] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 15.014705] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 1054.860682] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 [ 1055.385335] ath10k_pci :3a:00.0: unsupported HTC service id: 1536 - $ dmesg | grep pcieport [0.959817] pcieport :00:1c.0: AER: enabled with IRQ 122 [0.960121] pcieport :00:1c.4: AER: enabled with IRQ 123 [0.960397] pcieport :00:1c.5: AER: enabled with IRQ 124 [0.960657] pcieport :00:1d.0: AER: enabled with IRQ 125 [6.644709] pcieport :02:01.0: bridge window [io 0x1000-0x0fff] to [bus 04-38] add_size 1000 [6.644711] pcieport :02:02.0: bridge window [io 0x1000-0x0fff] to [bus 39] add_size 1000 [6.644713] pcieport :02:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 [6.644716] pcieport :01:00.0: bridge window [io 0x1000-0x0fff] to [bus 02-39] add_size 3000 [6.644719] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [6.644721] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [6.644723] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [6.644724] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [6.644728] pcieport :02:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [6.644729] pcieport :02:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [6.644731] pcieport :02:01.0: BAR 13: no space for [io size 0x1000] [6.644732] pcieport :02:01.0: BAR 13: failed to assign [io size 0x1000] [6.644734] pcieport :02:02.0: BAR 13: no space for [io size 0x1000] [6.644735] pcieport :02:02.0: BAR 13: failed to assign [io size 0x1000] [6.644738] pcieport :02:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [6.644739] pcieport :02:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [6.644740] pcieport :02:02.0: BAR 13: no space for [io size 0x1000] [6.644741] pcieport :02:02.0: BAR 13: failed to assign [io size 0x1000] [6.644743] pcieport :02:01.0: BAR 13: no space for [io size 0x1000] [6.644744] pcieport :02:01.0: BAR 13: failed to assign [io size 0x1000] [ 27.588309] pcieport :02:01.0: bridge window [io 0x1000-0x0fff] to [bus 04-38] add_size 1000 [ 27.588315] pcieport :02:02.0: bridge window [io 0x1000-0x0fff] to [bus
[Bug 1855479] Re: gnome-shell fills syslog with stack trace messages
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Description changed: - I'm using Ubuntu 18.04.3 LTS with kernel 5.4.0-050400rc8-generic 64 bit. - I don't use network-manager-gnome but wicd, so I've not updated gnome- - control-center, which depends on network-manager-gnome. My gnome-shell - version is 3.28.4-0ubuntu18.04.2. + Reinstalling gnome-control-center and disabling network-manager seems to have fixed it. Sorry! + -- + I'm using Ubuntu 18.04.3 LTS with kernel 5.4.0-050400rc8-generic 64 bit. I don't use network-manager-gnome but wicd, so I've not updated gnome-control-center, which depends on network-manager-gnome. My gnome-shell version is 3.28.4-0ubuntu18.04.2. The messages happen when I move my mouse to the dock, which I auto-hide. Recently I've noticed there's a delay to un-hide, presumably because of the stack trace. -- Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: == Stack trace for context 0x5619a9ae0330 == Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #0 0x5619a9e76868 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f6cc8e9c808 @ 35) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #1 0x5619a9e76748 i resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f6cec0d2bc0 @ 1462) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #2 0x5619a9e766b8 i resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f6cec0d2c48 @ 100) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #3 0x5619a9e76640 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f6cec0d2cd0 @ 10) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #4 0x7ffd0c2a8c40 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f6cec0d2230 @ 386) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #5 0x5619a9e764e0 i resource:///org/gnome/shell/ui/tweener.js:244 (0x7f6cec0cf808 @ 159) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #6 0x7ffd0c2aa030 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6cec0b5de0 @ 71) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #7 0x5619a9e76460 i resource:///org/gnome/shell/ui/tweener.js:219 (0x7f6cec0cf780 @ 15) Dec 06 20:01:45 user-XPS-13-9360 gnome-shell[1653]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Dec 06 20:01:48 user-XPS-13-9360 gnome-shell[1653]: Object St.BoxLayout (0x5619abda8650), has been already finalized. Impossible to get any property from it. Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: == Stack trace for context 0x5619a9ae0330 == Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #0 0x5619a9e76460 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:691 (0x7f6cc8eab5e8 @ 46) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #1 0x7ffd0c2aa840 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6cec0b5de0 @ 71) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #2 0x7ffd0c2aa900 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:928 (0x7f6cc8eabde0 @ 931) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #3 0x7ffd0c2aa9b0 b self-hosted:914 (0x7f6cec0f12b8 @ 346) Dec 06 20:01:48 user-XPS-13-9360 gnome-shell[1653]: Object St.BoxLayout (0x5619abda8650), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: == Stack trace for context 0x5619a9ae0330 == Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #0 0x5619a9e76460 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f6cc8e9c808 @ 35) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #1 0x7ffd0c2a77d0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f6cec0d2bc0 @ 1462) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #2 0x7ffd0c2a7880 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f6cec0d2c48 @ 100) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #3 0x7ffd0c2a8060 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f6cec0d2cd0 @ 10) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #4 0x7ffd0c2a8eb0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f6cec0d2230 @ 386) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #5 0x7ffd0c2a96b0 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f6cec0cf808 @ 159) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #6 0x7ffd0c2a9dd0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6cec0b5de0 @ 71) Dec 06 20:01:48 user-XPS-13-9360
[Bug 1855479] [NEW] gnome-shell fills syslog with stack trace messages
Public bug reported: I'm using Ubuntu 18.04.3 LTS with kernel 5.4.0-050400rc8-generic 64 bit. I don't use network-manager-gnome but wicd, so I've not updated gnome- control-center, which depends on network-manager-gnome. My gnome-shell version is 3.28.4-0ubuntu18.04.2. The messages happen when I move my mouse to the dock, which I auto-hide. Recently I've noticed there's a delay to un-hide, presumably because of the stack trace. -- Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: == Stack trace for context 0x5619a9ae0330 == Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #0 0x5619a9e76868 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f6cc8e9c808 @ 35) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #1 0x5619a9e76748 i resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f6cec0d2bc0 @ 1462) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #2 0x5619a9e766b8 i resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f6cec0d2c48 @ 100) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #3 0x5619a9e76640 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f6cec0d2cd0 @ 10) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #4 0x7ffd0c2a8c40 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f6cec0d2230 @ 386) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #5 0x5619a9e764e0 i resource:///org/gnome/shell/ui/tweener.js:244 (0x7f6cec0cf808 @ 159) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #6 0x7ffd0c2aa030 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6cec0b5de0 @ 71) Dec 06 20:01:45 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #7 0x5619a9e76460 i resource:///org/gnome/shell/ui/tweener.js:219 (0x7f6cec0cf780 @ 15) Dec 06 20:01:45 user-XPS-13-9360 gnome-shell[1653]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Dec 06 20:01:48 user-XPS-13-9360 gnome-shell[1653]: Object St.BoxLayout (0x5619abda8650), has been already finalized. Impossible to get any property from it. Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: == Stack trace for context 0x5619a9ae0330 == Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #0 0x5619a9e76460 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:691 (0x7f6cc8eab5e8 @ 46) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #1 0x7ffd0c2aa840 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6cec0b5de0 @ 71) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #2 0x7ffd0c2aa900 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:928 (0x7f6cc8eabde0 @ 931) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #3 0x7ffd0c2aa9b0 b self-hosted:914 (0x7f6cec0f12b8 @ 346) Dec 06 20:01:48 user-XPS-13-9360 gnome-shell[1653]: Object St.BoxLayout (0x5619abda8650), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: == Stack trace for context 0x5619a9ae0330 == Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #0 0x5619a9e76460 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f6cc8e9c808 @ 35) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #1 0x7ffd0c2a77d0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f6cec0d2bc0 @ 1462) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #2 0x7ffd0c2a7880 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f6cec0d2c48 @ 100) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #3 0x7ffd0c2a8060 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f6cec0d2cd0 @ 10) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #4 0x7ffd0c2a8eb0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f6cec0d2230 @ 386) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #5 0x7ffd0c2a96b0 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f6cec0cf808 @ 159) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #6 0x7ffd0c2a9dd0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6cec0b5de0 @ 71) Dec 06 20:01:48 user-XPS-13-9360 org.gnome.Shell.desktop[1653]: #7 0x7ffd0c2aa550 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f6cec0cf780 @ 15) Dec 06 20:01:48 user-XPS-13-9360 gnome-shell[1653]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 Uname: Linux 5.4.0-050400rc8-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 6 20:04:04 2019
[Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage
It seems when I update *all* firmware, not just for my wifi card, the issue seems to be fixed. Thanks! ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1853005 Title: Wifi drops out randomly and at large bandwidth usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage
I updated the firmware via the instructions here: https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware It didn't help. I looked at journalctl --follow and dmesg before and after the connections drops when downloading the large file, and no error messages appear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi drops out randomly and at large bandwidth usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi drops out randomly and at large bandwidth usage
** Summary changed: - Wifi drops out at large bandwidth usage + Wifi drops out randomly and at large bandwidth usage ** Description changed: System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Problem: Wifi drops out with large bandwidth usage. For example, I had - trouble downloading a folder from a ssh server at uni. During the - download, the wifi stopped. In the log of journalctl --follow, I found - many records of the kernel complaining about an unknown pci event, which - I think is related to the wifi dropping out. The output of journalctl - --follow during the wifi drop outs is attached as the file log.txt. I - deleted all entries from Nautilus and plank.desktop. + Problem: Wifi drops out randomly and with large bandwidth usage. For + example, I had trouble downloading a folder from a ssh server at uni. + During the download, the wifi stopped. In the log of journalctl + --follow, I found many records of the kernel complaining about an + unknown pci event, which I think is related to the wifi dropping out. + The output of journalctl --follow during the wifi drop outs is attached + as the file log.txt. I deleted all entries from Nautilus and + plank.desktop. Additional notes: simply turning the wifi on and off again re- establishes the connection, but obviously irritating if I need to download lots of files from a ssh server. Furthermore, my iPad has internet connection after my Linux laptop wifi drops out, so the problem is not the router/ISP. Limiting the download speed allowed me to download from the ssh server. scp -r -l 100 user@address:~/Documents/Textbooks ./ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-70-generic 4.15.0-70.79 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 14:31:06 2019 HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722 InstallationDate: Installed on 2017-02-26 (995 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi drops out randomly and at large bandwidth usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi drops out at large bandwidth usage
** Summary changed: - Wifi randomly drops out + Wifi drops out at large bandwidth usage ** Description changed: System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Problem: Wifi randomly drops out. For example, I had trouble downloading - a folder from a ssh server at uni. During the download, the wifi - stopped. In the log of journalctl --follow, I found many records of the - kernel complaining about an unknown pci event, which I think is related - to the wifi dropping out. The output of journalctl --follow during the - wifi drop outs is attached as the file log.txt. I deleted all entries - from Nautilus and plank.desktop. + Problem: Wifi drops out with large bandwidth usage. For example, I had + trouble downloading a folder from a ssh server at uni. During the + download, the wifi stopped. In the log of journalctl --follow, I found + many records of the kernel complaining about an unknown pci event, which + I think is related to the wifi dropping out. The output of journalctl + --follow during the wifi drop outs is attached as the file log.txt. I + deleted all entries from Nautilus and plank.desktop. Additional notes: simply turning the wifi on and off again re- establishes the connection, but obviously irritating if I need to download lots of files from a ssh server. Furthermore, my iPad has internet connection after my Linux laptop wifi drops out, so the problem is not the router/ISP. - Update: limiting the download speed allowed me to download from the ssh - server. scp -r -l 100 user@address:~/Documents/Textbooks ./ + Limiting the download speed allowed me to download from the ssh server. + scp -r -l 100 user@address:~/Documents/Textbooks ./ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-70-generic 4.15.0-70.79 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 14:31:06 2019 HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722 InstallationDate: Installed on 2017-02-26 (995 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi drops out at large bandwidth usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi randomly drops out
I don't know how to update the firmware, so I followed these instructions using fwupdmgr (https://itsfoss.com/update-firmware- ubuntu/). The issue still occurs. dmesg attached. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+attachment/5307065/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi randomly drops out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi randomly drops out
Also I want to add that I have to click `Turn Off' wifi twice if that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi randomly drops out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi randomly drops out
No. I tried it on a 4.13 kernel and the problem persists. Specifically, 1. I ping my router, everything is fine. 2. I download a large file from an ssh server at my uni. The speed is very fast, 7.5 MB/s 3. After a few seconds, the internet drops out without any warning and I can no longer ping my router. I didn't check journalctl unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi randomly drops out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853005] Re: Wifi randomly drops out
** Description changed: System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Problem: Wifi randomly drops out. For example, I had trouble downloading a folder from a ssh server at uni. During the download, the wifi stopped. In the log of journalctl --follow, I found many records of the kernel complaining about an unknown pci event, which I think is related to the wifi dropping out. The output of journalctl --follow during the wifi drop outs is attached as the file log.txt. I deleted all entries from Nautilus and plank.desktop. Additional notes: simply turning the wifi on and off again re- establishes the connection, but obviously irritating if I need to download lots of files from a ssh server. Furthermore, my iPad has internet connection after my Linux laptop wifi drops out, so the problem is not the router/ISP. + Update: limiting the download speed allowed me to download from the ssh + server. scp -r -l 100 az...@ssh.itp.kit.edu:~/Documents/Textbooks ./ + + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-70-generic 4.15.0-70.79 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: albert 2011 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: albert 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 14:31:06 2019 HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722 InstallationDate: Installed on 2017-02-26 (995 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. - Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. - Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. + Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. + Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-4.15.0-70-generic N/A - linux-backports-modules-4.15.0-70-generic N/A - linux-firmware 1.173.12 + linux-restricted-modules-4.15.0-70-generic N/A + linux-backports-modules-4.15.0-70-generic N/A + linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Description changed: System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Problem: Wifi randomly drops out. For example, I had trouble downloading a folder from a ssh server at uni. During the download, the wifi stopped. In the log of journalctl --follow, I found many records of the kernel complaining about an unknown pci event, which I think is related to the wifi dropping out. The output of journalctl --follow during the wifi drop outs is attached as the file log.txt. I deleted all entries from Nautilus and plank.desktop. Additional notes: simply turning the wifi on and off again re- establishes the connection, but obviously irritating if I need to download lots of files from a ssh server. Furthermore, my iPad has internet connection after my Linux laptop wifi drops out, so the problem is not the router/ISP. Update: limiting the download speed allowed me to download from the ssh - server. scp -r -l 100 az...@ssh.itp.kit.edu:~/Documents/Textbooks ./ - + server. scp -r -l 100 user@address:~/Documents/Textbooks ./ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-70-generic 4.15.0-70.79 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS
[Bug 1853005] [NEW] Wifi randomly drops out
Public bug reported: System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Problem: Wifi randomly drops out. For example, I had trouble downloading a folder from a ssh server at uni. During the download, the wifi stopped. In the log of journalctl --follow, I found many records of the kernel complaining about an unknown pci event, which I think is related to the wifi dropping out. The output of journalctl --follow during the wifi drop outs is attached as the file log.txt. I deleted all entries from Nautilus and plank.desktop. Additional notes: simply turning the wifi on and off again re- establishes the connection, but obviously irritating if I need to download lots of files from a ssh server. Furthermore, my iPad has internet connection after my Linux laptop wifi drops out, so the problem is not the router/ISP. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-70-generic 4.15.0-70.79 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 2011 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 14:31:06 2019 HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722 InstallationDate: Installed on 2017-02-26 (995 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Output of journalctl --follow" https://bugs.launchpad.net/bugs/1853005/+attachment/5306205/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853005 Title: Wifi randomly drops out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
