[Desktop-packages] [Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
Answers from GStreamer bugtracker: > This very much looks like it's something much lower level than gstreamer-libav. Googling libgomp shows it's an openmp implementation used with gcc which means I imagine this issues is either some compiler or ffmpeg issue or some combination thereof. > Yeah, this is not a problem on our side. Please report this in Ubuntu against their toolchain. By the way, I guess Totem is currently broken on Ubuntu Desktop images for Raspberry Pi 4 too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 Status in GStreamer: Unknown Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/648 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 20.04 is currently broken on aarch64
Just noticed that this issue affect regular Totem video player too. And it also is still reproducible on 20.10. ** Also affects: gcc-10 (Ubuntu) Importance: Undecided Status: New ** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Summary changed: - totem-video-thumbnailer in Ubuntu 20.04 is currently broken on aarch64 + totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 ** Summary changed: - totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 + Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #648 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/648 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
*on Ubuntu 20.10 with Linux 5.8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Issue is no longer reproducible on Linux 5.8, although on 5.9 there is regression: https://bugzilla.kernel.org/show_bug.cgi?id=209469 ** Bug watch added: Linux Kernel Bug Tracker #209469 https://bugzilla.kernel.org/show_bug.cgi?id=209469 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
Also reproducible when mpv running under XWayland (due to vo=sdl usage)
finish playback and exit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Bug description:
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605
---
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode for ARM devices
It's seems like there is a progress on getting Qualcomm Venus decoder works on Snapdragon-based laptops so this feature could be useful for these laptops too: https://github.com/bm16ton/yoga-c630-linux-kernel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1799686 Title: Enable v4l2 hardware accelerated video decode for ARM devices Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium browser is capable of decoding video via v4l2 codecs. ChromeOS uses this on arm devices to achieve good performance. Patches to enable this in Linux can be found here https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0 and here https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"
Out of curiosity I tried to reproduce this on other SBC - NanoPi-M1 which also running Armbian. Interestingly, it's not reproducible on this board. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1871543 Title: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable" Status in rtkit package in Ubuntu: Confirmed Bug description: I was debugging something else and found rtkit broken on my system. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called chroot. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped privileges. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited resources. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: Resource temporarily unavailable Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time threads. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads That state is reproducible through restarts. I haven't looked any further yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 07:59:58 2020 InstallationDate: Installed on 2018-10-12 (543 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"
> Do you have other things than the kernel from outside the Ubuntu Archive? Not much, just two packages: uboot bootloader: https://apt.armbian.com/pool/main/l/linux-u-boot-nanopct4-current/linux-u-boot-current-nanopct4_20.02.7_arm64.deb board-specific configs and various tools, such as monitoring tool, installer, etc.: https://apt.armbian.com/pool/main/l/linux-focal-root-current-nanopct4/linux-focal-root-current-nanopct4_20.02.7_arm64.deb (take a peek inside to get idea). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1871543 Title: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable" Status in rtkit package in Ubuntu: Confirmed Bug description: I was debugging something else and found rtkit broken on my system. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called chroot. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped privileges. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited resources. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: Resource temporarily unavailable Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time threads. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads That state is reproducible through restarts. I haven't looked any further yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 07:59:58 2020 InstallationDate: Installed on 2018-10-12 (543 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"
I can reliably reproduce this: 1. Inside several aarch64 systemd-machined containers (with PrivateUsers=0 in nspawn conf) with focal and running Gnome Shell session (accessed via TigerVNC server). Hosts in NanoPC-T4. 2. On one bare metal NanoPC-T4 host with focal, running Gnome Shell Wayland session. No container/virtualization stuff, only bare metal. Symptoms looks the same? ~$ sudo /usr/libexec/rtkit-daemon --stderr rtkit-daemon[5786]: Successfully called chroot. rtkit-daemon[5786]: Successfully dropped privileges. rtkit-daemon[5786]: Successfully limited resources. rtkit-daemon[5786]: pthread_create failed: Resource temporarily unavailable rtkit-daemon[5786]: Demoting known real-time threads. rtkit-daemon[5786]: Demoted 0 threads. With --no-drop-privileges it works: ~$ sudo /usr/libexec/rtkit-daemon --stderr --no-drop-privileges rtkit-daemon[5781]: Successfully called chroot. rtkit-daemon[5781]: Successfully limited resources. rtkit-daemon[5781]: Running. rtkit-daemon[5781]: Canary thread running. rtkit-daemon[5781]: Watchdog thread running. However, in both cases I have to use Armbian kernel. For the record, on RPi3B running generic Ubuntu 20.04 aarch64 image (boot via UEFI) this issue is not reproducible. I can help with further debug here, or my issue is different and I have to go to Armbian forum? In the former case what exactly I need to de to help debug this? ** Changed in: rtkit (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1871543 Title: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable" Status in rtkit package in Ubuntu: Confirmed Bug description: I was debugging something else and found rtkit broken on my system. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called chroot. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped privileges. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited resources. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: Resource temporarily unavailable Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time threads. Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads That state is reproducible through restarts. I haven't looked any further yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 07:59:58 2020 InstallationDate: Installed on 2018-10-12 (543 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 764368] Re: Please add support of Infrasonic Amon
This issue is still unresolved. Also, Marcus, could you please disable bot in this two kernel reports where apport information can not be provided due to nature of the issue? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863761 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/764368 Title: Please add support of Infrasonic Amon Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Incomplete Status in alsa-lib package in Arch Linux: New Bug description: Please add support of Infrasonic Amon (ID 1a4e:7021). Infrasonic Amon use are the same chip like Tascam US-122L. Information about Tascam US-122L support in ALSA available here: http://www.pps.jussieu.fr/~smimram/tascam/ To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/764368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 941219] Re: [Acer Aspire 8930G] Speaker Sound does not mute when Headphones are connected. Ubuntu 12.04 LTS. Missing Auto-Mute Mode in alsamixer.
I don't have this hardware on hands anymore. Is anyone can check this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/941219 Title: [Acer Aspire 8930G] Speaker Sound does not mute when Headphones are connected. Ubuntu 12.04 LTS. Missing Auto-Mute Mode in alsamixer. Status in alsa-driver package in Ubuntu: Incomplete Bug description: ALSA HDA, Laptop Speaker sound does not disable with headphones connected. Laptop: Acer Aspire 8930. I installed alsa-hda-dkms-acer3830tg_0.1_all but when rebooted speaker sound disappeared but headphone sound remained. Crashed pulseaudio indicator, no where to enable disable headphone sensing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/941219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500282]
> Is there any update on this? On Wayland-enabled Firefox build (Ubuntu and Fedora provide such builds) launched with MOZ_ENABLE_WAYLAND=1 under Gnome Shell Wayland session scaling works correctly. I didn't tested other cases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1500282 Title: pixel scaling seems to be rounded to integers Status in Mozilla Firefox: Confirmed Status in Mozilla Thunderbird: New Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: Firefox adapts its highdpi settings to the value in unity-control- center. However, right now I have it set to 1.5 and firefox seems to scale it to 2.0. I.e. everything is much bigger than it should be. If I set devPixelsPerPx to 1.5 manually everything looks fine. So there must be some bug in firefox that is reading this value as an integer. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1500282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Bug watch added: Linux Kernel Bug Tracker #204237 https://bugzilla.kernel.org/show_bug.cgi?id=204237 ** Changed in: linux Importance: Medium => Unknown ** Changed in: linux Status: Invalid => Unknown ** Changed in: linux Remote watch: Linux Kernel Bug Tracker #205083 => Linux Kernel Bug Tracker #204237 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Unknown Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1:
[Desktop-packages] [Bug 1846539]
*** This bug has been marked as a duplicate of bug 204237 *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Invalid Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: irina 818 F pulseaudio /dev/snd/controlC0: irina 818 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 4 01:22:54 2019 InstallationDate: Installed on 2019-02-12 (233 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" -
[Desktop-packages] [Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
** Tags added: eoan regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 Status in ffmpeg package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
I added gcc-9 and ffmpeg to related packages because if search "libgomp.so.1: cannot allocate memory in static TLS block" in Google you will find this issue starting to appear in different program this years (such as Anaconda installer, OpenCV, PHP ImageMagick module) so I don't think this issue is isolated to Totem. However, Totem is only program where I can reliable reproduce this issue right now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 Status in ffmpeg package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] [NEW] totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
Public bug reported: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Also affects: ffmpeg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 Status in ffmpeg package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on Dell Venue 11 Pro 7140
Add Linux as affected package as known workaround require changing kernel build configuration (unset CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT). ** Summary changed: - [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on Dell Venue 11 Pro 7140 + [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Unknown Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USER
[Desktop-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on Dell Venue 11 Pro 7140
** Attachment added: "Linux 5.3.1 without CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846539/+attachment/5294054/+files/dmesg_no_sof ** Bug watch added: Linux Kernel Bug Tracker #205083 https://bugzilla.kernel.org/show_bug.cgi?id=205083 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=205083 Importance: Unknown Status: Unknown ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Unknown Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
[Desktop-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on Dell Venue 11 Pro 7140
** Attachment added: "Linux 5.3.1 with CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT=y" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846539/+attachment/5294053/+files/dmesg_sof -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Unknown Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: irina 818 F pulseaudio /dev/snd/controlC0: irina 818 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 4 01:22:54
[Desktop-packages] [Bug 1846539] [NEW] [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
Public bug reported: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: irina 818 F pulseaudio /dev/snd/controlC0: irina 818 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 4 01:22:54 2019 InstallationDate: Installed on 2019-02-12 (233 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:broadwellrt286 failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r Symptom_Card: Встроенное
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Currently I doesn't have access to hardware. I will try to check /run/usb_modeswitch/current_cfg content with latest build from PPA this Friday, or next week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
I referring to the variant with the TCL dispatcher in the first PPA. You described this version in #4 as "dispatcher-c-rewrite.patch disabled" so this is why I call it like this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Log of usb-modeswitch 2.5.2+repack0-2ubuntu2~mtrudel1 and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=3) ** Attachment added: "usb_modeswitch.log" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5287517/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Log of usb-modeswitch 2.5.2+repack0-2ubuntu2~mtrudel1 and without /usr/share/usb_modeswitch/03f0:0857 ** Attachment added: "usb_modeswitch.log" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5287516/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Log of usb-modeswitch 2.5.2+repack0-2ubuntu1 from Ubuntu eoan repository and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=3) ** Attachment added: "usb_modeswitch.log" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5287518/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Shortly, 2.5.2+repack0-2ubuntu2~mtrudel1 version does not work with or without /usr/share/usb_modeswitch/03f0:0857 I created /usr/share/usb_modeswitch/03f0:0857 with Configuration=3 specifically to check if 2.5.2+repack0-2ubuntu2~mtrudel1 can behave at least like usb-modeswitch 2.5.2+repack0-2ubuntu1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Just in case I want to clarify that I did mistake in #19 and #22 - I
totally forgot that besides configuration file I also added couple of
lines with modem id's to /lib/udev/rules.d/40-usb_modeswitch.rules:
# HP lt4210
ATTR{idVendor}=="03f0", ATTR{idProduct}=="0857", RUN+="usb_modeswitch '/%k'"
Obviously, without this two lines even usb-modeswitch with disabled
dispatcher-c-rewrite.patch will not able to switch modem mode
automatically, as nothing will run usb_modeswitch against device path.
So, I wrote this message to clarify that all usb_modeswitch runs above
and below happened with modified
/lib/udev/rules.d/40-usb_modeswitch.rules
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1800794
Title:
usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Status in usb-modeswitch package in Ubuntu:
In Progress
Bug description:
Please refer to post of usb-modeswitch developer
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827
for complete issue description.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
> i.e. it addresses the problem description in the bug summary: "usb- modeswitch can't apply Configuration=0 to Snapdragon X12 LTE". Is that correct? Yes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
So last time (#16) usb-modeswitch service failed for me because there was no configuration for this modem in usb-modeswitch-data - result log is in #20 It's possible to workaround this be creating configuration manually (#21) but version without dispatcher-c-rewrite.patch is more convenient - it configured modem even without configuration file (#19). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Log of usb-modeswitch with fixed dispatcher-c-rewrite.patch and without /usr/share/usb_modeswitch/03f0:0857 ** Attachment added: "usb_modeswitch.log" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5286995/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Log of usb-modeswitch with fixed dispatcher-c-rewrite.patch and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=0) ** Attachment added: "usb_modeswitch.log" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5286996/+files/usb_modeswitch.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Log of usb-modeswitch with disabled dispatcher-c-rewrite.patch and without /usr/share/usb_modeswitch/03f0:0857 ** Attachment added: "usb_modeswitch_2-3" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+attachment/5286994/+files/usb_modeswitch_2-3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
> Is that the same error you get when you run the usb-modeswitch version in the Ubuntu archive? Yes, same error: "usb_modeswitch_dispatcher[3587]: Could not read attribute: No such file or directory" Installed version is: 2.5.2+repack0-2ubuntu1 > Can you please run test Sure, output is: ~$ ./test File "/lib/modules/5.2.10-050210-generic/kernel/drivers/net/usb/cdc_mbim.ko" found! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
> Any chance you can test this variant too, before I ask a sponsor to upload the patch? This variant fail to apply configuration with following error: > usb_modeswitch_dispatcher[2373]: Could not read attribute: No such file or directory Probably there is other issues besides new line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
> Does this possibly address the issue you are having? Yes, I can confirm that with Configuration=0 in /usr/share/usb_modeswitch/03f0:0857 and usb-modeswitch package from ppa:gunnarhj/usb-modeswitch usb-modeswitch service automatically switch bConfigurationValue of HP lt4220 (Snapdragon X12 LTE) to 3. In result - modem works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: New Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
** Changed in: usb-modeswitch (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: New Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
>From my understating this issue boils down to not dropping new line symbol from kernel version string when function in C program check presence of cdc_mbim kernel module. It can’t find cdc_mbim kernel module because it looking in folder that doesn’t exist, so automatic changing LTE modem mode to MBIM doesn’t happen and it stays in Ethernet mode, which doesn’t work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
> Please include all the debugging information you can here
check_mbim_available function was modified like this:
check_mbim_available (void)
{
int kver_fd = -1;
ssize_t read_count;
char kversion[100];
char *cdc_mbim_module_path;
struct stat buf;
kver_fd = open(OSRELEASE_FILE, O_RDONLY);
if (kver_fd > -1) {
read_count = read(kver_fd, , 100);
if (read_count > 0) {
asprintf(_mbim_module_path, "%s/%s/%s",
MODULES_PATH,
kversion,
CDC_MBIM_DRIVER_PATH);
+modeswitch_log("\n -> Let's check cdc_mbim_module_path : %s\n",
cdc_mbim_module_path);
if (!stat(cdc_mbim_module_path, ))
goto success;
if (!stat(CDC_MBIM_SYS_PATH, ))
goto success;
}
}
free(cdc_mbim_module_path);
return 0;
success:
free(cdc_mbim_module_path);
return 1;
}
In result log which was on expired pastebin it was visible that patch
that was printed after "Let's check cdc_mbim_module_path" message
include line break. It was right after kernel version, that filled by
#define OSRELEASE_FILE "/proc/sys/kernel/osrelease"
Example:
~$ cat /proc/sys/kernel/osrelease
4.19.0-041900-generic
~$ cat /proc/sys/kernel/osrelease | hexdump
000 2e34 3931 302e 302d 3134 3039 2d30 6567
010 656e 6972 0a63
016
Problem is that string in /proc/sys/kernel/osrelease include line break
symbol, and nothing in dispatcher-c-rewrite.patch drop this new line
symbol, so when check_mbim_available trying to check if cdc_mbim kernel
module is present, it looking for "4.19.0-041900-generic\n" (\n is not
visible but it's part of the string) instead of "4.19.0-041900-generic"
folder.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1800794
Title:
usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Status in usb-modeswitch package in Ubuntu:
Incomplete
Bug description:
Please refer to post of usb-modeswitch developer
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827
for complete issue description.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04
Interestingly, I left virtual machine with not working Nautilus running, and few hours later found that Nautilus started after all. So it's not like it not working at all, it's just take few minutes/hours to show the window. I restored virtual machine backup created yesterday and this was reproducible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04
Workaround does not help me too anymore. So there is possibility that after system upgrade there was one issue, and now it's another. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04
> https://wiki.ubuntu.com/Backtrace#Already_running_programs describes how to get a stacktrace of a program hanging Attached. ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+attachment/5273536/+files/stacktrace.txt ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Changed in: firefox Importance: Medium => Unknown ** Changed in: firefox Status: Invalid => Unknown ** Changed in: firefox Remote watch: Mozilla Bugzilla #563206 => Mozilla Bugzilla #1210727 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04
Same issue here, same workaround helps. Sebastian, it's seems like Nautilus does not crash. It just start, sit there and do nothing, not even create a window, yet still running in background. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: Incomplete Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821921] Re: Nautilus upgrade 18.10 to 19.04
** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1821921 Title: Nautilus upgrade 18.10 to 19.04 Status in nautilus package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: term1# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gnome-shell-extension-desktop-icons : Depends: nautilus (>= 3.30.4) but it is not installed nautilus-share : Depends: nautilus (>= 2.10) but it is not installed ubuntu-desktop : Depends: nautilus but it is not installed ubuntu-desktop-minimal : Depends: nautilus but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). term1# apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: gir1.2-mutter-3 libdns-export1102 libgmime-3.0-0 libgsoap-2.8.60 libisc-export169 libkf5dbusaddons-bin libkf5iconthemes-bin libllvm7 libnfs11 liborcus-0.13-0 libperl5.26 libprotobuf10 libvoikko1 perl-modules-5.26 python-tdb sonnet-plugins Use 'apt autoremove' to remove them. The following additional packages will be installed: nautilus Suggested packages: gnome-sushi nautilus-extension-brasero The following NEW packages will be installed: nautilus 0 upgraded, 1 newly installed, 0 to remove and 657 not upgraded. 78 not fully installed or removed. Need to get 0 B/599 kB of archives. After this operation, 2010 kB of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: warning: files list file for package 'nautilus-data' missing; assuming package has no files currently installed dpkg: warning: files list file for package 'nautilus-dropbox' missing; assuming package has no files currently installed dpkg: warning: files list file for package 'nautilus-extension-gnome-terminal' missing; assuming package has no files currently installed (Reading database ... 213687 files and directories currently installed.) Preparing to unpack .../nautilus_1%3a3.32.0-0ubuntu1_amd64.deb ... Unpacking nautilus (1:3.32.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/nautilus_1%3a3.32.0-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libtotem-properties-page.so', which is also in package totem 3.26.2-1ubuntu3 Errors were encountered while processing: /var/cache/apt/archives/nautilus_1%3a3.32.0-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 27 10:02:55 2019 InstallationDate: Installed on 2018-10-19 (159 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1821921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Good to know. What is downside of enabling hardware acceleration in deb packages too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Termin
Issue is no longer reproducible with current gnome-shell and mutter in 18.10. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: mutter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-04-20 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Tags: third-party-packages cosmic wayland-session Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-04-20 (131 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563110]
> Or do we have to compile it ourselves from this branch? There is prebuilt packages, if you need them: https://github.com/heikomat/linux/releases By the way, is UCM from Comment 68 is recent, or there is newer version somewhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode
Daniel, should we fill separate bugreport regarding VA-API? Or, perhaps, if you understand situation better, you can fill it? Merge request: https://chromium- review.googlesource.com/c/chromium/src/+/532294 Upstream answers: https://bugs.chromium.org/p/chromium/issues/detail?id=463440#c68 https://bugs.chromium.org/p/chromium/issues/detail?id=463440#c77 "This is not a burden we want to take on, as we don't have plans to release the feature in the product, or otherwise need it for development." So, with not implemented video decoding in Firefox, here we are - patched Chromium packages in disributions seems like laptop/tablet users last resort, as upstream "don't have plans to release the feature in the product". I guess that why Chromium packages in Fedora is patched now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1799686 Title: Enable v4l2 hardware accelerated video decode Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium browser is capable of decoding video via v4l2 codecs. ChromeOS uses this on arm devices to achieve good performance. Patches to enable this in Linux can be found here https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0 and here https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode
Fedora developers enabled video decoding in their builds. Is anyone from Canonical can comments on this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1799686 Title: Enable v4l2 hardware accelerated video decode Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium browser is capable of decoding video via v4l2 codecs. ChromeOS uses this on arm devices to achieve good performance. Patches to enable this in Linux can be found here https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0 and here https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode
https://src.fedoraproject.org/rpms/chromium/c/278c62709d1dba5883c3b69047706837bb402bd7?branch=master -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1799686 Title: Enable v4l2 hardware accelerated video decode Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium browser is capable of decoding video via v4l2 codecs. ChromeOS uses this on arm devices to achieve good performance. Patches to enable this in Linux can be found here https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0 and here https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697641] Re: Chromium doesn't open OSK under GNOME Shell
Oliver, is it still works for you with current Chromium builds? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1697641 Title: Chromium doesn't open OSK under GNOME Shell Status in chromium-browser package in Ubuntu: In Progress Bug description: Other Gtk apps signal the OSK to appear when using touch as the primary navigation method. e.g. Touch in to gedit, and the osk pops up, touch in to eog and it goes away. Chromium doesn't do this (and nor does Firefox). This will be required for good 2-in-1 support. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 58.0.3029.110-0ubuntu0.16.04.1281 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: AP///wAQrHNATDUxRxAWAQSlMx14O26lo1RPnyYRUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUA/h8RAAAe/wA1OURKUDI0SkcxNUwK/ABERUxMIFUyMzEySE0K/QA4TB5TEQAKICAgICAgAOk= dpms: On modes: 1920x1080 1680x1050 1680x945 1400x1050 1400x1050 1600x900 1280x1024 1280x1024 1440x900 1440x900 1280x960 1366x768 1360x768 1280x800 1280x800 1152x864 1280x768 1280x768 1280x720 1024x768 1024x768 1024x768 1024x576 800x600 800x600 800x600 800x600 848x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0-DP-3: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-3: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAw5NgCAAAUAQOAHBB46tTllVlXiyggUFQBAQEBAQEBAQEBAQEBAQEBYB1W2FAAGDAwQEcAFZwQAAAb/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdIMi1TTEIxAIQ= dpms: On modes: 1366x768 enabled: enabled status: connected DRM.card0-VGA-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected Date: Tue Jun 13 09:54:41 2017 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2016-04-22 (416 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Load-Avg-1min: 0.27 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 4287CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=3016f766-1b5d-4550-ba62-3373b530cf42 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b'' modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1697641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800794] [NEW] usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Public bug reported: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: New Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Termin
> A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. This part of the issue was reported here: https://gitlab.gnome.org/GNOME/mutter/issues/164 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-04-20 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Tags: third-party-packages cosmic wayland-session Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-04-20 (131 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792573] Re: gnome-shell assert failure: gnome-shell: ../src/evdev-mt-touchpad.c:1541: tp_detect_thumb_while_moving: Assertion failed: "first"
Bug reported upstream: https://gitlab.freedesktop.org/libinput/libinput/issues/170 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792573 Title: gnome-shell assert failure: gnome-shell: ../src/evdev-mt- touchpad.c:1541: tp_detect_thumb_while_moving: Assertion failed: "first" Status in gnome-shell package in Ubuntu: Confirmed Status in libinput package in Ubuntu: Confirmed Bug description: Gnome Shell Wayland session crash twice while Logitech Touchpad T650 was used for scrolling. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-1ubuntu2 Uname: Linux 4.18.3-041803-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: gnome-shell: ../src/evdev-mt-touchpad.c:1541: tp_detect_thumb_while_moving: Проверочное утверждение «first» не выполнено. CurrentDesktop: GNOME Date: Fri Sep 14 20:23:37 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-04-20 (147 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: __assert_fail_base (fmt=0x7f6078627622 , assertion=0x7f6080918903 "first", file=0x7f60809187c4 "../src/evdev-mt-touchpad.c", line=1541, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f6080918903 "first", file=0x7f60809187c4 "../src/evdev-mt-touchpad.c", line=1541, function=0x7f60809191a0 "tp_detect_thumb_while_moving") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10 Title: gnome-shell assert failure: gnome-shell: ../src/evdev-mt-touchpad.c:1541: tp_detect_thumb_while_moving: Проверочное утверждение «first» не выполнено. UpgradeStatus: Upgraded to cosmic on 2018-04-20 (147 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()
I not sure what exactly crashed it, I just got similar crash on Ubuntu 18.10, that all I know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1718135 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() Status in nautilus package in Ubuntu: Confirmed Bug description: Copying files ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 10:25:22 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-10-06 (713 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5573e2a1d902 : cmpq $0x0,0x20(%rdi) PC (0x5573e2a1d902) ok source "$0x0" ok destination "0x20(%rdi)" (0x0020) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_progress_manager_has_viewers () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() UpgradeStatus: Upgraded to artful on 2017-09-14 (4 days ago) UserGroups: adm audio cdrom dialout dip fax lpadmin lxd netdev plex plugdev sambashare scanner sudo tape vboxusers video usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1718135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()
Still issue in Ubuntu 18.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1718135 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() Status in nautilus package in Ubuntu: Confirmed Bug description: Copying files ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 10:25:22 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-10-06 (713 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5573e2a1d902 : cmpq $0x0,0x20(%rdi) PC (0x5573e2a1d902) ok source "$0x0" ok destination "0x20(%rdi)" (0x0020) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_progress_manager_has_viewers () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() UpgradeStatus: Upgraded to artful on 2017-09-14 (4 days ago) UserGroups: adm audio cdrom dialout dip fax lpadmin lxd netdev plex plugdev sambashare scanner sudo tape vboxusers video usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1718135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606579] Re: Digital output has a higher priority than analog output
Lenovo Y550P-4CWI is not available anymore, so I re-verified this issue on another laptop - Acer Aspire 7560G (Radeon HD 6620G+6650M). This time I tested with Kubuntu 18,10 daily image, instead of Kubuntu 17.10. With Radeon driver digital output is disabled by default, so audio goes to internal audio adapter. Also when I enabled HDMI output manually in System Settings, it priority remain below internal audio adapter which is desired behaviour. Unfortunately, I can no longer verify if issue is present with nouveau, but let's hope it's fixed there too. For the time being, I close this report. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/606579 Title: Digital output has a higher priority than analog output Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: phonon Digital output (nVidia GT216M HDMI) has a higher priority than analog output (hda_codec: ALC272) in Ubuntu Maverick. In result after boot LiveCD/DVD on laptop (Lenovo Y550P-4CWI) user not hear any sound. Analog outputs should have higher priority by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/606579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789678] Re: X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session
*** This bug is a duplicate of bug 1790357 *** https://bugs.launchpad.net/bugs/1790357 Sure, new bugreport: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1789678 ** This bug has been marked a duplicate of private bug 1790357 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1789678 Title: X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session. I also noticed this with DRI3 (both of default modesetting DDX and intel DDX) issue is more easily reproducible than with DRI2 (intel DDX). I running Ubuntu 18.10 (latest updates) on HP Stream 7 Tablet with Intel Atom Z3735G. There was no such issue in Ubuntu 18.04 on same device. Backtrace is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789933] Re: gnome-shell crashed with SIGSEGV in shell_app_dispose() from g_object_unref() from g_hash_table_remove_node() from g_hash_table_remove_internal() from _shell_app_s
> Please try removing all of them and see if that fixes the problem. I didn't try to remove all extension, but disabled all extensions instead - issue is still reproducible. Is it sufficient? ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789933 Title: gnome-shell crashed with SIGSEGV in shell_app_dispose() from g_object_unref() from g_hash_table_remove_node() from g_hash_table_remove_internal() from _shell_app_system_notify_app_state_changed() from shell_app_state_transition() from _shell_app_remove_window() Status in gnome-shell package in Ubuntu: New Bug description: Original bugreport: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1789644 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 Uname: Linux 4.18.3-041803-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 30 23:19:18 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-04-20 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb834684b6f:mov(%rax),%rsi PC (0x7fb834684b6f) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/gnome-shell/libgnome-shell.so g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 _shell_app_system_notify_app_state_changed () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: Upgraded to cosmic on 2018-04-20 (132 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789644] Re: Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached
Hello! Thank you for looking into this bugreport! > Then tell us the ID of the newly-created bug. Sure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789933 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789644 Title: Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello! In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for me back to GDM3 when I close warning message that appear on Evolution 3.29.90 (window that inform user that he is running unstable version of Evolution). Seems like this happen only if external display attached. Dell Latitude 7285 Dock: Belkin USB-C Express Dock 3.1 HD F4U093 External display: Dell UP3017 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1789645/+attachment/5182574/+files/ProcCpuinfoMinimal.txt ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-04-20 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Tags: third-party-packages cosmic wayland-session Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-04-20 (131 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1789645/+attachment/5182573/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-04-20 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Tags: third-party-packages cosmic wayland-session Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-04-20 (131 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Termin
apport information ** Tags added: apport-collected cosmic third-party-packages wayland- session ** Description changed: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. - A also find that switch keyboard layout with default Alt+Shift cause - Opera display it's menu (seems like this is reaction to Alt like it was - pressed as separate buttong) which interrupt text typing. Issue is not - reproducible if user press Shift first, however many people used to hold - Alt first and then press Shift. + A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu9 + Architecture: amd64 + CurrentDesktop: GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-04-20 (132 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) + Package: mutter + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash + Tags: third-party-packages cosmic wayland-session + Uname: Linux 4.18.3-041803-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-04-20 (131 days ago) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1789645/+attachment/5182572/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-04-20 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Tags: third-party-packages cosmic wayland-session Uname: Linux 4.18.3-041803-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-04-20 (131 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789678] Re: X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session
Backtrace ** Attachment added: "gdb-Xorg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789678/+attachment/5182225/+files/gdb-Xorg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1789678 Title: X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session Status in xorg-server package in Ubuntu: New Bug description: Hello! X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session. I also noticed this with DRI3 (both of default modesetting DDX and intel DDX) issue is more easily reproducible than with DRI2 (intel DDX). I running Ubuntu 18.10 (latest updates) on HP Stream 7 Tablet with Intel Atom Z3735G. There was no such issue in Ubuntu 18.04 on same device. Backtrace is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789678] [NEW] X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session
Public bug reported: Hello! X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session. I also noticed this with DRI3 (both of default modesetting DDX and intel DDX) issue is more easily reproducible than with DRI2 (intel DDX). I running Ubuntu 18.10 (latest updates) on HP Stream 7 Tablet with Intel Atom Z3735G. There was no such issue in Ubuntu 18.04 on same device. Backtrace is attached. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1789678 Title: X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session Status in xorg-server package in Ubuntu: New Bug description: Hello! X.Org Server 1.20.1 crash when I attempt to enter special symbols like @ > " via onscreen keyboard Onboard in Gnome Shell Xorg session. I also noticed this with DRI3 (both of default modesetting DDX and intel DDX) issue is more easily reproducible than with DRI2 (intel DDX). I running Ubuntu 18.10 (latest updates) on HP Stream 7 Tablet with Intel Atom Z3735G. There was no such issue in Ubuntu 18.04 on same device. Backtrace is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Termin
** Description changed: Hello! - I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy - text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for - running program. This happen even when I do this inside virt-viewer - connection to virtual machine. + I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. + Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Termin
** Summary changed: - Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C interrupt for running program + Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789645] [NEW] Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C interrupt for running program
Public bug reported: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1789645 Title: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C interrupt for running program Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Hello! I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C) for running program. This happen even when I do this inside virt-viewer connection to virtual machine. A also find that switch keyboard layout with default Alt+Shift cause Opera display it's menu (seems like this is reaction to Alt like it was pressed as separate buttong) which interrupt text typing. Issue is not reproducible if user press Shift first, however many people used to hold Alt first and then press Shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789644] [NEW] Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached
Public bug reported: Hello! In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for me back to GDM3 when I close warning message that appear on Evolution 3.29.90 (window that inform user that he is running unstable version of Evolution). Seems like this happen only if external display attached. Dell Latitude 7285 Dock: Belkin USB-C Express Dock 3.1 HD F4U093 External display: Dell UP3017 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland Importance: Undecided Status: New ** No longer affects: wayland ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789644 Title: Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Hello! In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for me back to GDM3 when I close warning message that appear on Evolution 3.29.90 (window that inform user that he is running unstable version of Evolution). Seems like this happen only if external display attached. Dell Latitude 7285 Dock: Belkin USB-C Express Dock 3.1 HD F4U093 External display: Dell UP3017 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718298] Re: On Ubuntu Gnome 17.10 Caribou appear on the screen on every keyboard layout switch performed by Onboard
Not reproducible anymore with Ubuntu 18.04 and 18.10. ** Changed in: onboard (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1718298 Title: On Ubuntu Gnome 17.10 Caribou appear on the screen on every keyboard layout switch performed by Onboard Status in onboard package in Ubuntu: Invalid Bug description: Hello! When I perform keyboard layout switch by pressing left Shift and then right Shift (or right and then left) on Compact layout of Onboard, that cause Caribou to appear on the screen, every time. When I perform keyboard layout switch by selector on Gnome panel, this issue is not reproducible. This started to happen after upgrade from Ubuntu Gnome 17.04 to Ubuntu Gnome 17.10, while using Onboard packe from system repository, in both cases. Onscreen keyboard is disabled in Gnome's accessibility settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1718298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773167]
> What does the EDID contain when there is an HDMI output but cable is not plugged in? On devices with physical HDMI output get-edid return nothing (because no devices HDMI is attached). On devices without HDMI output, such as Lenovo Miix2 8, EDID contain this: [5.431895] i915 :00:02.0: HDMI-A-2: EDID is invalid: [5.431902] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431904] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431906] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431908] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431910] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431912] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431914] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [5.431916] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > It would seem more appropriate to do that already in the kernel, though. So I should fill separate report here, at freedesktop, or at kernel's bugzilla? Which component I should choice? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1773167 Title: [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a single CPU core Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Triaged Bug description: On a krez ninja 1103 laptop audio is not working; pulseaudio consumes 100% of a single CPU core. Pulseaudio log atached. According to perf, most CPU is consumed at __memset_erms. Below is the GDB stacktrace of pulseaudio. # gdb -p 1009 -batch -eval-command="thread apply all bt" [New LWP 1028] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x56318e574a30) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 205 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory. Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)): #0 0x7fe2ab063339 in _IO_str_init_static_internal (sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36 #1 0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", maxlen=, flags=1, slen=, format=0x7fe2ac698e8d "%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62 #2 0x7fe2ac6601ca in pa_vsnprintf () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7fe2ac660366 in pa_snprintf () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7fe2ac66bda8 in pa_log_levelv_meta () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #5 0x7fe2ac66b655 in pa_log_level_meta () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #6 0x7fe2a52b36ae in ?? () from /usr/lib/pulse-11.1/modules/libalsa-util.so #7 0x7fe2ac68c2a8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at pthread_create.c:463 #9 0x7fe2ab0f488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)): #0 0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x56318e574a30) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 #1 do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at sem_waitcommon.c:111 #2 0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, abstime=0x0) at sem_waitcommon.c:181 #3 0x7fe2ac68c502 in pa_semaphore_wait () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7fe2ac8cca24 in pa_asyncmsgq_send () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so #5 0x7fe2a6841119 in ?? () from /usr/lib/pulse-11.1/modules/libprotocol-native.so #6 0x7fe2ac675ee2 in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fe2a6844695 in ?? () from /usr/lib/pulse-11.1/modules/libprotocol-native.so #8 0x7fe2ac678bef in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #9 0x7fe2ac67b6ab in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #10 0x7fe2ac67ba49 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #11 0x7fe2ac67c2cf in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #14 0x7fe2ac40e530 in pa_mainloop_run () from
[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2
> Is this still an issue for 16.04 Not for 16.04.0-16.04.2 as far I remember, but still issue for 16.0.3 and 16.04.4. I guess as soon as 16.04.5 get released this issue should be harder to reproduce, just like in 18.04 now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1719038 Title: X Server crashes during log in VM since 16.04.2 Status in X.Org X server: Unknown Status in qemu package in Ubuntu: New Status in spice package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: If I change screen resolution in my VM with Kubuntu 16.04.3 and then make log off and then log on X server is crashes doesn't able me to log in. Please, look in Xorg.0.log.old for backtrace. Also the appropriate report on freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=102554 Host: Kubuntu 17.04 Linux 4.13.2 libvirt-bin 3.6.0 qemu 2.10 Guest: Kubuntu 16.04.3 Linux 4.10.0-35-generic xserver-xorg-video-qxl 0.1.4-3ubuntu3 xserver-common 1.18.4-0ubuntu0.3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 01:27:49 2017 InstallationDate: Installed on 2016-09-16 (371 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1326954]
I wonder if the fact that I use "suspend freeze" mode instead of default "suspend" mode makes a difference? https://www.freedesktop.org/software/systemd/man/sleep.conf.d.html I have to do so because modern hardware implement S0i3 instead of S3, so default mode will just won't work (tablets and laptops without S3 support will just poweroff or reboot on attempt to go into S3). > I'll analyze the logs and let you know what I find. Ok. Just to let you know, I find first unit not reliable enough, so I edited it a little bit: Removed "StopWhenUnneeded=yes" and "RemainAfterExit=yes". Replaced "=-/bin/systemctl" with "=/bin/systemctl". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]'
[Desktop-packages] [Bug 1326954]
Created attachment 134821 ModemManager 1.6.8, patched, suspend->resume cycle I was able to test it kind of ahead of time, and unfortunately this doesn't help. Log attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim),
[Desktop-packages] [Bug 1326954]
Created attachment 134822 ModemManagerHook.service I also need to mention that workaround from Commentary 16 later was modified to not only restart ModemManager, but also detach modem before suspend, and reattach it after suspend. systemd unit is attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic'
[Desktop-packages] [Bug 1326954]
> Could you apply the patch in a custom build and retry, to see if it fixes your issue? Hello! Thank you for looking into this issue! :) I tried to build version 1.6.8, but build failed: https://launchpad.net/~russianneuromancer/+archive/ubuntu/drivers/+build/13571525 It is supposed to work with version 1.6.8 or I need master? (In latter case I have no idea how to build modemmanager package.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 16 <<<<<< data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... <<<<<< Header: <<<<<< length = 16 <<<<<< type= open (0x0001) <<<<<< transaction = 1 <<<<<< Contents: <<<<<< max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >>>>>> RAW: >>>>>> length = 16 >>>>>> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 12 <<<<<< data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... <<<<<< Header: <<<<<< length = 12 <<<<<< type= close (0x0002) <<<<<< transaction = 2 [/dev/cdc-wdm0] Received message... >>>>>> RAW: >>>>>> length = 16 >>>>>> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device i
[Desktop-packages] [Bug 1326954]
In addition to Dell Venue 8 Pro 5855 tablet with Dell Wireless 5809e (Comment 13) I find same issue reproducible on Dell Wireless 5810e (Telit LN930 with 1620 firmware) with patch from Comment 23. I also find that detach/attach modem via systemd unit is sufficient, ModemManager restart seems like not necessary. Aleksander, please let us know if any additional logs or testing is required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device:
[Desktop-packages] [Bug 1326954]
Hi Any news? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own : 'unknown' - Status | lock: 'none'
[Desktop-packages] [Bug 1326954]
Thanks you once again :) Yes, with this patch build was successful. I will test it next week and will let you know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers |
[Desktop-packages] [Bug 1326954]
Created attachment 130974 mbim-proxy log (suspend -> wakeup) from EM7305 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own : 'unknown'
[Desktop-packages] [Bug 1326954]
Created attachment 130975 ModemManager (suspend -> wakeup) from EM7305 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own : 'unknown'
[Desktop-packages] [Bug 1326954]
And in case it could help someone, this workaround systemd unit helps me. With this unit connection could be established after suspend. /etc/systemd/system/ModemManagerHook.service: [Unit] Description=ModemManager sleep hook Before=sleep.target StopWhenUnneeded=yes [Service] Type=oneshot RemainAfterExit=yes ExecStart=-/bin/systemctl stop ModemManager ExecStop=-/bin/systemctl start ModemManager [Install] WantedBy=sleep.target -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168'
[Desktop-packages] [Bug 1326954]
I have same issue on Dell Venue 8 Pro 5855 tablet with Dell Wireless 5809e (Sierra Wireless AirPrime EM7305; default SWI9X15C_05.05.58.00 firmware). Please look into attached logs: 4:26 mbim-proxy and ModemManager proxy is started, then tablet was suspended 4:27 wakeup from suspended, connection is not established 4:28 second attempt to connect, also unsuccessful. mbim-proxy and ModemManager termination and following restart allowed me to successfully establish connection again. If my issue is different and I need to fill separate bugreport - please let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' |
[Desktop-packages] [Bug 608537] Re: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks
New link to upstream bugreport: https://gitlab.gnome.org/GNOME/rhythmbox/issues/557 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/608537 Title: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks Status in GStreamer: Confirmed Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Triaged Status in rhythmbox package in Debian: Confirmed Bug description: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks. It's a bit strange. There is a lot of peoples, who need support of cue sheet. There is a few open source players for Linux with proper cue sheet support (Audacious, DeaDBeeF, qmmp) - Rhythmbox and GStreamer developers can use code from this player for implement cue sheet support in Rhythmbox. Users ask Rhythmbox developers about that last five years (looks like the first time it happened here: http://www.mail-archive.com/rhythmbox-devel@gnome.org/msg02395.html ), but support of cue sheet still not implement in Rhythmbox. Even Amarok have basic cue sheet support since version 2.3. So, maybe it's a time for cooperate Rhythmbox and GStreamer developers and add cue sheet support to Rhythmbox? To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/608537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 608537] Re: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks
** Bug watch added: GNOME Bug Tracker #776613 https://bugzilla.gnome.org/show_bug.cgi?id=776613 ** Changed in: gstreamer Importance: Wishlist => Unknown ** Changed in: gstreamer Status: Invalid => Unknown ** Changed in: gstreamer Remote watch: GNOME Bug Tracker #588269 => GNOME Bug Tracker #776613 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/608537 Title: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks Status in GStreamer: Unknown Status in Rhythmbox: Confirmed Status in rhythmbox package in Ubuntu: Triaged Status in rhythmbox package in Debian: Confirmed Bug description: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks. It's a bit strange. There is a lot of peoples, who need support of cue sheet. There is a few open source players for Linux with proper cue sheet support (Audacious, DeaDBeeF, qmmp) - Rhythmbox and GStreamer developers can use code from this player for implement cue sheet support in Rhythmbox. Users ask Rhythmbox developers about that last five years (looks like the first time it happened here: http://www.mail-archive.com/rhythmbox-devel@gnome.org/msg02395.html ), but support of cue sheet still not implement in Rhythmbox. Even Amarok have basic cue sheet support since version 2.3. So, maybe it's a time for cooperate Rhythmbox and GStreamer developers and add cue sheet support to Rhythmbox? To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/608537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606579] Re: Digital output has a higher priority than analog output
Issue is still reproducible. ** Changed in: pulseaudio (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/606579 Title: Digital output has a higher priority than analog output Status in pulseaudio package in Ubuntu: New Bug description: Binary package hint: phonon Digital output (nVidia GT216M HDMI) has a higher priority than analog output (hda_codec: ALC272) in Ubuntu Maverick. In result after boot LiveCD/DVD on laptop (Lenovo Y550P-4CWI) user not hear any sound. Analog outputs should have higher priority by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/606579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718298] Re: On Ubuntu Gnome 17.10 Caribou appear on the screen on every keyboard layout switch performed by Onboard
** Tags added: artful regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1718298 Title: On Ubuntu Gnome 17.10 Caribou appear on the screen on every keyboard layout switch performed by Onboard Status in onboard package in Ubuntu: New Bug description: Hello! When I perform keyboard layout switch by pressing left Shift and then right Shift (or right and then left) on Compact layout of Onboard, that cause Caribou to appear on the screen, every time. When I perform keyboard layout switch by selector on Gnome panel, this issue is not reproducible. This started to happen after upgrade from Ubuntu Gnome 17.04 to Ubuntu Gnome 17.10, while using Onboard packe from system repository, in both cases. Onscreen keyboard is disabled in Gnome's accessibility settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1718298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM starting from Kubuntu 16.04.2
** Tags added: regression-release ** Tags added: artful zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1719038 Title: X Server crashes during log in VM starting from Kubuntu 16.04.2 Status in X.Org X server: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: If I change screen resolution in my VM with Kubuntu 16.04.3 and then make log off and then log on X server is crashes doesn't able me to log in. Please, look in Xorg.0.log.old for backtrace. Also the appropriate report on freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=102554 Host: Kubuntu 17.04 Linux 4.13.2 libvirt-bin 3.6.0 qemu 2.10 Guest: Kubuntu 16.04.3 Linux 4.10.0-35-generic xserver-xorg-video-qxl 0.1.4-3ubuntu3 xserver-common 1.18.4-0ubuntu0.3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 01:27:49 2017 InstallationDate: Installed on 2016-09-16 (371 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719038] Re: X Server crashes during login in VM 16.04.3
** Bug watch added: freedesktop.org Bugzilla #102554 https://bugs.freedesktop.org/show_bug.cgi?id=102554 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=102554 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1719038 Title: X Server crashes during login in VM 16.04.3 Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: If I change screen resolution in my VM with Kubuntu 16.04.3 and then make log off and then log on X server is crashes doesn't able me to log in. Please, look in Xorg.0.log.old for backtrace. Also the appropriate report on freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=102554 Host: Kubuntu 17.04 Linux 4.13.2 libvirt-bin 3.6.0 qemu 2.10 Guest: Kubuntu 16.04.3 Linux 4.10.0-35-generic xserver-xorg-video-qxl 0.1.4-3ubuntu3 xserver-common 1.18.4-0ubuntu0.3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 01:27:49 2017 InstallationDate: Installed on 2016-09-16 (371 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718298] [NEW] On Ubuntu Gnome 17.10 Caribou appear on the screen on every keyboard layout switch performed by Onboard
Public bug reported: Hello! When I perform keyboard layout switch by pressing left Shift and then right Shift (or right and then left) on Compact layout of Onboard, that cause Caribou to appear on the screen, every time. When I perform keyboard layout switch by selector on Gnome panel, this issue is not reproducible. This started to happen after upgrade from Ubuntu Gnome 17.04 to Ubuntu Gnome 17.10, while using Onboard packe from system repository, in both cases. Onscreen keyboard is disabled in Gnome's accessibility settings. ** Affects: onboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1718298 Title: On Ubuntu Gnome 17.10 Caribou appear on the screen on every keyboard layout switch performed by Onboard Status in onboard package in Ubuntu: New Bug description: Hello! When I perform keyboard layout switch by pressing left Shift and then right Shift (or right and then left) on Compact layout of Onboard, that cause Caribou to appear on the screen, every time. When I perform keyboard layout switch by selector on Gnome panel, this issue is not reproducible. This started to happen after upgrade from Ubuntu Gnome 17.04 to Ubuntu Gnome 17.10, while using Onboard packe from system repository, in both cases. Onscreen keyboard is disabled in Gnome's accessibility settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1718298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)
This issue could be related: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1696305 Title: High CPU usage in gnome-shell just redrawing the screen (Firefox is running) Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Even when doing nothing at all, gnome-shell uses around 70% CPU. ``` inxi -t cm Processes: CPU: % used - top 5 active 1: cpu: 68.6% command: gnome-shell pid: 1399 2: cpu: 50.4% command: Xwayland pid: 1405 3: cpu: 19.7% command: firefox pid: 3684 4: cpu: 2.4% command: gnome-shell pid: 1859 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 13603 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055 ``` It's also strange that Xwayland is active as I did choose the "normal" gnome session upon signin. ``` echo $XDG_SESSION_TYPE x11 ``` While searching I found a recent problem with AMD GPUs, but I'm using an Intel GPU ``` glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) Haswell Mobile (0xa16) Version: 17.1.0 Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0 OpenGL core profile shading language version string: 4.50 OpenGL core profile
[Desktop-packages] [Bug 1304173] Re: Xorg crashed with SIGABRT in __assert_fail_base()
** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1304173 Title: Xorg crashed with SIGABRT in __assert_fail_base() Status in xserver-xorg-video-qxl package in Ubuntu: Fix Released Bug description: Xorg crash when I open yandex.ru in Epiphany browser that running under QEMU (so LLVMpipe is in use). Distribution is Ubuntu Gnome 14.04 Beta 2 (updated). ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 8 13:47:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2014-04-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-gcQdP3/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=ru_RU.UTF-8 TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=5188726f-24e1-414f-b9bf-df75433b87da ro quiet splash vt.handoff=7 Renderer: Software Signal: 6 SourcePackage: xorg-server StacktraceTop: __assert_fail_base (fmt=0x7fd57591d718 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fd57193fcd3 "src_x1 >= 0", file=file@entry=0x7fd57193fc7d "../../src/qxl_surface.c", line=line@entry=545, function=function@entry=0x7fd57193fd90 "qxl_surface_copy") at assert.c:92 __GI___assert_fail (assertion=0x7fd57193fcd3 "src_x1 >= 0", file=0x7fd57193fc7d "../../src/qxl_surface.c", line=545, function=0x7fd57193fd90 "qxl_surface_copy") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/qxl_drv.so ?? () from /usr/lib/xorg/modules/drivers/qxl_drv.so ?? () from /usr/lib/xorg/modules/drivers/qxl_drv.so Title: Xorg crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 8 13:51:20 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual-0 Virtual-1 Virtual-2 Virtual-3 xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: qxl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1304173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
So after all nobody reported this to bugs.freedesktop.org? I also guess there is few different issues in this bugreport, so I think it's good idea to fill separate bugreport on bugs.freedesktop.org if you have very different symptoms. How to fill bugreport to bugs.freedesktop.org: https://01.org/linuxgraphics/documentation/how-report-bugs drm-tip kernel is here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in X.Org X server: New Status in xorg package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668013] Re: soffice.bin crashed with SIGSEGV in _xcb_conn_wait()
** Information type changed from Private to Public ** Description changed: LibreOffice crash on start after upgrade to 5.3.0 in Kubuntu 17.04 Beta. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: libreoffice-core 1:5.3.0~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 26 15:40:31 2017 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin ExecutableTimestamp: 1487040521 InstallationDate: Installed on 2011-04-03 (2155 days ago) InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5 - ProcCwd: /home/nikita SegvAnalysis: - Segfault happened at: 0x7ff0923ebbf6:mov%rax,0xa8(%rsp) - PC (0x7ff0923ebbf6) ok - source "%rax" ok - destination "0xa8(%rsp)" (0x7ffc6bb09ff8) not located in a known VMA region (needed writable region)! - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7ff0923ebbf6:mov%rax,0xa8(%rsp) + PC (0x7ff0923ebbf6) ok + source "%rax" ok + destination "0xa8(%rsp)" (0x7ffc6bb09ff8) not located in a known VMA region (needed writable region)! + Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 - ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 - xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 - _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6 - _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 + ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 + xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 + _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6 + _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: soffice.bin crashed with SIGSEGV in xcb_writev() UpgradeStatus: Upgraded to zesty on 2015-04-17 (680 days ago) UserGroups: adm audio cdrom dialout libvirt libvirtd lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1668013 Title: soffice.bin crashed with SIGSEGV in _xcb_conn_wait() Status in libreoffice package in Ubuntu: New Bug description: LibreOffice crash on start after upgrade to 5.3.0 in Kubuntu 17.04 Beta. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: libreoffice-core 1:5.3.0~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 26 15:40:31 2017 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin ExecutableTimestamp: 1487040521 InstallationDate: Installed on 2011-04-03 (2155 days ago) InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5 SegvAnalysis: Segfault happened at: 0x7ff0923ebbf6:mov%rax,0xa8(%rsp) PC (0x7ff0923ebbf6) ok source "%rax" ok destination "0xa8(%rsp)" (0x7ffc6bb09ff8) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: soffice.bin crashed with SIGSEGV in xcb_writev() UpgradeStatus: Upgraded to zesty on 2015-04-17 (680 days ago) UserGroups: adm audio cdrom dialout libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1668013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672003] Re: soffice.bin crashed with SIGSEGV in XQueryPointer()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1672003 Title: soffice.bin crashed with SIGSEGV in XQueryPointer() Status in libreoffice package in Ubuntu: New Bug description: LibreOffice crash on start after upgrade to 5.3.0 in Kubuntu 17.04 Beta. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: libreoffice-core 1:5.3.0~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Tue Mar 7 09:39:11 2017 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2011-04-03 (2168 days ago) InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5 Signal: 11 SourcePackage: libreoffice StacktraceTop: XQueryPointer () from /usr/lib/x86_64-linux-gnu/libX11.so.6 X11SalFrame::Init(SalFrameStyleFlags, SalX11Screen, SystemParentData*, bool) () from /usr/lib/libreoffice/program/libvclplug_genlo.so X11SalFrame::X11SalFrame(SalFrame*, SalFrameStyleFlags, SystemParentData*) () from /usr/lib/libreoffice/program/libvclplug_genlo.so ?? () from /usr/lib/libreoffice/program/libvclplug_kde4lo.so ?? () from /usr/lib/libreoffice/program/libvclplug_kde4lo.so Title: soffice.bin crashed with SIGSEGV in XQueryPointer() UpgradeStatus: Upgraded to zesty on 2015-04-17 (693 days ago) UserGroups: adm audio cdrom dialout libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1672003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672706] [NEW] onboard 1.4.1 doesn't work in Ubuntu Gnome 16.10
Public bug reported: On Ubuntu Gnome 16.10 x86_64 version 1.3.0+2221-0ppa1~yakkety is working, however after update to 1.4.1 via stable PPA, Onboard doesn't start anymore: Traceback (most recent call last): File "/usr/bin/onboard", line 36, in ob = Onboard() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 148, in __init__ self.init() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 189, in init self._init_delayed() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 225, in _init_delayed self._window = KbdWindow(self.keyboard_widget, icp) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 610, in __init__ self.restore_window_rect(startup = True) File "/usr/lib/python3/dist-packages/Onboard/WindowUtils.py", line 795, in restore_window_rect rect = self.on_restore_window_rect(rect) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1122, in on_restore_window_rect r = self.get_current_rect() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line , in get_current_rect rect = self.get_hidden_rect() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1100, in get_hidden_rect return self.get_docking_hideout_rect() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1394, in get_docking_hideout_rect area, geom = self.get_docking_monitor_rects() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1417, in get_docking_monitor_rects area = self.update_monitor_workarea(monitor) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1464, in update_monitor_workarea area = self.get_monitor_workarea(monitor) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1470, in get_monitor_workarea monitor = display.get_monitor(monitor_index) AttributeError: 'X11Display' object has no attribute 'get_monitor' ** Affects: onboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1672706 Title: onboard 1.4.1 doesn't work in Ubuntu Gnome 16.10 Status in onboard package in Ubuntu: New Bug description: On Ubuntu Gnome 16.10 x86_64 version 1.3.0+2221-0ppa1~yakkety is working, however after update to 1.4.1 via stable PPA, Onboard doesn't start anymore: Traceback (most recent call last): File "/usr/bin/onboard", line 36, in ob = Onboard() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 148, in __init__ self.init() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 189, in init self._init_delayed() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 225, in _init_delayed self._window = KbdWindow(self.keyboard_widget, icp) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 610, in __init__ self.restore_window_rect(startup = True) File "/usr/lib/python3/dist-packages/Onboard/WindowUtils.py", line 795, in restore_window_rect rect = self.on_restore_window_rect(rect) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1122, in on_restore_window_rect r = self.get_current_rect() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line , in get_current_rect rect = self.get_hidden_rect() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1100, in get_hidden_rect return self.get_docking_hideout_rect() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1394, in get_docking_hideout_rect area, geom = self.get_docking_monitor_rects() File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1417, in get_docking_monitor_rects area = self.update_monitor_workarea(monitor) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1464, in update_monitor_workarea area = self.get_monitor_workarea(monitor) File "/usr/lib/python3/dist-packages/Onboard/KbdWindow.py", line 1470, in get_monitor_workarea monitor = display.get_monitor(monitor_index) AttributeError: 'X11Display' object has no attribute 'get_monitor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1672706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664138] Re: soffice.bin crashed with SIGSEGV in ResMgr::GetLong()
Your LibreOffice partially updated. Wait for other 5.3.0 packages to get from proposed to release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1664138 Title: soffice.bin crashed with SIGSEGV in ResMgr::GetLong() Status in libreoffice package in Ubuntu: Confirmed Bug description: soffice.bin crashed with SIGSEGV in ResMgr::GetLong() ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: libreoffice-core 1:5.2.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Mon Feb 13 09:03:51 2017 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-10-13 (122 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash LD_LIBRARY_PATH= SegvAnalysis: Segfault happened at: 0x7f2ab939adf0 <_ZN6ResMgr7GetLongEPv>:mov (%rdi),%eax PC (0x7f2ab939adf0) ok source "(%rdi)" (0x55f1c6756d4b) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ResMgr::GetLong(void*) () from /usr/lib/libreoffice/program/libmergedlo.so ResMgr::ReadLong() () from /usr/lib/libreoffice/program/libmergedlo.so ImageList::ImageList(ResId const&) () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so SvFileInformationManager::GetFileImage(INetURLObject const&) () from /usr/lib/libreoffice/program/libmergedlo.so Title: soffice.bin crashed with SIGSEGV in ResMgr::GetLong() UpgradeStatus: Upgraded to zesty on 2017-01-16 (27 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1664138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586493] Re: "Expand on landscape screens" option not working in trunk
> Pull it all the way to the right to have it snap to the screen edge and > disable the aspect ratio limit, i.e. always stretch from side to side. Thanks! Will try that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1586493 Title: "Expand on landscape screens" option not working in trunk Status in Onboard: Fix Released Status in onboard package in Ubuntu: Invalid Bug description: "Expand on landscape screens" option not working in trunk, revision 2152. Ubuntu Gnome 16.04 x86_64. Gnome Shell 3.18 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1586493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
