[Desktop-packages] [Bug 1784779] [NEW] libglib2.0-dev cross architecture installation fails
Public bug reported: While attempting to install libglib2.0-dev for a cross-compile I ran into the following dependency issue; on x86_64 host: $ cat Dockerfile ARG BASE=ubuntu:18.04 FROM $BASE ENV DEBIAN_FRONTEND=noninteractive ARG DEBARCH=s390x RUN echo "deb [arch=$DEBARCH] http://ports.ubuntu.com/ubuntu-ports bionic main universe" >> /etc/apt/sources.list # Install package for static cross compilation RUN dpkg --add-architecture $DEBARCH; \ apt-get -y update || true ARG PACKAGE=libxml2-dev RUN apt-get -y install $PACKAGE:$DEBARCH ; \ rm -rf /var/lib/apt/lists/* $ docker build --build-arg DEBARCH=ppc64el --build-arg PACKAGE=libglib2.0-dev . Sending build context to Docker daemon 2.56kB Step 1/8 : ARG BASE=ubuntu:18.04 Step 2/8 : FROM $BASE ---> 113a43faa138 Step 3/8 : ENV DEBIAN_FRONTEND=noninteractive ---> Using cache ---> 5c2ee26240f2 Step 4/8 : ARG DEBARCH=s390x ---> Using cache ---> 83be859bd660 Step 5/8 : RUN echo "deb [arch=$DEBARCH] http://ports.ubuntu.com/ubuntu-ports bionic main universe" >> /etc/apt/sources.list ---> Using cache ---> 981e02924110 Step 6/8 : RUN dpkg --add-architecture $DEBARCH; apt-get -y update || true ---> Using cache ---> b210ae3169ec Step 7/8 : ARG PACKAGE=libuuid1 ---> Using cache ---> 25926cf2ef2b Step 8/8 : RUN apt-get -y install $PACKAGE:$DEBARCH ; rm -rf /var/lib/apt/lists/* ---> Running in 0a65b7ccea56 Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libglib2.0-dev:ppc64el : Depends: libglib2.0-0:ppc64el (= 2.56.1-2ubuntu1) but it is not going to be installed Depends: libglib2.0-bin:ppc64el (= 2.56.1-2ubuntu1) but it is not going to be installed Depends: libglib2.0-dev-bin:ppc64el (= 2.56.1-2ubuntu1) but it is not going to be installed Depends: pkg-config:ppc64el Commenting out the repo for Ubuntu ports was able to install the same package on Debian:stable without conflicts. $ docker build --build-arg BASE=debian:stable --build-arg DEBARCH=ppc64el --build-arg PACKAGE=libglib2.0-dev . Sending build context to Docker daemon 2.56kB Step 1/7 : ARG BASE=ubuntu:18.04 Step 2/7 : FROM $BASE ---> b18abcb8ff46 Step 3/7 : ENV DEBIAN_FRONTEND=noninteractive ---> Using cache ---> 83aa1773a21e Step 4/7 : ARG DEBARCH=s390x ---> Using cache ---> 7a359b6826e9 Step 5/7 : RUN dpkg --add-architecture $DEBARCH; apt-get -y update || true ---> Running in d2028c09314e Ign:1 http://cdn-fastly.deb.debian.org/debian stable InRelease Get:4 http://security.debian.org/debian-security stable/updates InRelease [94.3 kB] Get:2 http://cdn-fastly.deb.debian.org/debian stable-updates InRelease [91.0 kB] Get:5 http://security.debian.org/debian-security stable/updates/main amd64 Packages [376 kB] Get:6 http://security.debian.org/debian-security stable/updates/main ppc64el Packages [357 kB] Get:3 http://cdn-fastly.deb.debian.org/debian stable Release [118 kB] Get:7 http://cdn-fastly.deb.debian.org/debian stable-updates/main amd64 Packages [5148 B] Get:8 http://cdn-fastly.deb.debian.org/debian stable-updates/main ppc64el Packages [5092 B] Get:9 http://cdn-fastly.deb.debian.org/debian stable Release.gpg [2434 B] Get:10 http://cdn-fastly.deb.debian.org/debian stable/main amd64 Packages [7099 kB] Get:11 http://cdn-fastly.deb.debian.org/debian stable/main ppc64el Packages [6919 kB] Fetched 15.1 MB in 6s (2396 kB/s) Reading package lists... Removing intermediate container d2028c09314e ---> 845939568747 Step 6/7 : ARG PACKAGE=libuuid1 ---> Running in b4f41ec4bc8b Removing intermediate container b4f41ec4bc8b ---> ef4c946771ec Step 7/7 : RUN apt-get -y install $PACKAGE:$DEBARCH ; rm -rf /var/lib/apt/lists/* ---> Running in eabeeaf82098 Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: bzip2 dh-python file gcc-6-base:ppc64el libblkid1:ppc64el libc-dev-bin libc6:ppc64el libc6-dev:ppc64el libdpkg-perl libexpat1 libffi6 libffi6:ppc64el libfile-fcntllock-perl libgcc1:ppc64el libgdbm3 libglib2.0-0 libglib2.0-0:ppc64el libglib2.0-bin libglib2.0-data libicu57 liblocale-gettext-perl libmagic-mgc libmagic1 libmount1:ppc64el libmpdec2 libpcre16-3:ppc64el libpcre3:ppc64el libpcre3-dev:ppc64el libpcre32-3:ppc64el libpcrecpp0v5:ppc64el libperl5.24 libpython3-stdlib libpython3.5-minimal libpython3.5-stdlib libreadline7 libselinux1:ppc64el libsqlite3-0 libssl1.1 libstdc++6:ppc64el libuuid1:ppc64el libxml2 linux-libc-dev:ppc64el manpages manpages-dev mime-support netbase perl perl-modules-5.24
[Desktop-packages] [Bug 1759497] Re: 80% (512MB) of gnome-shell's memory mappings at start up are due to PulseAudio
Launchpad has imported 4 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=105779. 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 2018-03-28T07:24:17+00:00 Daniel van Vugt wrote: Created attachment 138392 gnome-shell-all-mmaps-at-startup.pdf 80% (512MB) of gnome-shell's memory mappings at start-up are due to PulseAudio. This seems excessive. Memory profile from Google heap profiler attached. Although this may not be a bug. It might just be reserved address space with very little physical memory impact...? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/3 On 2018-03-28T07:36:07+00:00 Daniel van Vugt wrote: Looks like maybe gnome-shell's use of libcanberra might be one of the triggers. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/4 On 2018-03-28T16:07:45+00:00 Tanu Kaskinen wrote: Each "mempool" in pulseaudio is 64 MB by default, and there's one mempool per client. Maybe gnome-shell has multiple connections to pulseaudio? 8 connections sounds excessive, though... Maybe the server's own mempool is visible in the client memory mapping too, so perhaps two mempools per connection are visible in the client memory map. 4 connections sounds still a bit much, though. The mempools should indeed not have full "physical" impact unless they're actually fully used. What if you set "shm-size-bytes = 33554432" (i.e. 32 MB) in /etc/pulse/client.conf and /etc/pulse/daemon.conf and reboot? Does the gnome-shell memory usage go down by 256 MB? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/6 On 2018-07-30T09:41:07+00:00 Gitlab-migration wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/92. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/10 ** Changed in: pulseaudio Status: Confirmed => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1759497 Title: 80% (512MB) of gnome-shell's memory mappings at start up are due to PulseAudio Status in PulseAudio: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in libcanberra package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: 80% (512MB) of gnome-shell's memory mappings at start-up are due to PulseAudio. This seems excessive. Memory profile from Google heap profiler attached. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1759497/+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 1772425] Re: ODT document crashes when you open it in Writer
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1772425 Title: ODT document crashes when you open it in Writer Status in libreoffice package in Ubuntu: Expired Bug description: The attached document makes LibreOffice Writer crash immediately after opening it, along with the following error message: *** Error in `/usr/lib/libreoffice/program/soffice.bin': munmap_chunk(): invalid pointer: 0x55794428ad40 *** I created this ODT file by converting a Word document with Writer; "file" tells me the original was "Composite Document File V2 Document, Little Endian, Os: Windows, Version 5.0, Code page: -535, Template: Normal, Revision Number: 1, Name of Creating Application: Microsoft Word 10.0". The original document, which was sent to me by somebody else, contained parts which seemed to work fine but when I reached the end of the file, Writer crashed. This modified ODT version I'm attaching only contains the part which makes the program crash. The document is written in Arabic, in case it makes any difference. Description: Ubuntu 17.10 Release: 17.10 libreoffice-writer: Installed: 1:5.4.6-0ubuntu0.17.10.1 Candidate: 1:5.4.6-0ubuntu0.17.10.1 Version table: *** 1:5.4.6-0ubuntu0.17.10.1 500 500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:5.4.5-0ubuntu0.17.10.5 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 1:5.4.1-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 14:09:36 2018 InstallationDate: Installed on 2017-02-13 (462 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.utf-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772425/+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 1774498] Re: Windows flash by external screen on virtual desktop change
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1774498 Title: Windows flash by external screen on virtual desktop change Status in gnome-shell package in Ubuntu: Expired Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell 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/1774498/+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 1743489] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1743489 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1743489 Title: iwlwifi firmware panic on 4.13, ucode 29.610311.0 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: On random occasion, or with certain wifi loads, iwlwifi panics with the wifi nolonger being wakeable; [ 14.548729] iwlwifi :05:00.0: loaded firmware version 29.610311.0 op_mode iwlmvm [ 14.611562] iwlwifi :05:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 [ 14.631936] iwlwifi :05:00.0: base HW address: 08:d4:0c:ef:9b:4c [ 15.094132] iwlwifi :05:00.0 wlo1: renamed from wlan0 [ 436.462157] WARNING: CPU: 3 PID: 0 at /build/linux-4LIBhY/linux-4.13.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1873 iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462159] Modules linked in: ccm rfcomm cmac bnep binfmt_misc nls_iso8859_1 amd_freq_sensitivity edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek aesni_intel snd_hda_codec_generic arc4 snd_hda_codec_hdmi aes_x86_64 crypto_simd glue_helper snd_hda_intel cryptd uvcvideo snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 snd_hwdep videobuf2_core snd_seq_midi_event joydev snd_rawmidi videodev iwlmvm input_leds hp_wmi sparse_keymap media wmi_bmof mac80211 snd_pcm btusb serio_raw btrtl snd_seq btbcm btintel k10temp fam15h_power bluetooth snd_seq_device snd_timer i2c_piix4 iwlwifi ecdh_generic cfg80211 snd soundcore shpchp i2c_scmi mac_hid hp_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4 [ 436.462351] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462417] iwl_read_prph+0x32/0x80 [iwlwifi] [ 436.462444] iwl_trans_pcie_log_scd_error+0x120/0x1e0 [iwlwifi] [ 436.462477] ? iwl_pcie_txq_inc_wr_ptr+0xf0/0xf0 [iwlwifi] [ 436.462499] iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi] [ 436.516736] iwlwifi :05:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [22, 107] HW [90, 90] FH TRB=0x05a5a5a5a [ 440.022480] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 440.022600] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 440.022607] iwlwifi :05:00.0: Scan failed! ret -5 [ 441.041965] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 441.042121] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 441.042128] iwlwifi :05:00.0: Scan failed! ret -5 [ 442.061856] iwlwifi :05:00.0: Failed to wake NIC for hcmd ...recurring Kubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 16 14:14:26 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-05 (375 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.80 metric 600 192.168.30.0/24 dev vpn_vectrobe proto kernel scope link src 192.168.30.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2018-01-15 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1743489] Re: iwlwifi firmware panic on 4.13, ucode 29.610311.0
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1743489 Title: iwlwifi firmware panic on 4.13, ucode 29.610311.0 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Bug description: On random occasion, or with certain wifi loads, iwlwifi panics with the wifi nolonger being wakeable; [ 14.548729] iwlwifi :05:00.0: loaded firmware version 29.610311.0 op_mode iwlmvm [ 14.611562] iwlwifi :05:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 [ 14.631936] iwlwifi :05:00.0: base HW address: 08:d4:0c:ef:9b:4c [ 15.094132] iwlwifi :05:00.0 wlo1: renamed from wlan0 [ 436.462157] WARNING: CPU: 3 PID: 0 at /build/linux-4LIBhY/linux-4.13.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1873 iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462159] Modules linked in: ccm rfcomm cmac bnep binfmt_misc nls_iso8859_1 amd_freq_sensitivity edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek aesni_intel snd_hda_codec_generic arc4 snd_hda_codec_hdmi aes_x86_64 crypto_simd glue_helper snd_hda_intel cryptd uvcvideo snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 snd_hwdep videobuf2_core snd_seq_midi_event joydev snd_rawmidi videodev iwlmvm input_leds hp_wmi sparse_keymap media wmi_bmof mac80211 snd_pcm btusb serio_raw btrtl snd_seq btbcm btintel k10temp fam15h_power bluetooth snd_seq_device snd_timer i2c_piix4 iwlwifi ecdh_generic cfg80211 snd soundcore shpchp i2c_scmi mac_hid hp_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4 [ 436.462351] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462417] iwl_read_prph+0x32/0x80 [iwlwifi] [ 436.462444] iwl_trans_pcie_log_scd_error+0x120/0x1e0 [iwlwifi] [ 436.462477] ? iwl_pcie_txq_inc_wr_ptr+0xf0/0xf0 [iwlwifi] [ 436.462499] iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi] [ 436.516736] iwlwifi :05:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [22, 107] HW [90, 90] FH TRB=0x05a5a5a5a [ 440.022480] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 440.022600] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 440.022607] iwlwifi :05:00.0: Scan failed! ret -5 [ 441.041965] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 441.042121] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 441.042128] iwlwifi :05:00.0: Scan failed! ret -5 [ 442.061856] iwlwifi :05:00.0: Failed to wake NIC for hcmd ...recurring Kubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 16 14:14:26 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-05 (375 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.80 metric 600 192.168.30.0/24 dev vpn_vectrobe proto kernel scope link src 192.168.30.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2018-01-15 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743489/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version:
[Desktop-packages] [Bug 1245473]
FYI the bug may be temporarily fixed on Ubuntu 16.04 LTS (with HWE), Ubuntu 18.04 LTS (and Mint 19) using packages from my PPA ( https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys or " ppa:nrbrtx/xorg-hotkeys " ). It contains patched Xorg (with patch from kyak - https://aur.archlinux.org/packages/xorg-server-bug865/ ). Thank you very much again, kyak! And it is unbelievable that we need to patch core graphical system component by ourselves to use traditional keyboard shortcuts ... -- 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: Confirmed 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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1583801]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193. -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1784633] Re: workspace side selector not properly rendered
Firstly please check that you are not using any gnome-shell extensions as extensions tend to cause a large number of bugs. If the problem persists without extensions then please report the bug to the shell developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the ID of the new bug. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1784633 Title: workspace side selector not properly rendered Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu to 18.04 the workspace selector, show on the side of the shell is not properly rendered. The panel takes the whole right side, independent from the number of workspaces I chose and the colored border around the active one is offset. The first time I open the shell the border highlight the proper box, the is set to the top left corner of the panel. I am attaching a picture showing the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 31 09:57:01 2018 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2016-07-02 (758 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-07-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784633/+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 1784671] Re: Keeping Alt+Space pressed shows the window menu and then minimizes the window
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Tags added: cosmic ** Tags added: 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/1784671 Title: Keeping Alt+Space pressed shows the window menu and then minimizes the window Status in gnome-shell package in Ubuntu: Confirmed Bug description: To reproduce: Open a couple of windows Press Alt+Space and keep it pressed Expected results: The window menu opens and nothing else happens Current behavior: The window menu opens The window is minimized The window menu of the following window is open The window is minized ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784671/+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 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
This bug was fixed in the package mutter - 3.28.3-2 --- mutter (3.28.3-2) unstable; urgency=medium * Team upload [ Iain Lane ] * debian/gbp.conf: Set the upstream branch to upstream/3.28.x, since we've branched for experimental now. [ Marco Trevisan (Treviño) ] * d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch: - Avoid crashing when warning about wrongly set crtc mode (LP: #1754949) * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch: - Don't crash if drmModeGetResources returns NULL (LP: #1767956) * d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch: - Always update monitor in wayland, avoiding crash (LP: #1784398) * d/p/monitor-manager-Filter-out-low-screen-resolutions.patch: - Don't return screen resolutions that can't be applied (LP: #1772831) * d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch: - Don't crash if a modal dialog closes while being dragged (LP: #1422253) * d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch: - Don't try to use an invalid monitor mode to figure out scaling (LP: #1723615) [ Simon McVittie ] * Sort patch series in upstream order, with patches applied upstream first * d/copyright: Remove obsolete FSF postal addresses * Standards-Version: 4.1.5 (no changes required) * Set Rules-Requires-Root to no * Update symbols file -- Simon McVittie Tue, 31 Jul 2018 15:35:03 +0100 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+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 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
This bug was fixed in the package mutter - 3.28.3-2 --- mutter (3.28.3-2) unstable; urgency=medium * Team upload [ Iain Lane ] * debian/gbp.conf: Set the upstream branch to upstream/3.28.x, since we've branched for experimental now. [ Marco Trevisan (Treviño) ] * d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch: - Avoid crashing when warning about wrongly set crtc mode (LP: #1754949) * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch: - Don't crash if drmModeGetResources returns NULL (LP: #1767956) * d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch: - Always update monitor in wayland, avoiding crash (LP: #1784398) * d/p/monitor-manager-Filter-out-low-screen-resolutions.patch: - Don't return screen resolutions that can't be applied (LP: #1772831) * d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch: - Don't crash if a modal dialog closes while being dragged (LP: #1422253) * d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch: - Don't try to use an invalid monitor mode to figure out scaling (LP: #1723615) [ Simon McVittie ] * Sort patch series in upstream order, with patches applied upstream first * d/copyright: Remove obsolete FSF postal addresses * Standards-Version: 4.1.5 (no changes required) * Set Rules-Requires-Root to no * Update symbols file -- Simon McVittie Tue, 31 Jul 2018 15:35:03 +0100 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() Status in mutter package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/130 https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339 --- This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either. What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen. So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two). Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat). Either way is a bug because the session should survive monitor shenanigans... :-) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 14 15:39:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-30 (75 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fae20ab44a0 : mov0x8(%rdi),%eax PC (0x7fae20ab44a0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1784671] Re: Keeping Alt+Space pressed shows the window menu and then minimizes the window
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/1784671 Title: Keeping Alt+Space pressed shows the window menu and then minimizes the window Status in gnome-shell package in Ubuntu: Confirmed Bug description: To reproduce: Open a couple of windows Press Alt+Space and keep it pressed Expected results: The window menu opens and nothing else happens Current behavior: The window menu opens The window is minimized The window menu of the following window is open The window is minized ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784671/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
Chris Guiver, you may need to use: sudo ubuntu-bug /var/crash/FILENAME.crash when filing crash reports in order for the upload/uploaded files to be generated, and, in turn, to get the errors reported successfully. Given the reproducibility of the crash, and how you are using the latest Ubuntu release, I'll mark this Triaged for now, and an xorg developer may further review. ** Changed in: xorg (Ubuntu) Status: Incomplete => Triaged -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Triaged Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu
Someone (Julian, Alexey?) please open an upstream bug for this problem at: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new ID. Dylan: If you get an empty space then please use bug 1774957 instead. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- 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/1755986 Title: WiFi icon / settings gone from user menu Status in gnome-shell package in Ubuntu: Incomplete Bug description: Recently, in the GNOME session, the WiFi icon vanished, and all that I get is the icon for connected network, which is odd. My other machine does not even seem to get that icon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 06:59:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell 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/1755986/+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 1784595] Re: takes forever to boot
** Package changed: xorg (Ubuntu) => 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/1784595 Title: takes forever to boot Status in Ubuntu: New Bug description: I apologise I really have no idea, this report was generated automatically. I resized some partitions and merged some partitions. I then went through a "Grub Rescue>" to get up and running again. the system now takes about 3 minutes to get to the login screen. I updated and installed grub as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jul 31 19:34:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fb01] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GF108M [GeForce GT 630M] [1179:fb01] InstallationDate: Installed on 2018-07-13 (17 days ago) InstallationMedia: Robolinux_9.3 16.04 - Release amd64 MachineType: TOSHIBA Satellite P850 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=fd6d67e8-fc11-4624-b9a6-3cd136a622e4 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: 6.70 dmi.board.asset.tag: * dmi.board.name: QFKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr6.70:bd02/20/2013:svnTOSHIBA:pnSatelliteP850:pvrPSPKFA-049001:rvnTOSHIBA:rnQFKAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite P850 dmi.product.version: PSPKFA-049001 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 1 05:03:53 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1784595/+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 1390474]
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=55a25246ee80aa950bf27f811c0cc176d0821a4e
pulseaudio does not support non-interlaved mode
static void check_access(snd_pcm_t *pcm_handle, snd_pcm_hw_params_t *hwparams,
bool use_mmap) {
if ((use_mmap && !snd_pcm_hw_params_test_access(pcm_handle, hwparams,
SND_PCM_ACCESS_MMAP_INTERLEAVED)) ||
!snd_pcm_hw_params_test_access(pcm_handle, hwparams,
SND_PCM_ACCESS_RW_INTERLEAVED))
pa_log_error("Weird, PCM claims to support interleaved access, but
snd_pcm_hw_params_set_access() 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/1390474
Title:
"Volume element PCM has 6 channels. That's too much!" - PA doesn't
support elements with more than two channels
Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the
error "Volume element PCM has 6 channels. That's too much! I can't handle
that!" and the card fails to show up in Sound Settings.
Everything is fine with 24/48 mode (2 channels).
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1390474]
(In reply to Tanu Kaskinen from comment #39) > The log shows that you're not using module-udev-detect. I don't know if > that's why things stopped working, but that would anyway be the first thing > to fix. Debian changed the packaging so that "pulseaudio-module-udev" is now > a separate package. You have probably disabled automatic installation of > recommended packages, because by default that package should get installed > automatically. Thanks a lot! My system really didn't install module-udev-detect (package pulseaudio-module-udev in debian stretch/testing). Now it works again! -- 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/1390474 Title: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error "Volume element PCM has 6 channels. That's too much! I can't handle that!" and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
** Description changed: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. 67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 166. 68 May 22 09:37:39 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session opened for user guiverc by (uid=0) 69 May 22 09:37:39 d960-ubu2 systemd-logind[1108]: New session 178 of user guiverc. 70 May 22 09:38:11 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out
[Desktop-packages] [Bug 1390474]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/457. -- 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/1390474 Title: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error "Volume element PCM has 6 channels. That's too much! I can't handle that!" and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1783662] Re: Xorg server crashing on boot "Failing initialization of X screen 0"
*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 ** Description changed: + UPDATE: The cause of this issue is not the fault of Ubuntu or the xorg- + server. This crash occurs when the system RAM is experiencing problems. + I have managed to fix this issue by readjusting one of my RAM chips. + + - + Ubuntu version: Ubuntu 18.04 LTS - - I have recently been having a problem with my desktop completely locking up (no input is accepted) after a few minutes of usage. Every time I restarted my PC, the time it took to freeze got shorter and shorter until GDM just refused to load on startup (I couldn't even login). I Eventually got stuck on the screen where it shows services starting with their status with the last item being "[ OK ] Started GNOME Display Manager". + I have recently been having a problem with my desktop completely locking + up (no input is accepted) after a few minutes of usage. Every time I + restarted my PC, the time it took to freeze got shorter and shorter + until GDM just refused to load on startup (I couldn't even login). I + Eventually got stuck on the screen where it shows services starting with + their status with the last item being "[ OK ] Started GNOME Display + Manager". I started having this problem just a few days ago. Prior to these freezing issues my installation was working perfectly, buttery smooth. The only major thing that I did that may be causing this issue is my Oculus Rift that I left plugged into my PC. After leaving my PC on the services screen all night, it actually unfroze and displayed a stack trace. Unfortunately, I don't have that stack trace. However, I have posted the Xorg.0.log below which may be relevant. Since, I have been able to recover my PC from the freezing issues. After the services screen disappeared and a stack trace displayed, I was able to access a terminal session with Ctrl+Alt+F2 and run the command "sudo apt purge nvidia*". * /var/log/Xorg.0.log * [ 1165.010] (--) Log file renamed from "/var/log/Xorg.pid-19451.log" to "/var/log/Xorg.0.log" - [ 1165.011] + [ 1165.011] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 1165.011] X Protocol Version 11, Revision 0 [ 1165.011] Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu [ 1165.011] Current Operating System: Linux austin-Z87-DS3H 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 [ 1165.011] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=c512947f-950a-4c87-99a0-9b7b6c9d6e68 ro quiet splash vt.handoff=1 [ 1165.011] Build Date: 13 April 2018 08:07:36PM - [ 1165.011] xorg-server 2:1.19.6-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) + [ 1165.011] xorg-server 2:1.19.6-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) [ 1165.011] Current version of pixman: 0.34.0 [ 1165.011] Before reporting problems, check http://wiki.x.org - to make sure that you have the latest version. + to make sure that you have the latest version. [ 1165.011] Markers: (--) probed, (**) from config file, (==) default setting, - (++) from command line, (!!) notice, (II) informational, - (WW) warning, (EE) error, (NI) not implemented, (??) unknown. + (++) from command line, (!!) notice, (II) informational, + (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1165.011] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 24 23:24:11 2018 [ 1165.011] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1165.011] (==) No Layout section. Using the first Screen section. [ 1165.011] (==) No screen section available. Using defaults. [ 1165.011] (**) |-->Screen "Default Screen Section" (0) [ 1165.011] (**) | |-->Monitor "" [ 1165.011] (==) No monitor specified for screen "Default Screen Section". - Using a default monitor configuration. + Using a default monitor configuration. [ 1165.011] (==) Automatically adding devices [ 1165.011] (==) Automatically enabling devices [ 1165.011] (==) Automatically adding GPU devices [ 1165.011] (==) Automatically binding GPU devices [ 1165.011] (==) Max clients allowed: 256, resource mask: 0x1f [ 1165.011] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1165.011] Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 1165.011] Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 1165.011] Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 1165.011] Entry
[Desktop-packages] [Bug 1390474] Re: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels
** Changed in: pulseaudio Status: Fix Released => Unknown -- 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/1390474 Title: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error "Volume element PCM has 6 channels. That's too much! I can't handle that!" and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1251127] Re: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] Pulseaudio fails to detect card
** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/1251127 Title: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] Pulseaudio fails to detect card Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Incomplete Bug description: lsb_release -rd: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy pkgname: pulseaudio: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://ftp.nluug.nl/os/Linux/distr/ubuntu/ trusty/main i386 Packages 500 http://ftp.tudelft.nl/archive.ubuntu.com/ saucy/main i386 Packages 100 /var/lib/dpkg/status 1:3.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cschilder 2392 F mixer_applet2 Date: Thu Nov 14 07:35:59 2013 InstallationDate: Installed on 2013-11-01 (12 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Title: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: Upgraded to trusty on 2013-11-01 (12 days ago) dmi.bios.date: 01/23/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.10 dmi.board.asset.tag: CZC3211FPH dmi.board.name: 2ADE dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.0 dmi.chassis.asset.tag: CZC3211FPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.10:bd01/23/2013:svnHewlett-Packard:pnHPCompaqPro4300SFFPC:pvr:rvnHewlett-Packard:rn2ADE:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Compaq Pro 4300 SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1251127/+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 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Released Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1251127]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/426. -- 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/1251127 Title: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] Pulseaudio fails to detect card Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Incomplete Bug description: lsb_release -rd: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy pkgname: pulseaudio: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://ftp.nluug.nl/os/Linux/distr/ubuntu/ trusty/main i386 Packages 500 http://ftp.tudelft.nl/archive.ubuntu.com/ saucy/main i386 Packages 100 /var/lib/dpkg/status 1:3.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic i686 ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cschilder 2392 F mixer_applet2 Date: Thu Nov 14 07:35:59 2013 InstallationDate: Installed on 2013-11-01 (12 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Title: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: Upgraded to trusty on 2013-11-01 (12 days ago) dmi.bios.date: 01/23/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.10 dmi.board.asset.tag: CZC3211FPH dmi.board.name: 2ADE dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.0 dmi.chassis.asset.tag: CZC3211FPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.10:bd01/23/2013:svnHewlett-Packard:pnHPCompaqPro4300SFFPC:pvr:rvnHewlett-Packard:rn2ADE:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Compaq Pro 4300 SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1251127/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
fyi: looking at the wiki, /etc/gdm3/custom.conf now has Enable=true (it was commented out sorry) "Reporting a crash in the stable release" may not apply, but I couldn't find a problem_types (only mentioned this as I noted you were last wiki editor; thank you!) Thank you for link - appreciated. I still get nothing since 11-july on https://errors.ubuntu.com/user/ceaac5c412433432f0beca83292fc33804be2fdae3b13b7fc7185e6a52d5fd6941294dff354c0cc3a5000fce6202e51c04e867a10ca60bb60b3682028253f96e (I checked the ID; and copied it twice into browser from `sudo cat /var/lib/whoopsie/whoopsie-id` getting same result) Thanks Christopher - I do appreciate your help (hopefully I'm learning slowly!) -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Incomplete Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26
[Desktop-packages] [Bug 1390474]
The log shows that you're not using module-udev-detect. I don't know if that's why things stopped working, but that would anyway be the first thing to fix. Debian changed the packaging so that "pulseaudio-module- udev" is now a separate package. You have probably disabled automatic installation of recommended packages, because by default that package should get installed automatically. -- 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/1390474 Title: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error "Volume element PCM has 6 channels. That's too much! I can't handle that!" and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1390474]
Hi, I'm not sure if this is 100% the same issue, but my problems started again when Debian upgraded from pulseaudio 8 to 9 recently. Even though I still use tsched=0, I hear huge amounts of clicks and pops while playing back (everything sounds like a very old vinyl recording now...). Enabling tsched makes no difference, in fact I think that it is still of even though I tried tsched=1. I'll attach the verbose log. -- 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/1390474 Title: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error "Volume element PCM has 6 channels. That's too much! I can't handle that!" and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1390474]
http://pastebin.com/CzQQhvET -- 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/1390474 Title: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error "Volume element PCM has 6 channels. That's too much! I can't handle that!" and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1390474]
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/rme9652/hdsp.c
static struct snd_pcm_hardware snd_hdsp_capture_subinfo =
{
.info = (SNDRV_PCM_INFO_MMAP |
SNDRV_PCM_INFO_MMAP_VALID |
SNDRV_PCM_INFO_NONINTERLEAVED |
SNDRV_PCM_INFO_SYNC_START),
#ifdef SNDRV_BIG_ENDIAN
.formats = SNDRV_PCM_FMTBIT_S32_BE,
#else
.formats = SNDRV_PCM_FMTBIT_S32_LE,
#endif
.rates =(SNDRV_PCM_RATE_32000 |
SNDRV_PCM_RATE_44100 |
SNDRV_PCM_RATE_48000 |
SNDRV_PCM_RATE_64000 |
SNDRV_PCM_RATE_88200 |
SNDRV_PCM_RATE_96000),
.rate_min = 32000,
.rate_max = 96000,
.channels_min = 5,
.channels_max = HDSP_MAX_CHANNELS,
.buffer_bytes_max = HDSP_CHANNEL_BUFFER_BYTES * HDSP_MAX_CHANNELS,
.period_bytes_min = (64 * 4) * 10,
.period_bytes_max = (8192 * 4) * HDSP_MAX_CHANNELS,
.periods_min = 2,
.periods_max = 2,
.fifo_size =0
};
only support 2 periods and non-interleaved access mode
pulseaudio cannot use 4 fragments
this mean one period of channel 1 , follow by one period of channel 2
,..., one period of channel n
seem has flag to control the precision of hw pointer
static snd_pcm_uframes_t hdsp_hw_pointer(struct hdsp *hdsp)
{
int position;
position = hdsp_read(hdsp, HDSP_statusRegister);
if (!hdsp->precise_ptr)
return (position & HDSP_BufferID) ? (hdsp->period_bytes / 4) :
0;
position &= HDSP_BufferPositionMask;
position /= 4;
position &= (hdsp->period_bytes/2) - 1;
return position;
}
--
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/1390474
Title:
"Volume element PCM has 6 channels. That's too much!" - PA doesn't
support elements with more than two channels
Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the
error "Volume element PCM has 6 channels. That's too much! I can't handle
that!" and the card fails to show up in Sound Settings.
Everything is fine with 24/48 mode (2 channels).
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1390474]
Created attachment 125150
attachment-5407-0.html
Meaning what exactly?
It worked with previous versions. And even if it doesn't work - what is
the recommended step here? Remove pulseaudio?
Thanks & best regards
Benjamin
Am 19. Juli 2016 16:09:10 MESZ, schrieb bugzilla-dae...@freedesktop.org:
>https://bugs.freedesktop.org/show_bug.cgi?id=84804
>
>--- Comment #37 from Raymond ---
>https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=55a25246ee80aa950bf27f811c0cc176d0821a4e
>
>
>pulseaudio does not support non-interlaved mode
>
>
>static void check_access(snd_pcm_t *pcm_handle, snd_pcm_hw_params_t
>*hwparams,
>bool use_mmap) {
> if ((use_mmap && !snd_pcm_hw_params_test_access(pcm_handle, hwparams,
>SND_PCM_ACCESS_MMAP_INTERLEAVED)) ||
>!snd_pcm_hw_params_test_access(pcm_handle, hwparams,
>SND_PCM_ACCESS_RW_INTERLEAVED))
> pa_log_error("Weird, PCM claims to support interleaved access, but
>snd_pcm_hw_params_set_access() failed.");
>+
>
>--
>You are receiving this mail because:
>You reported the bug.
--
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/1390474
Title:
"Volume element PCM has 6 channels. That's too much!" - PA doesn't
support elements with more than two channels
Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the
error "Volume element PCM has 6 channels. That's too much! I can't handle
that!" and the card fails to show up in Sound Settings.
Everything is fine with 24/48 mode (2 channels).
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1390474/+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 1438510]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/525. -- 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/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Released Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
guiverc@d960-ubu2:/var/crash$ ls -la total 64408 drwxrwsrwt 3 rootwhoopsie 4096 Aug 1 08:32 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. drwxrwsr-x 2 guiverc whoopsie 4096 Jul 30 09:19 2018-05-22 -rw-r- 1 guiverc whoopsie70917 Jul 30 08:28 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 44980186 Jul 30 08:29 _usr_bin_vlc.1000.crash -rw-r- 1 guiverc whoopsie 20876029 Aug 1 08:28 _usr_lib_xorg_Xorg.1000.crash these .crash files have been filed (now twice) with `ubuntu-bug _usr_bin_caffeine.1000.crash` using my username (guiverc), no paths as I navigated to the directory first. A "Sorry, Ubuntu 18.10 has experienced an internal error" box appears each time, I just hit continue, and I get returned to shell. guiverc@d960-ubu2:/var/crash$ ubuntu-bug _usr_lib_xorg_Xorg.1000.crash Gtk-Message: 09:55:58.212: Failed to load module "appmenu-gtk-module" Gtk-Message: 09:55:58.212: Failed to load module "appmenu-gtk-module" Gtk-Message: 09:55:58.213: Failed to load module "appmenu-gtk-module" guiverc@d960-ubu2:/var/crash$ None have the .upload* in directory; and the 2018-07-30 Xorg crash file was overwritten by today's crash. -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Incomplete Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2
[Desktop-packages] [Bug 1784690] Bug is not a security issue
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free 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 geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784690 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in geoclue-2.0 package in Ubuntu: New Bug description: Crash report generated ProblemType: Package DistroRelease: Ubuntu 17.10 Package: geoclue-2.0 2.4.7-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 Date: Wed Jul 25 07:45:26 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-19 (1016 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.2 SourcePackage: geoclue-2.0 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1784690/+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 1784690] Re: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784690 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in geoclue-2.0 package in Ubuntu: New Bug description: Crash report generated ProblemType: Package DistroRelease: Ubuntu 17.10 Package: geoclue-2.0 2.4.7-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 Date: Wed Jul 25 07:45:26 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-19 (1016 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.2 SourcePackage: geoclue-2.0 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1784690/+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 1784690] Re: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
It failed to install since there was no available group ID to create: addgroup: No GID is available in the range 100-999 (FIRST_SYS_GID - LAST_SYS_GID). addgroup: The group `geoclue' was not created. Have you got a large number of groups in your system? ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784690 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in geoclue-2.0 package in Ubuntu: New Bug description: Crash report generated ProblemType: Package DistroRelease: Ubuntu 17.10 Package: geoclue-2.0 2.4.7-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 Date: Wed Jul 25 07:45:26 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-19 (1016 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.2 SourcePackage: geoclue-2.0 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1784690/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
** Attachment added: "syslog.2018-08.01" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5170143/+files/syslog.2018-08.01 -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Incomplete Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
Chris Guiver: 1) While the issue is being root caused, please keep light-locker, and caffeine uninstalled. 2) Regarding the file: -rw-r- 1 guiverc whoopsie 20M Aug 1 08:28 _usr_lib_xorg_Xorg.1000.crash No error reports have been reported to errors since 2018-07-11. One may further confirm is if in the folder /var/crash there are files .upload and .uploaded found along with the same .crash file (or a bug report is created on Launchpad). Clicking on the crash GUI doesn't indicate if a crash was successfully reported. For more on this, please see https://help.ubuntu.com/community/ReportingBugs . Hence, could you please report the crash, and advise to the additional files in /var/crash? -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Incomplete Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
** Attachment added: "journalctl-a.2018-08-01.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5170140/+files/journalctl-a.2018-08-01.txt -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Incomplete Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
today's crash -rw-r- 1 guiverc whoopsie 20M Aug 1 08:28 _usr_lib_xorg_Xorg.1000.crash // this has was reported (ubuntu-bug) no caffeine or light-locker are installed on screen I had 4 'repeats' but was able to look closer and not it's not a message repeated, but it's part of `dmesg` log, which contained today the following [116686.756961] radeon :01:00.0: couldn't schedule ib [116686.756995] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! [118941.608308] radeon :01:00.0: couldn't schedule ib [118941.608344] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! [118941.608308] radeon :01:00.0: couldn't schedule ib [118941.608344] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! [171718.127155] radeon :01:00.0: couldn't schedule ib [171718.127190] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! [218598.613273] radeon :01:00.0: couldn't schedule ib [218598.613308] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! NOTE: I didn't write down the numbers but counted four 'repeats' only so one of my copy/pastes (from dmesg) wasn't there (I'm assuming the top/first one). The left 'dmesg' time part is what I missed yesterday. The message appears near top left (maybe a few lines down) on both screens, stays there awhile then screen blanks and I'm back at login greeter (my xfce session gone) ** Attachment added: "dmesg.2018-08-01" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5170138/+files/dmesg.2018-08-01 -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in xorg package in Ubuntu: Incomplete Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item
[Desktop-packages] [Bug 1521987]
(In reply to Eugene Crosser from comment #25) > It happens when audio control application running and not running likewise, > but desktop's audio widget in the panel is indeed running (Cinnamon and > Unity, same manifestations). It is possible that this audio widget is indeed > the culprit. It's possible, but I don't think it's likely. Can you attach a log file that shows what happens when you start with analog output selected and headphones plugged in, and then unplug them and plug them back in? Instructions for getting the log: https://wiki.ubuntu.com/PulseAudio/Log -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 128797 Pulse Log incorrect switching Log that should show pulse incorrectly switching to digital when it should switch back to the previous configuration for speakers. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Do you happen to have the audio settings application open? If you do, it can mess up the device selection: https://bugzilla.gnome.org/show_bug.cgi?id=762932 -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
(In reply to Tanu Kaskinen from comment #24) > Do you happen to have the audio settings application open? If you do, it can > mess up the device selection: > https://bugzilla.gnome.org/show_bug.cgi?id=762932 It happens when audio control application running and not running likewise, but desktop's audio widget in the panel is indeed running (Cinnamon and Unity, same manifestations). It is possible that this audio widget is indeed the culprit. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/390. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
(In reply to pablow.1422 from comment #44) > Created attachment 131569 [details] > pulse audio verbose log > > Same problem and use case: analog line-out speakers, headphone plugged-in, > headphone unplugged, digital output profile set instead of analog line-out > (Analog Duplex to be precise). > > It happens on Fedora 25 (10.0-2.fc25) and openSUSE tumbleweed (can't have > access to that PC right now), both running KDE Plasma desktop (5.9.5). > > KDE devs said it should be reported here > [https://bugs.kde.org/show_bug.cgi?id=380316#add_comment] Never mind. Something in the miniplug speaker contact was preventing the detection of the port as being connected. Sorry for the useless reply. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 131569 pulse audio verbose log Same problem and use case: analog line-out speakers, headphone plugged- in, headphone unplugged, digital output profile set instead of analog line-out (Analog Duplex to be precise). It happens on Fedora 25 (10.0-2.fc25) and openSUSE tumbleweed (can't have access to that PC right now), both running KDE Plasma desktop (5.9.5). KDE devs said it should be reported here [https://bugs.kde.org/show_bug.cgi?id=380316#add_comment] -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
(In reply to Tanu Kaskinen from comment #42) > (In reply to flat from comment #40) > > Same issue on xfce4, so it's not budgie. > > It certainly was Budgie according to the log. Maybe xfce4 has a similar bug > in its volume control thingy. No problem on the delay, thanks for taking the time to look into this. I'll file a bug report with budgie. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
(In reply to flat from comment #40) > Same issue on xfce4, so it's not budgie. It certainly was Budgie according to the log. Maybe xfce4 has a similar bug in its volume control thingy. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Sorry for the long delay, I have trouble keeping up with all email... (In reply to flat from comment #39) > Created attachment 129322 [details] > pulse audio verbose log with > 0001-card-log-the-reason-for-profile-changes.patch 10.0 > > Sorry it took a couple days for it to happen again. Guess it helps when you > compile to actually apply the patch... haha. Here's a log from it switching > between digital and normal, even after I set it to the correct > configurations it seems to switch. Looking through the log I think it might > have to do with budgie-panel, but I'm not sure. Yes, "Budgie Volume Control" changes the profile to digital. > Also got another crash so > that's the first log. Second log starts on line 4424 It's not a crash, it's a failure to start the daemon. module-esound- protocol-unix can't setup itself, because the socket it needs is reserved by some other process (probably another pulseaudio instance). I'm not sure why this happens, but you can safely remove module-esound- protocol-unix from /etc/pulse/default.pa. It's extremely unlikely that you have any applications that still use esound. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 129226 0001-card-log-the-reason-for-profile-changes.patch (for 10.0) Here's the updated patch. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
The new log doesn't seem to have the patch applied. Can you try again? You can check that pulseaudio is running with the patch by searching the log for messages that contain "XXX" that are printed whenever the card profile changes. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 129265 pulse audio verbose log with 0001-card-log-the-reason-for-profile-changes.patch 10.0 Here is the log from the new rebased patch. The bug did occur in git master but not as often. >The first log shows four "audio-volume-change" sounds being played in quick >succession during the crash. The volume changes are initiated by >gnome-settings-daemon. >Did you change the volume manually while disconnecting the headphones, or is >this something that gnome-settings-daemon does automatically? I'm not sure if that was me or not. I usually tap the volume key a couple times to see what output configuration it is set on because it's quick. This time I didn't touch the volume manually. The log should show it switching from 5.1 to digital then digital to 5.1 and then 5.1 to stereo duplex and then stereo duplex to digital. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Same issue on xfce4, so it's not budgie. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 129322 pulse audio verbose log with 0001-card-log-the-reason-for-profile-changes.patch 10.0 Sorry it took a couple days for it to happen again. Guess it helps when you compile to actually apply the patch... haha. Here's a log from it switching between digital and normal, even after I set it to the correct configurations it seems to switch. Looking through the log I think it might have to do with budgie-panel, but I'm not sure. Also got another crash so that's the first log. Second log starts on line 4424 -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 129175 0001-card-log-the-reason-for-profile-changes.patch Here's the patch. It's written against the git master branch. If you need it for some other PulseAudio version, let me know and I'll rebase it. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
In my case speakers should be set to Analog Surround 5.1 Output + Analog Stereo Input, however after unplugging headphones they are switched to digital out. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Sure, if you write a patch I will compile and test it. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
The log doesn't match your problem description. The digital profile is not activated at all. The log shows switching between headphones and lineout in 2.1 mode. You wanted to use 5.1, so is your problem actually that you get 2.1 audio instead of 5.1? -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 129184 pulse verbose log with 0001-card-log-the-reason-for-profile-changes.patch So interestingly enough I can't reproduce the issue using git master. Attached are two logs as one attachment. The second log starts at line 5308 (Didn't want to spam attachments). The first log shows pulse crashing upon disconnecting the headphones. The second log shows pulse switching between 5.1-stereo and Analog Stereo working fine. If you rebase the patch on 10.0 I can try it again to see what was going on. Version 10.0 is the current version from Arch Linux's repos. I assume a commit since then must have fixed something either intentionally or unintentionally. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
(In reply to flat from comment #34) > Created attachment 129184 [details] > pulse verbose log with 0001-card-log-the-reason-for-profile-changes.patch > > So interestingly enough I can't reproduce the issue using git master. The first log with the crash shows a switch to the digital profile. Unfortunately, the crash happens before the log message I added is printed. The first log shows four "audio-volume-change" sounds being played in quick succession during the crash. The volume changes are initiated by gnome-settings-daemon. Did you change the volume manually while disconnecting the headphones, or is this something that gnome-settings- daemon does automatically? > Attached are two logs as one attachment. The second log starts at line 5308 > (Didn't want to spam attachments). The first log shows pulse crashing upon > disconnecting the headphones. The second log shows pulse switching between > 5.1-stereo and Analog Stereo working fine. If you rebase the patch on 10.0 I > can try it again to see what was going on. Version 10.0 is the current > version from Arch Linux's repos. I assume a commit since then must have > fixed something either intentionally or unintentionally. I don't think it's fixed in master, but I can anyway make a patch for 10.0. I'll change it so that the profile change reason is printed in an earlier phase. I'll also add some logging in an attempt to make it easier to track down the reason for the crash if it happens again. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Thanks, the log is interesting. At line 5943 the headphones are plugged in. Pulseaudio then decides to switch from the 5.1 profile to the analog stereo profile, as expected. After switching the profile, however, pulseaudio decides to immediately switch to digital output instead. Unfortunately the log doesn't show why this happens. If I write a patch that adds better logging, will you be able to apply and test it? Here are some instructions for building and installing pulseaudio from source: https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/PulseAudioFromGit/ -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Created attachment 128999 digital/5.1 - stereo out/digital Sorry, this bug isn't consistent so that last log may not have reflected the issue. This _should_ show that it starts my headphones as digital out, upon unplugging the line out should be switched to 5.1. Again plugging in headphones changes the output to digital. After setting the headphones to stereo out via pulse audio volume control, unplugging the headphones sets the configuration back to digital. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
(In reply to Tanu Kaskinen from comment #22) > I believe PulseAudio 9.0 will handle your use case well. Please report back > if it doesn't. It does not. Version: 1:9.0-2ubuntu2 Same behavior: after plugging and unplugging the headset some nonexistent device becomes active, and I have no sound until I manually select "line out". -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
*** Bug 96237 has been marked as a duplicate of this bug. *** -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
I believe PulseAudio 9.0 will handle your use case well. Please report back if it doesn't. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
I am not sure that the suggested patch is a good fix for the problem. As I understand it, with the patch, when the currently active destination becomes unavailable, new destination is chosen on the basis of its priority. Now consider my own use case: I have S/PDIF and Analog outputs on the chip, but S/PDIF is not connected to anywhere (there is no connector on the box). I have speakers permanently connected to the analog "line out" socket. And I use headphones intermittently. Normally, desktop's audio widget configures "line out" as active, which is what I want. When I plug the headphones, they automatically become active, and speakers are muted, which is what I want, again. But, when I unplug the headphones, (unconnected) S/PDIF becomes active instead of the speakers, and I lose sound until I manually reconfigure the output via the audio widget. I think that my scenario is quite typical (it happens both on my desktop and notebook computers), and should be addressed better. Thank you. -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987]
Just to let you know: I had a similar bug with Fedora 24 which drove me nuts. Analog output was always switched back to digital, losing sound. Changing it in pavucontrol didn't last longer than a few seconds. With the patch from comment 12, my problem is fixed! -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1521987] Re: Sound is not automatically switched back from headphones to speakers
** Changed in: pulseaudio Status: Confirmed => Unknown ** Bug watch added: GNOME Bug Tracker #762932 https://bugzilla.gnome.org/show_bug.cgi?id=762932 ** Bug watch added: KDE Bug Tracking System #380316 https://bugs.kde.org/show_bug.cgi?id=380316 -- 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/1521987 Title: Sound is not automatically switched back from headphones to speakers Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: When plugging in headphones, sound output is correctly switched from speakers (line out) to the headphones. When the headphones are unplugged, sound is NOT automatically switched back to the speakers. This bug started happening on my system after I upgraded from 14.04 to 15.10 so it is a regression. Attached is pulseaudio log of what happens when I plug and unplug my headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1521987/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time
Yesterday I discovered another Gnome software bug, (another) one of
Files (Nautilus). Without any reason, Files was running 4+% of the CPU
for a long time, without even touching it. Might be some interaction, if
I see that again, will file a separate bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
In Progress
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) =
[Desktop-packages] [Bug 1755986] Re: WiFi icon / settings gone from user menu
In fact, the issue is not limited to wireless networks. The wired connection options are also not displayed correctly. This screenshot shows what I see in the menu when connected to wired network with wrong profile. By the way, after I reinstalled Ubuntu 18.04.1, the problem showed up for the first time after I added a second wired profile... But I also did some other things, so I am not sure it was caused by adding the second profile. ** Attachment added: "Screenshot of user menu when connected to wired network with wrong profile" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+attachment/5170108/+files/Screenshot%20user%20menu%20on%20wrong%20wired%20network.png -- 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/1755986 Title: WiFi icon / settings gone from user menu Status in gnome-shell package in Ubuntu: Confirmed Bug description: Recently, in the GNOME session, the WiFi icon vanished, and all that I get is the icon for connected network, which is odd. My other machine does not even seem to get that icon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 06:59:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell 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/1755986/+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 1755986] Re: WiFi icon / settings gone from user menu
In fact, the issue is not limited to wireless networks. The wired connection options are also not displayed correctly. This screenshot shows what I see in the menu when connected to wired network with wrong profile. By the way, after I reinstalled Ubuntu 18.04.1, the problem showed up for the first time after I added a second wired profile... But I also did some other things, so I am not sure it was caused by adding the second profile. ** Attachment added: "Screenshot of user menu when connected to wired network with wrong profile" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+attachment/5170109/+files/Screenshot%20user%20menu%20on%20wrong%20wired%20network.png -- 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/1755986 Title: WiFi icon / settings gone from user menu Status in gnome-shell package in Ubuntu: Confirmed Bug description: Recently, in the GNOME session, the WiFi icon vanished, and all that I get is the icon for connected network, which is odd. My other machine does not even seem to get that icon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 06:59:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell 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/1755986/+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 1784706] [NEW] [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] Background noise or low volume
Public bug reported: I am having the same problem with Linux Mint. I play any audio(from YouTube or hard disk) and the volume is very low. And the background noise is very high. Apparently Ubuntu did not have such a problem. But unfortunately I am facing this problem which I tried not to face by abandoning Linux mint and switching to Ubuntu. I am expecting: 1. Stopping background noise 2. Stable and decent volume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdintisar 3307 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 1 01:51:48 2018 InstallationDate: Installed on 2018-07-29 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 0F1J0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5459:pvr:rvnDellInc.:rn0F1J0W:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5459 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784706 Title: [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: I am having the same problem with Linux Mint. I play any audio(from YouTube or hard disk) and the volume is very low. And the background noise is very high. Apparently Ubuntu did not have such a problem. But unfortunately I am facing this problem which I tried not to face by abandoning Linux mint and switching to Ubuntu. I am expecting: 1. Stopping background noise 2. Stable and decent volume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdintisar 3307 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 1 01:51:48 2018 InstallationDate: Installed on 2018-07-29 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 0F1J0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5459:pvr:rvnDellInc.:rn0F1J0W:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5459 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784706/+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 1755986] Re: WiFi icon / settings gone from user menu
I think I am experiencing the same bug. Here is a screenshot of my desktop with user menu when I am connected by WiFi. By the way, I reinstalled Ubuntu 18.04.1 from scratch last week, but I kept my user directory intact. I had this issue since upgrading to 18.04 from 17.10. ** Attachment added: "Screenshot of user menu when connected to WiFi" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+attachment/5170107/+files/Screenshot%20user%20menu%20on%20WiFi.png -- 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/1755986 Title: WiFi icon / settings gone from user menu Status in gnome-shell package in Ubuntu: Confirmed Bug description: Recently, in the GNOME session, the WiFi icon vanished, and all that I get is the icon for connected network, which is odd. My other machine does not even seem to get that icon. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 06:59:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell 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/1755986/+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 1784473] Re: [radeon] Ubuntu boots to a black screen
After installing upstream kernel the issue is solved though boot time is long. I get this screen(https://ibb.co/isQYTz) after selecting the kernel from grub, not an issue to me but thought to inform you. Also can I remove the kernel because had remove virtualbox ** Description changed: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live-boot-leads-to- blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] + Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: amit 2479 F pulseaudio - /dev/snd/controlC0: amit 2479 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: amit 2479 F pulseaudio + /dev/snd/controlC0: amit 2479 F pulseaudio
[Desktop-packages] [Bug 1070002] Re: system-config-printer: Unknown value for media-col: (unknown IPP value tag 0x34)
I have the same error on a Dell C1765nfw-MFP; on 198.168.0.7:9100 that had been working for years, However cups was update approximately July 14, 2018 I am running Ubuntu-Gnome 14.04.5-LTS, with the Gnome flashback Metacity desktop and I am wonderfully stuck on this desktop. Also since the update I can't print at all as I get a 'Filter error', reported as Bug #1784512. I could do a timeshift backup, but then other things I like and net would be broke Like apache 2 and PHP.INI and my-weather indicator, and so on. Also since the update my gcc-4.8 will not compile (Make) Bug #1575109 So far I have had to r-sync a backup on my system because of updates 4 times the last 2 months due to upstates. I am confused, frustrated and dismayed recently with Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1070002 Title: system-config-printer: Unknown value for media-col: (unknown IPP value tag 0x34) Status in system-config-printer package in Ubuntu: Fix Released Bug description: When running system-config-printer from the console and then entering my HP-LJ-2200 preferences I get the following errors in the console: $ system-config-printer Unknown value for media-col: (unknown IPP value tag 0x34) Choices: [u'media-bottom-margin', u'media-left-margin', u'media-right-margin', u'media-size', u'media-source', u'media-top-margin', u'media-type'] Selecting from choices: media-bottom-margin ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: system-config-printer-common 1.3.11+20120807-0ubuntu10 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 21:57:49 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926) Lpstat: device for HP-LaserJet-2200: socket://10.100.10.9 Lsusb: Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 003: ID 04b4:0033 Cypress Semiconductor Corp. Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6325 (EY349EA#AKD) PackageArchitecture: all Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: HP-LaserJet-2200: HP LaserJet 2200 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=4f0c1391-e243-4e37-aaab-52625df3e3bd ro SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68TT2 Ver. F.07 dmi.board.name: 30B0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.15 dmi.chassis.asset.tag: CNU7110B09 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6325 (EY349EA#AKD) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1070002/+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 1784540] Re: Nvidia G94 [GeForce 9600 GT] Driver doesn't load properly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-304 (Ubuntu) ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1784540 Title: Nvidia G94 [GeForce 9600 GT] Driver doesn't load properly Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Main Linux Mint 18.3 "Sylvia" Base Ubuntu xenial. After Upgrade to linux kernal 4.15.0-29 nvidia-340 (recommended) installed but fails to display alternative resolution settings and fails to recognise the second monitor. Version 340.104-0ubuntu0.16.04.1 NVIDIA binary driver - version 340.104 nvidia-304 installed but fails to display alternative resolution settings and fails to recognise the second monitor. Version 304.135.0ubuntu0.16.04.2 NVIDIA legacy binary driver - version 304.135 this all works ok with the previous kernal 4.13.0-45 I haven't tried the xserver-xorg-video-nouveau (open-source) driver yet. If after trying it I am still having problems I will endeavour to update this bug report if I can get to it. === lsb_release -rd Description: Linux Mint 18.3 Sylvia Release: 18.3 === --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 3071 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=1cd525be-8127-439c-aa6e-c91c051c995c InstallationDate: Installed on 2018-06-16 (44 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release i386 20171124 IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=ecc21d3e-2058-4bbc-83fd-5a294c65fb6b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.157.20 RfKill: Tags: sylvia Uname: Linux 4.15.0-29-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1784540/+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 1784540] [NEW] Nvidia G94 [GeForce 9600 GT] Driver doesn't load properly
You have been subscribed to a public bug: Main Linux Mint 18.3 "Sylvia" Base Ubuntu xenial. After Upgrade to linux kernal 4.15.0-29 nvidia-340 (recommended) installed but fails to display alternative resolution settings and fails to recognise the second monitor. Version 340.104-0ubuntu0.16.04.1 NVIDIA binary driver - version 340.104 nvidia-304 installed but fails to display alternative resolution settings and fails to recognise the second monitor. Version 304.135.0ubuntu0.16.04.2 NVIDIA legacy binary driver - version 304.135 this all works ok with the previous kernal 4.13.0-45 I haven't tried the xserver-xorg-video-nouveau (open-source) driver yet. If after trying it I am still having problems I will endeavour to update this bug report if I can get to it. === lsb_release -rd Description:Linux Mint 18.3 Sylvia Release:18.3 === --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 3071 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=1cd525be-8127-439c-aa6e-c91c051c995c InstallationDate: Installed on 2018-06-16 (44 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release i386 20171124 IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=ecc21d3e-2058-4bbc-83fd-5a294c65fb6b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.157.20 RfKill: Tags: sylvia Uname: Linux 4.15.0-29-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Medium Status: New ** Tags: apport-collected sylvia -- Nvidia G94 [GeForce 9600 GT] Driver doesn't load properly https://bugs.launchpad.net/bugs/1784540 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. -- 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 1509950]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/211. -- 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/1509950 Title: DELL XPS M1210 STAC9221 Dual Headphone jacks not working Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Incomplete Bug description: Ubuntu 15.10 after latest update headphones stopped working. When I ran alsamixer in the terminal, I saw they were muted. after unmuting them I pressed F6 and saw the soundcard id, then pressed esc and esc to exit alsamixer then entered sudo alsactl store Intel After rebooting they worked! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1272 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 02:15:01 2015 InstallationDate: Installed on 2015-10-20 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/11/2008:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXC062 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1509950/+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 1509950] Re: DELL XPS M1210 STAC9221 Dual Headphone jacks not working
** Changed in: alsa-driver Status: Confirmed => Unknown -- 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/1509950 Title: DELL XPS M1210 STAC9221 Dual Headphone jacks not working Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Incomplete Bug description: Ubuntu 15.10 after latest update headphones stopped working. When I ran alsamixer in the terminal, I saw they were muted. after unmuting them I pressed F6 and saw the soundcard id, then pressed esc and esc to exit alsamixer then entered sudo alsactl store Intel After rebooting they worked! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1272 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 02:15:01 2015 InstallationDate: Installed on 2015-10-20 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/11/2008:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXC062 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1509950/+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 1784580] Re: evolution cannot type messages
The freeze / inability to type seems to occur only after selecting a bit of text with the mouse, then typing to replace that text. After a while if I persist trying to type, the window goes blank as shown in the attached screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1784580 Title: evolution cannot type messages Status in evolution package in Ubuntu: New Bug description: Something similar seems to be happening again now. I cannot type messages in evolution since the very latest update. Other fields work but trying to type in the main email box doesn't work. I get a popup about something having gone wrong with webkitgtk, and it sent some bug report about it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784580/+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 1784580] Re: evolution cannot type messages
** Attachment added: "Screenshot of the problem occurring in the evolution compose window" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784580/+attachment/5170051/+files/Screenshot%20from%202018-07-31%2020-23-28.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1784580 Title: evolution cannot type messages Status in evolution package in Ubuntu: New Bug description: Something similar seems to be happening again now. I cannot type messages in evolution since the very latest update. Other fields work but trying to type in the main email box doesn't work. I get a popup about something having gone wrong with webkitgtk, and it sent some bug report about it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784580/+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 1784580] Re: evolution cannot type messages
I have figured out the culprit: The "Screen reader" accessibility setting was turned on for some reason, and if I turn it off, this problem goes away. Steps to reproduce this problem: 1. Turn on screen reader 2. Right click an old email in evolution, choose Edit as new message 3. Paint some text with the mouse, start typing to replace it. 4. Continue trying to type even when the window seemingly freezes. 5. The compose window should go blank and show a view similar to the attached screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1784580 Title: evolution cannot type messages Status in evolution package in Ubuntu: New Bug description: Something similar seems to be happening again now. I cannot type messages in evolution since the very latest update. Other fields work but trying to type in the main email box doesn't work. I get a popup about something having gone wrong with webkitgtk, and it sent some bug report about it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784580/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
In case it helps anyone else on *buntu systems: sudo apt-get install libcap-dev sudo apt-get install libsndfile-dev Warning: UDEV & SPEEX not enabled: ./configure --enable-udev --enable-speex didn't work for me. See https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/28 and comment 4 here: https://www.linuxquestions.org/questions/linux-software-2/audio-problems-pulseaudio-installation-938130/ ./configure --enable-speex make sudo make install pulseaudio --version -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1784514] Re: Update evolution-data-server to 3.28.5
This bug was fixed in the package evolution-data-server - 3.28.5-3ubuntu1 --- evolution-data-server (3.28.5-3ubuntu1) cosmic; urgency=medium * debian/libebook-contacts-1.2-2.symbols: Mark a symbol as optional since it isn't present in Ubuntu's ppc64el build evolution-data-server (3.28.5-3) unstable; urgency=medium * debian/libebook-contacts-1.2-2.symbols: Adjust for hppa evolution-data-server (3.28.5-2) unstable; urgency=medium * Update symbols files for new release evolution-data-server (3.28.5-1) unstable; urgency=medium * New upstream release (LP: #1784514) -- Jeremy Bicha Tue, 31 Jul 2018 10:11:35 -0400 ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1784514 Title: Update evolution-data-server to 3.28.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Bionic: In Progress Bug description: Impact == 3.28.5 is the final scheduled bug fix release in the 3.28 series. Updating e-d-s is required to update evolution to 3.28.5 (LP: #1784522) https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+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 1784522] Re: Update evolution to 3.28.5
This bug was fixed in the package evolution - 3.28.5-1 --- evolution (3.28.5-1) unstable; urgency=medium * New upstream release (LP: #1784522) * Bump e-d-s dependencies and build-dependencies to 3.28.5 -- Jeremy Bicha Mon, 30 Jul 2018 22:27:47 -0400 ** Changed in: evolution (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1784522 Title: Update evolution to 3.28.5 Status in evolution package in Ubuntu: Fix Released Status in evolution source package in Bionic: In Progress Bug description: Impact == evolution 3.28.5 is the final scheduled bug fix release in the 3.28 series. https://gitlab.gnome.org/GNOME/evolution/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution/commits/gnome-3-28 Test Case = After installing this update, please restart your computer. Verify that evolution still works as well as it did before. Optionally, you can go through some of the fixed bugs to verify the bug and the fix. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME Ubuntu GNOME stopped including Evolution by default in 17.04. Upgraders may still have Evolution installed and it's a popular app. (It was demoted to universe before 16.04 LTS.) Other Info == This update depends on evolution-data-server 3.28.5 (LP: #1784514) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784522/+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 1784473] Re: [radeon] Ubuntu boots to a black screen
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784473 Title: [radeon] Ubuntu boots to a black screen Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live- boot-leads-to-blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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:
[Desktop-packages] [Bug 1784671] [NEW] Keeping Alt+Space pressed shows the window menu and then minimizes the window
Public bug reported: To reproduce: Open a couple of windows Press Alt+Space and keep it pressed Expected results: The window menu opens and nothing else happens Current behavior: The window menu opens The window is minimized The window menu of the following window is open The window is minized ... ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1784671 Title: Keeping Alt+Space pressed shows the window menu and then minimizes the window Status in gnome-shell package in Ubuntu: New Bug description: To reproduce: Open a couple of windows Press Alt+Space and keep it pressed Expected results: The window menu opens and nothing else happens Current behavior: The window menu opens The window is minimized The window menu of the following window is open The window is minized ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784671/+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 1784669] [NEW] package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de
Public bug reported: I was trying to install nautilus-image-converter-0-3-1-en-ubu.deb and then crashed! ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libunity9 7.1.4+18.04.20180209.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 13:03:49 2018 ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de outras instâncias do pacote libunity9:i386 InstallationDate: Installed on 2018-05-15 (76 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: libunity Title: package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de outras instâncias do pacote libunity9:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1784669 Title: package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de outras instâncias do pacote libunity9:i386 Status in libunity package in Ubuntu: New Bug description: I was trying to install nautilus-image-converter-0-3-1-en-ubu.deb and then crashed! ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libunity9 7.1.4+18.04.20180209.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 13:03:49 2018 ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de outras instâncias do pacote libunity9:i386 InstallationDate: Installed on 2018-05-15 (76 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: libunity Title: package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de outras instâncias do pacote libunity9:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1784669/+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 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
Tentative fix: https://gitlab.gnome.org/Community/Ubuntu/gnome- software/merge_requests/4 -- 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/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades Status in gnome-software package in Ubuntu: In Progress Bug description: In Ubuntu the GUI for upgrading packages is update-manager allowing debconf questions to be answered when needed and Ubuntu also offers unattended-upgrades for upgrading packages in the background and it keeps back packages from upgrading when configuration-file changes would need user interaction during the upgrade. Unattended-upgrades can be configured to perform upgrades during system shutdown. Gnome Software in Bionic started offering performing upgrades during shutdown using PackageKit independently from update-manager and unattended-upgrades without offering all of the features of either one. Unless there is a decision to fully switch to Gnome Software I suggest disabling the "Install pending software updates" on the shutdown screen to avoid confusing users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
"pulseaudio --version" to check v12.2 link https://www.freedesktop.org/software/pulseaudio/releases/pulseaudio-12.2.tar.xz -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1778011] Re: PRIME Power Saving mode draws too much power
This bug was fixed in the package nvidia-prime - 0.8.9 --- nvidia-prime (0.8.9) cosmic; urgency=medium [ Alberto Milone ] * 90-nvidia.conf, debian/rules, prime-select: - Make sure to remove the old blacklist file. - Use /lib for blacklist-nvidia.conf. - Do not check if prime is supported when disabling nvidia. - Enable KMS by default. - Install prime-switch again (LP: #1778011). * debian/nvidia-prime.nvidia-prime-boot.service: - Remove service. [ Alex Tu ] * prime-select: avoid regenerating the initramfs. -- Alberto Milone Tue, 31 Jul 2018 16:47:20 +0200 ** Changed in: nvidia-prime (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: In Progress Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in gdm3 source package in Bionic: In Progress Status in nvidia-prime source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Solving the problem in systemd (LP: #1777099), and adding code in gpu- manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep, dramatically decreases power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+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 1421002]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/57. -- 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/1421002 Title: pulseaudio crashed with SIGABRT in transport_speaker_gain_changed_cb() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: Change Bluethooth ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:4.0-0ubuntu23 Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2991 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 11 20:01:45 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-09-25 (139 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/pulse-4.0/modules/module-bluetooth-device.so pa_hook_fire () from /usr/lib/libpulsecore-4.0.so ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: pulseaudio crashed with SIGABRT in pa_hook_fire() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1421002/+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 1421002] Re: pulseaudio crashed with SIGABRT in transport_speaker_gain_changed_cb()
** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/1421002 Title: pulseaudio crashed with SIGABRT in transport_speaker_gain_changed_cb() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: Change Bluethooth ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:4.0-0ubuntu23 Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2991 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 11 20:01:45 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-09-25 (139 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/pulse-4.0/modules/module-bluetooth-device.so pa_hook_fire () from /usr/lib/libpulsecore-4.0.so ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: pulseaudio crashed with SIGABRT in pa_hook_fire() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1421002/+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 1780442] Re: Please backport fix for & in attributes
When will this fix be released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780442 Title: Please backport fix for & in attributes Status in Fwupd: New Status in appstream-glib package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: Fix Committed Bug description: [Impact] There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. [Test Case] * Try to perform an update on a 8bitdo affected device. [Regression Potential] * Regressions would occur in metadata processing where the fwupd daemon wouldn't be able to process it. [Other Info] This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1780442/+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 1725779] Re: Gnome network manager cannot find authentication binary
Same issue here 18.04 with latest updates Jul 31 15:50:15 nash-laptop NetworkManager[857]: [1533048615.0356] vpn-connection[0x55b3f2d287a0,0217bd2c-3791-4aed-8877-c3b2562aa5f2," - jbotto",0]: Started the VPN service, PID 19470 Jul 31 15:50:15 nash-laptop NetworkManager[857]: [1533048615.0506] vpn-connection[0x55b3f2d287a0,0217bd2c-3791-4aed-8877-c3b2562aa5f2," - jbotto",0]: Saw the service appear; activating connection Jul 31 15:50:15 nash-laptop gnome-shell[2389]: Invalid VPN service type (cannot find authentication binary) Jul 31 15:50:15 nash-laptop gnome-shell[2389]: Invalid VPN service type (cannot find authentication binary) Jul 31 15:50:15 nash-laptop NetworkManager[857]: [1533048615.1203] vpn-connection[0x55b3f2d287a0,0217bd2c-3791-4aed-8877-c3b2562aa5f2," - jbotto",0]: Failed to request VPN secrets #3: No agents were available for this request. Jul 31 15:50:15 nash-laptop NetworkManager[857]: [1533048615.1263] vpn-connection[0x55b3f2d287a0,0217bd2c-3791-4aed-8877-c3b2562aa5f2," - jbotto",0]: VPN plugin: state changed: stopped (6) -- 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/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/1725779/+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 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
On an Ubuntu 14.04 system I installed the libglib2.0-0 package, then modified my /etc/apt/sources.list file from trusty to xenial, tried to install libglib2.0-0 and then experienced the crash in this bug report. I performed the same steps but added xenial-proposed to my /etc/apt/sources.list file and then the upgrade wanted to also install dpkg among other things. (trusty-amd64)root@impulse:/home/bdmurray# apt-get install libglib2.0-0 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libboost-date-time1.54.0 libboost-system1.54.0 libcdr-0.0-0 libcmis-0.4-4 libelfg0 libevdev2 libgnome-desktop-3-12 libinput-bin libinput10 libmspub-0.0-0 liborcus-0.6-0 librhythmbox-core8 libvisio-0.0-0 libwpd-0.9-9 libwpg-0.2-2 libwps-0.2-2 overlay-scrollbar-gtk2 pidgin-data rhythmbox-mozilla xfonts-mathml Use 'apt-get autoremove' to remove them. The following extra packages will be installed: adwaita-icon-theme apt apt-utils console-setup console-setup-linux cups cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-server-common dbus dpkg fontconfig fontconfig-config fonts-stix gcc-5-base gir1.2-javascriptcoregtk-4.0 gir1.2-rb-3.0 gir1.2-webkit2-4.0 ... Then in /var/log/apt/term.log we can see: ... Setting up dpkg (1.18.4ubuntu1.4) ...^M$ Installing new version of config file /etc/cron.daily/dpkg ...^M$ (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Re ading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(R eading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M( Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 132743 files and directories currently installed.)^M$ Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu4_amd64.deb ...^M$ Unpacking libglib2.0-0:amd64 (2.48.2-0ubuntu4) over (2.40.2-0ubuntu1) ...^M$ ... ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Xenial: Fix Committed Bug description: [Test case] Verify that a release-upgrade of an Ubuntu desktop works from trusty to xenial with -proposed enabled. Package failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0 2.48.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jul 27 18:31:08 2018 DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu3 Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack): triggers ci file contains unknown directive `interest-await' ErrorMessage: triggers ci file contains unknown directive `interest-await' InstallationDate: Installed on 2015-03-31 (1213 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+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 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
Yes, if we return early in gs_plugin_refresh in plugins/packagekit/gs- plugin-packagekit-refresh.c just after refreshing the metadata (i.e. if we skip downloading updates), the prepared-update file is never written, so that appears to be what we want. -- 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/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades Status in gnome-software package in Ubuntu: In Progress Bug description: In Ubuntu the GUI for upgrading packages is update-manager allowing debconf questions to be answered when needed and Ubuntu also offers unattended-upgrades for upgrading packages in the background and it keeps back packages from upgrading when configuration-file changes would need user interaction during the upgrade. Unattended-upgrades can be configured to perform upgrades during system shutdown. Gnome Software in Bionic started offering performing upgrades during shutdown using PackageKit independently from update-manager and unattended-upgrades without offering all of the features of either one. Unless there is a decision to fully switch to Gnome Software I suggest disabling the "Install pending software updates" on the shutdown screen to avoid confusing users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+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
