date:20201012

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

-- 
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/1851551

Title:
  man page does not mention that -e is deprecated

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  gnome-terminal -e 'command...'  emits a warning:

  # Option “-e” is deprecated and might be removed in a later version of 
gnome-terminal.
  # Use “-- ” to terminate the options and put the command line to execute 
after it.

  However this is contrary to the man page, which says nothing about -e
  being deprecated, and does not mention anything about the new method
  being possible (-- followed by command and options).

  Please update the documentation

  STEPS TO REPRODUCE:

  1.  man gnome-terminal
  2.  gnome-terminal -e "sh -c 'ls -l; sleep 3'"

  RESULTS: The documented method of specifying a command causes a
  deprecation warning.

  EXPECTED RESULTS: Documentation should say how to do the right thing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 10:20:44 2019
  InstallationDate: Installed on 2019-02-06 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1851551/+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 1742865] Re: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found

This is two separate issues:

1. Please tell us if you still have a problem with Fn keys not working
in a more recent Ubuntu release.

2. The nvidia card is detected according to your Lspci.txt, but it
appears there's just no driver installed for it.

** Summary changed:

- Fn Keys do not work, nvidia card not found 
+ Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
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/1742865

Title:
  Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Browsed and tried solutions over the past 2 years, nothing worked...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
  Uname: Linux 4.4.0-108-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jan 12 06:43:48 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828]
 Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829]
  InstallationDate: Installed on 2016-07-07 (553 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 174f:14e6 Syntek 
   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: LENOVO 80R6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed 
root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK:
  dmi.product.name: 80R6
  dmi.product.version: Lenovo Yoga 500-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 12 06:14:57 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14162 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742865/+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 1899376] Re: Confusing versioning of language-selector

2020-10-12 Thread handsome_feng

First of all, sorry for the inconvenience. I have deleted the package
from the PPA and will make a statement about this issue.

We made that change was because the sogou input method conflicted with
fcitx-ui-qimpanel and they needed to hijack the same dbus. We came up
with this bad idea when we couldn't change the Sogou input code, not
realizing the potential problems that could follow.

Now we're communicating with Sogou to find another way to fix the
problem, thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1899376

Title:
  Confusing versioning of language-selector

Status in Ubuntu Kylin:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  My attention was called to the existence of version 0.304 of language-
  selector in some of the 
  PPAs. It happened in a rather annoying way:

  https://discourse.ubuntu.com/t/request-better-arabic-font-for-
  ubuntu-20-04/14573/183

  I don't know how 'official' those PPAs are, but I see that the only
  difference compared to language-selector in the official Ubuntu
  archive is that users are not prompted to pull the fcitx-ui-qimpanel
  package.

  Ok.. So maybe it's no longer suitable for UKUI to install that
  package. But if that's the case, how about handling that in the
  official language-selector version?

  * If it's no longer useful for any Fcitx users, we could simply drop
  it from pkg_depends

  * If it's still useful for non-UKUI Fcitx users, we could stop
  language-selector from pulling it for UKUI users

  In any case it's highly desirable to get away from a situation where
  some users have a version of language-selector which blocks them from
  updates.

  Please let me know how you think this should best be handled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1899376/+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 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-10-12 Thread Didier Roche

I reapplied your debian/changelog directly and pushed to focal (pending
approval). Thanks a lot!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1899376] Re: Confusing versioning of language-selector

2020-10-12 Thread Gunnar Hjalmarsson

Thanks for addressing the issue so quickly, @handsome_feng. Closing the
bug, since it now has served its purpose of calling your attention to
it. :)

** Changed in: ubuntukylin
   Status: New => Fix Released

** Changed in: language-selector (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1899376

Title:
  Confusing versioning of language-selector

Status in Ubuntu Kylin:
  Fix Released
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  My attention was called to the existence of version 0.304 of language-
  selector in some of the 
  PPAs. It happened in a rather annoying way:

  https://discourse.ubuntu.com/t/request-better-arabic-font-for-
  ubuntu-20-04/14573/183

  I don't know how 'official' those PPAs are, but I see that the only
  difference compared to language-selector in the official Ubuntu
  archive is that users are not prompted to pull the fcitx-ui-qimpanel
  package.

  Ok.. So maybe it's no longer suitable for UKUI to install that
  package. But if that's the case, how about handling that in the
  official language-selector version?

  * If it's no longer useful for any Fcitx users, we could simply drop
  it from pkg_depends

  * If it's still useful for non-UKUI Fcitx users, we could stop
  language-selector from pulling it for UKUI users

  In any case it's highly desirable to get away from a situation where
  some users have a version of language-selector which blocks them from
  updates.

  Please let me know how you think this should best be handled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1899376/+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 1899435] [NEW] laptop (docked w/ lid closed) suspends after login

2020-10-12 Thread EAB

Public bug reported:

I installed 20.04 on my Thinkpad T440p laptop (previously 18.04). As
with 18.04 I boot up the laptop with it docked and with the lid closed,
however with 20.04 something new happens right after user login ... the
laptop goes into suspend and has to be woken up by pressing the power
button on the dock. This behavior is new and did not happen with 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 12 09:32:53 2020
InstallationDate: Installed on 2020-09-22 (19 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1899435

Title:
  laptop (docked w/ lid closed) suspends after login

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  I installed 20.04 on my Thinkpad T440p laptop (previously 18.04). As
  with 18.04 I boot up the laptop with it docked and with the lid
  closed, however with 20.04 something new happens right after user
  login ... the laptop goes into suspend and has to be woken up by
  pressing the power button on the dock. This behavior is new and did
  not happen with 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 12 09:32:53 2020
  InstallationDate: Installed on 2020-09-22 (19 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1899435/+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 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-10-12 Thread Didier Roche

** Changed in: libgweather (Ubuntu Focal)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  In Progress
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1316518] Re: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working

2020-10-12 Thread lemrm

Still exist in 20.04

** Attachment added: "status-s900x-2020-10-12=09-30.bash"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316518/+attachment/5421161/+files/status-s900x-2020-10-12%3D09-30.bash

-- 
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/1316518

Title:
  [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Internal Mic of Samsung Ativ book 9 (NP900X3G) is not supported
  properly.

  Stereo recording in audacity records sound from mic in L channel and only 
loud noise in R channel (phase inverted?)
  Muting R channel, and setting L channel to around 16%, in pavucontrol allows 
to record audio, but in poor quality.

  alsa-info.sh output: http://www.alsa-
  project.org/db/?f=064f0b536a1b068efd30d58c2641b5ec2348f059

  Ubuntu Gnome 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarah  2014 F pulseaudio
    sarah  8509 F alsamixer
   /dev/snd/controlC0:  sarah  2014 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  6 11:55:36 2014
  InstallationDate: Installed on 2014-04-29 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: None of the above
  Title: [900X3G, Realtek ALC282, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04ADU.023.140414.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3G-K02DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 900X3G
  dmi.product.version: P04ADU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarah  2004 F pulseaudio
   /dev/snd/controlC1:  sarah  2004 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=b4bd3914-d1c4-40f0-ba32-fb19aa9af13c
  InstallationDate: Installed on 2014-04-29 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=92ac4966-692f-4e06-a1dd-da069008e861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  StagingDrivers: rts5139
  Tags:  trusty trusty staging
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04ADU.023.140414.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3G-K02DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELE

[Desktop-packages] [Bug 1724037] Re: Allow GNOME fractional scaling below 100%

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1465
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1465

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1465
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724037

Title:
  Allow GNOME fractional scaling below 100%

Status in Mutter:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  It should be possible to scale down the whole shell to less than 100%
  e.g. 90% 85% etc.

  thanks

  ProblemType: Bug
  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
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 20:14:43 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724037/+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 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect

Maybe related:

https://gitlab.gnome.org/GNOME/mutter/-/issues/1466

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1466
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1466

-- 
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/1899206

Title:
  Tweaktool Keyboard “Additional Layout Options” not persisting on USB
  keyboard unplug/reconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which
  seems to have been introduced within the past couple of weeks. I have
  a couple custom keyboard settings configured in Tweaktool "Additional
  Layout Options". These settings work great.

  I have a USB keyboard plugged into the machine. If I have the keyboard
  plugged in when I start my Gnome session, the customized keyboard
  layout options are correctly applied to the USB keyboard. If I unplug
  and reconnect the keyboard, the keyboard does will _NOT_ have the
  customized keyboard settings.

  If I restart my Gnome session (using Alt-F2 -> "r"), the customized
  settings are applied to the keyboard.

  I think this behavior is something new. Before, I was able to
  unplug/reconnect my keyboard and it would apply my customized keyboard
  settings on reconnect. Is there anything I can do to force the
  application of the custom keyboard tweaks on USB keyboard reconnect?

  Is anyone else able to reproduce this? I don't have any other machines
  with Ubuntu 20.04.1 to test with.

  Thanks!

  (This is also cross-posted at askubuntu:
  https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional-
  layout-options-not-working)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+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 1899437] [NEW] package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed libglib2.0-cil package post-installation script subprocess returned error exit status 1

2020-10-12 Thread Sarah Chatelain

Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libglib2.0-cil 2.12.40-3
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Oct 12 09:13:09 2020
ErrorMessage: installed libglib2.0-cil package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-07-26 (809 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: gtk-sharp2
Title: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed 
libglib2.0-cil package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)

** Affects: gtk-sharp2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk-sharp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899437

Title:
  package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed
  libglib2.0-cil package post-installation script subprocess returned
  error exit status 1

Status in gtk-sharp2 package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-cil 2.12.40-3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 12 09:13:09 2020
  ErrorMessage: installed libglib2.0-cil package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-26 (809 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gtk-sharp2
  Title: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed 
libglib2.0-cil package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk-sharp2/+bug/1899437/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2020-10-12 Thread bernd

Same here (Ubuntu 20.04)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1838151

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1899437] Re: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed libglib2.0-cil package post-installation script subprocess returned error exit status 1

2020-10-12 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk-sharp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899437

Title:
  package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed
  libglib2.0-cil package post-installation script subprocess returned
  error exit status 1

Status in gtk-sharp2 package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-cil 2.12.40-3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 12 09:13:09 2020
  ErrorMessage: installed libglib2.0-cil package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-26 (809 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gtk-sharp2
  Title: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed 
libglib2.0-cil package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk-sharp2/+bug/1899437/+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 1899315] Re: Keyboard won't work in password entry when resuming

2020-10-12 Thread Brett Witty

If I attempt to "Switch users" it'll give me a different graphical
login, let me type my password, blank the screens and be back where I
was.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1899315

Title:
  Keyboard won't work in password entry when resuming

Status in lightdm package in Ubuntu:
  New

Bug description:
  If I lock my screen and return, lightdm-gtk will ask for my password,
  but accepts no keyboard input. I can Ctrl-Alt-F1, log in and restart
  the lightdm service which mostly solves the issue, but this is a pain
  to do every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Oct 11 15:19:25 2020
  InstallationDate: Installed on 2017-08-29 (1138 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-10-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1899315/+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 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-10-12 Thread zdohnal

Hi Shivani,

I'm sorry I don't have such a list.

Did you have such a list when you removed the dependency on plugin for
other models in 3.20.6?

I base my request (revert all plugin dependency made in 3.20.6) upon the
following logic:

- when model support was added it was tested by HPLIP project owners
- when user had a plugin problem with a model (the model needed a plugin 
although models.dat says it doesn't), he reached HPLIP project owners with the 
issue and they updated models.dat

so based on the prerequisites it doesn't make sense to remove dependency
on plugin for models, unless you have a list of devices which you tested
and actually don't need a plugin but they are noted as they need a
plugin.

Wouldn't it make sense to revert the 'plugin state' to the state before
3.20.6, depending on the presumption 'the previous state was tested' is
true?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1883898

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1883898/+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 1899442] [NEW] Test Output Device Button does not respect when you change the output device

Public bug reported:

I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition
to the appearance changes in the Sound Settings, there was also a
regression.

Steps to Reproduce:

1. Open Settings app and go to Sound section.
2. Click 'Test' button beside chosen Output Device.
3. Press the 'Front Left', 'Front Right', etc buttons and hear the 
corresponding output.
4. Change output device to a different device.
5. Try Step 3 again.

Expected: The test audio plays out of the newly selected device.
Actual: The test audio plays out of the previous device.

Toggling the device does not help. Nor does restarting the Settings app.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 12 01:40:21 2020
InstallationDate: Installed on 2018-09-01 (772 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: USB PnP Sound Device - USB PnP Sound Device
Symptom_PulseAudioLog:
 Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1
 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0
 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded.
 Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded.
Symptom_Type: Volume slider, or mixer problems
Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem
UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)
dmi.bios.date: 10/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2b
dmi.board.asset.tag: Default string
dmi.board.name: Z370N WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370N WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

  I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition
  to the appearance changes in the Sound Settings, there was also a
  regression.
  
  Steps to Reproduce:
  
  1. Open Settings app and go to Sound section.
  2. Click 'Test' button beside chosen Output Device.
  3. Press the 'Front Left', 'Front Right', etc buttons and hear the 
corresponding output.
  4. Change output device to a different device.
  5. Try Step 3 again.
  
  Expected: The test audio plays out of the newly selected device.
  Actual: The test audio plays out of the previous device.
  
  Toggling the device does not help. Nor does restarting the Settings app.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 12 01:40:21 2020
  InstallationDate: Installed on 2018-09-01 (772 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB PnP Sound Device - USB PnP Sound Device
  Symptom_PulseAudioLog:
-  Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
-  Oct 12 01:17:33 luq-home-pc pulseaudio[1281]: No UCM verb is valid for hw:1
-  Oct 12 01:17:34 luq-home-pc pulseaudio[1281]: No UCM verb is valid for hw:0
-  Oct 12 01:17:40 luq-home-pc systemd[1275]: pulseaudio.service: Succeeded.
-  Oct 12 01:17:51 luq-home-pc systemd[1275]: pulseaudio.socket: Succeeded.
+  Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-dae

[Desktop-packages] [Bug 1899442] Re: Test Output Device Button does not respect when you change the output device

Also interestingly, the little Testing window popup now lets you press
multiple buttons and hear the test sounds simultaneously whereas before
it was one at a time.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1899442

Title:
  Test Output Device Button does not respect when you change the output
  device

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in
  addition to the appearance changes in the Sound Settings, there was
  also a regression.

  Steps to Reproduce:

  1. Open Settings app and go to Sound section.
  2. Click 'Test' button beside chosen Output Device.
  3. Press the 'Front Left', 'Front Right', etc buttons and hear the 
corresponding output.
  4. Change output device to a different device.
  5. Try Step 3 again.

  Expected: The test audio plays out of the newly selected device.
  Actual: The test audio plays out of the previous device.

  Toggling the device does not help. Nor does restarting the Settings
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 12 01:40:21 2020
  InstallationDate: Installed on 2018-09-01 (772 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB PnP Sound Device - USB PnP Sound Device
  Symptom_PulseAudioLog:
   Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1
   Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0
   Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded.
   Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370N WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1899442] Re: Test Output Device Button does not respect when you change the output device

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1899442

Title:
  Test Output Device Button does not respect when you change the output
  device

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in
  addition to the appearance changes in the Sound Settings, there was
  also a regression.

  Steps to Reproduce:

  1. Open Settings app and go to Sound section.
  2. Click 'Test' button beside chosen Output Device.
  3. Press the 'Front Left', 'Front Right', etc buttons and hear the 
corresponding output.
  4. Change output device to a different device.
  5. Try Step 3 again.

  Expected: The test audio plays out of the newly selected device.
  Actual: The test audio plays out of the previous device.

  Toggling the device does not help. Nor does restarting the Settings
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 12 01:40:21 2020
  InstallationDate: Installed on 2018-09-01 (772 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB PnP Sound Device - USB PnP Sound Device
  Symptom_PulseAudioLog:
   Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1
   Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0
   Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded.
   Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370N WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1897170] Update Released

2020-10-12 Thread Łukasz Zemczak

The verification of the Stable Release Update for file-roller has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1897170

Title:
  SRU the current 3.36.3 stable update

Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that opening archives of different type still works correctly

  * Regression potential

  The update includes some fixes around drag and drop so that needs some
  extra testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1897170/+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 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

This bug was fixed in the package cheese - 3.34.0-1ubuntu1

---
cheese (3.34.0-1ubuntu1) focal; urgency=medium

  * debian/patches/gitlab_always_headerbar.patch:
- display the headerbar on any desktop since the compatibility menubar
  was removed, thanks esoleyman (lp: #1879183)

 -- Sebastien Bacher   Thu, 24 Sep 2020 21:37:10
+0200

** Changed in: cheese (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1879183

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Released
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+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 1897170] Re: SRU the current 3.36.3 stable update

This bug was fixed in the package file-roller - 3.36.3-0ubuntu1

---
file-roller (3.36.3-0ubuntu1) focal; urgency=medium

  * New stable update (lp: #1897170)

 -- Sebastien Bacher   Thu, 24 Sep 2020 20:53:08
+0200

** Changed in: file-roller (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1897170

Title:
  SRU the current 3.36.3 stable update

Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that opening archives of different type still works correctly

  * Regression potential

  The update includes some fixes around drag and drop so that needs some
  extra testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1897170/+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 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

2020-10-12 Thread Łukasz Zemczak

I have no reason to not believe the verification provided in comment
#20, as comment #21 does not provide any context and is rather
disrespectful. If this update does indeed cause a regression, please
fill a regression-update bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1879183

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Released
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+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 1879183] Update Released

2020-10-12 Thread Łukasz Zemczak

The verification of the Stable Release Update for cheese has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1879183

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Released
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+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 1899456] [NEW] [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)

2020-10-12 Thread Rico Tzschichholz

Public bug reported:

The yaru icon style is explicitly shipped within the ubuntu source
package of libreoffice.

libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28"

The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11"

Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru-
fullcolor/compare/2020-09-28...2020-10-11

Most noticeable visual changes:
* https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105
* https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121
* https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125
* https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Assignee: Rico Tzschichholz (ricotz)
 Status: New

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

-- 
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/1899456

Title:
   [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The yaru icon style is explicitly shipped within the ubuntu source
  package of libreoffice.

  libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28"

  The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11"

  Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru-
  fullcolor/compare/2020-09-28...2020-10-11

  Most noticeable visual changes:
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125
  * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name

This bug was fixed in the package accountsservice - 0.6.55-0ubuntu13

---
accountsservice (0.6.55-0ubuntu13) groovy; urgency=medium

  * debian/patches/0010-set-language.patch:
- Don't dismiss C.UTF-8 as an invalid locale name (LP: #1873678)

 -- Gunnar Hjalmarsson   Fri, 09 Oct 2020 15:08:15
+0200

** Changed in: accountsservice (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1873678

Title:
  gnome-language-selector crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is
  not a valid locale name

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  In Progress

Bug description:
  [Impact]

  accountsservice includes a function for checking the validity of
  locales, and it incorrectly considers "C.UTF-8" to be invalid. It
  leads to incorrect behavior under certain conditions and also a crash
  if the function was triggered from language-selector-gnome.

  Even if this only makes a difference in special corner cases, it
  happens often enough to justify this SRU:

  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=language-
  selector&period=year

  (It's the top ranked crash type in the list.)

  The version in focal-proposed fixes the issue.

  [Test case]

  Make a fresh install of Ubuntu 20.04 (a VM works fine)

  Once logged in:

  * Install accountsservice, gir1.2-accountsservice-1.0 and
libaccountsservice0 from focal-proposed

  * Open /etc/default/locale for editing, replace its contents with
the single line:

LANG=C.UTF-8

and reboot.

  Open Language Support and change language (drag any language above
  the "English" item)

  Open ~/.pam_environment and find that e.g. LANG is now the locale
  representing the language you selected, while e.g. LC_TIME is set to
  "C.UTF-8".

  [Regression risk]

  This is a oneliner which white list "C.UTF-8" as a valid locale name.
  I can't think of a case where this would cause unexpected behavior.

  [Original description]

  USB live disk (20.04 beta)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: MATE
  Date: Sun Apr 19 17:07:26 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: N/A
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a 
valid locale name
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-10-12 Thread Nick De Graeve

For me it is fixed since the latest kernel update, 5.4.0-48-generic.

- Ubuntu 20.04.1 LTS
- Dell XPS 15 7590
- Bose QuietComfort 35 II

-- 
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/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect

2020-10-12 Thread Detlef Niemann

had the same problem with my apple keyboard settings, downgrading solved
it. thanks.

-- 
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/1899206

Title:
  Tweaktool Keyboard “Additional Layout Options” not persisting on USB
  keyboard unplug/reconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which
  seems to have been introduced within the past couple of weeks. I have
  a couple custom keyboard settings configured in Tweaktool "Additional
  Layout Options". These settings work great.

  I have a USB keyboard plugged into the machine. If I have the keyboard
  plugged in when I start my Gnome session, the customized keyboard
  layout options are correctly applied to the USB keyboard. If I unplug
  and reconnect the keyboard, the keyboard does will _NOT_ have the
  customized keyboard settings.

  If I restart my Gnome session (using Alt-F2 -> "r"), the customized
  settings are applied to the keyboard.

  I think this behavior is something new. Before, I was able to
  unplug/reconnect my keyboard and it would apply my customized keyboard
  settings on reconnect. Is there anything I can do to force the
  application of the custom keyboard tweaks on USB keyboard reconnect?

  Is anyone else able to reproduce this? I don't have any other machines
  with Ubuntu 20.04.1 to test with.

  Thanks!

  (This is also cross-posted at askubuntu:
  https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional-
  layout-options-not-working)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-10-12 Thread Nick De Graeve

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

For me it is fixed since the latest kernel update, 5.4.0-48-generic.

- Ubuntu 20.04.1 LTS
- Dell XPS 15 7590
- Bose QuietComfort 35 II

-- 
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/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect

2020-10-12 Thread Gunnar Hjalmarsson

Thanks for testing. That helps us narrow down the cause of the issue.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Tags added: regression-update rls-ff-incoming

-- 
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/1899206

Title:
  Tweaktool Keyboard “Additional Layout Options” not persisting on USB
  keyboard unplug/reconnect

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which
  seems to have been introduced within the past couple of weeks. I have
  a couple custom keyboard settings configured in Tweaktool "Additional
  Layout Options". These settings work great.

  I have a USB keyboard plugged into the machine. If I have the keyboard
  plugged in when I start my Gnome session, the customized keyboard
  layout options are correctly applied to the USB keyboard. If I unplug
  and reconnect the keyboard, the keyboard does will _NOT_ have the
  customized keyboard settings.

  If I restart my Gnome session (using Alt-F2 -> "r"), the customized
  settings are applied to the keyboard.

  I think this behavior is something new. Before, I was able to
  unplug/reconnect my keyboard and it would apply my customized keyboard
  settings on reconnect. Is there anything I can do to force the
  application of the custom keyboard tweaks on USB keyboard reconnect?

  Is anyone else able to reproduce this? I don't have any other machines
  with Ubuntu 20.04.1 to test with.

  Thanks!

  (This is also cross-posted at askubuntu:
  https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional-
  layout-options-not-working)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899206/+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 1899283] Re: [UIFe] New Yaru theme with upstream fixes

This bug was fixed in the package yaru-theme - 20.10.6.1

---
yaru-theme (20.10.6.1) groovy; urgency=medium

  [ Frederik Feichtmeier ]
  * Fix nautilus icon view backdrop text (#2397)

  [ Marco Trevisan (Treviño) ]
  * UIFe for groovy (LP: #1899283)

yaru-theme (20.10.6) groovy; urgency=medium

  [ Paul Kepinski ]
  * Link insync emblems to our ones (#2375)
  * Fix question_arrow cursor outline color (#2385)

  [ Frederik Feichtmeier ]
  * Adapt shell links to gtk links: orange->blue (#2378)
  * Gtk theme: less shadows, gray sidebars (#2376)
  * Style HDY window widgets from libhandy (#2382)
  * Backdrop and border improvements (#2389)
- fix switch border in the dark theme being overly pronounced in the
  backdrop
- default theme pathbar border improvements for active and backdrop
- fix nautilus list view to use $backdrop_selected_fg_color and not some
  gray
- fix nautilus list view header to have the same bg color as the rest of
  the treeview in the backdrop
- revert nautilus icon view to be orange in the backdrop but with
  $backdrop_selected_fg_color

  [ Carlo Lobrano ]
  * Fix typo in meson project name.
  * calendar-other-month-day color shall not change if the day has an event.
(#2380, #2164)

  [ Muqtadir ]
  * add system-run-symbolic icon (#2379)
  * symlink text-x-r-source to text-x-r (#2374)
  * Gnome-clocks: added symlinks to alarm and globe (#2387)

yaru-theme (20.10.5) groovy; urgency=medium

  [ Paul Kepinski ]
  * Books rounded corners (#2363)
  * Links all disk icons to media-optical (#2369)
  * Add text-x-patch mimetype icon (#2353)

  [ Frederik Feichtmeier ]
  * _tweaks: remove circular button min-width (#2370)

 -- Marco Trevisan (Treviño)   Sat, 10 Oct 2020
21:12:58 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1899283

Title:
  [UIFe] New Yaru theme with upstream fixes

Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  There are new upstream changes for yaru, as upstream stated:

  We've pushed various fixes, no design changes, into master and also
  reverted the gray sidebar row (needs deeper testing). There is no
  design change only fixes for wrong colors or borders

  The changes are not visible but they revert that "gray" backdrop color in 
selection from the previous update (see differences at [1]).
  Design never even ack'ed the gray selection.
  So, to have orange rows and fixes for borders and this update is needed.

  Fixes impact particulary libhandy apps.

  Here's a list of mayor changes:

  clobrano & 3v1n0 | Fix typo in meson project name. | 96271d6
  Feichtmeier | Style HDY window widgets from libhandy (#2382) | 07b1d1f
  clobrano | calendar-other-month-day color shall not change if the day has 
an eve… | 3b02a88
  Muqtxdir | add system-run-symbolic icon (#2379) | 84574ea
  Muqtxdir | symlink text-x-r-source to text-x-r (#2374) | 89b1ee0
  Jupiter007-43 | Fix question_arrow cursor outline color (#2385) | 4c92718
  Muqtxdir | Gnome-clocks: added symlinks to alarm and globe (#2387) | 
0ecf271
  Feichtmeier | Backdrop and border improvements (#2389) | 78f5de1

  Except 84574ea [2] it's all fixes, especially 3b02a88, 07b1d1f and
  78f5de1 contain important fixes for the themes.

  The diff from the actual version in archive is here:
    https://github.com/ubuntu/yaru/compare/20.10.4...20.10.6

  Even though the diff would be from 20.04.5, but that had a build
  failure so can't be really counted.

  ubuntu-translators notified:

https://lists.ubuntu.com/archives/ubuntu-translators/2020-October/007717.html

  ubuntu-doc notified:
https://lists.ubuntu.com/archives/ubuntu-doc/2020-October/020763.html

  [1] https://imgur.com/a/GcJ1jnr
  [2] 
https://github.com/ubuntu/yaru/commit/84574ea018374c1b441c353e69603115435f5fff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1899283/+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 1899464] Re: En passant au nouveau paquet, j'ai perdu tout mon historique et mes onglet ouvert de la cession précédente...

2020-10-12 Thread didier culieras

L'historique...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1899464

Title:
  En passant au nouveau paquet, j'ai perdu tout mon historique et mes
  onglet ouvert de la cession précédente...

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Bonjour,
  Comment retrouver ma cession précédente et l'historique ?
  Merci

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899464/+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 1899464] Re: En passant au nouveau paquet, j'ai perdu tout mon historique et mes onglet ouvert de la cession précédente...

2020-10-12 Thread didier culieras

Récupérer l'historique...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1899464

Title:
  En passant au nouveau paquet, j'ai perdu tout mon historique et mes
  onglet ouvert de la cession précédente...

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Bonjour,
  Comment retrouver ma cession précédente et l'historique ?
  Merci

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899464/+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 1899464] [NEW] En passant au nouveau paquet, j'ai perdu tout mon historique et mes onglet ouvert de la cession précédente...

2020-10-12 Thread didier culieras

Public bug reported:

Bonjour,
Comment retrouver ma cession précédente et l'historique ?
Merci

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1899464

Title:
  En passant au nouveau paquet, j'ai perdu tout mon historique et mes
  onglet ouvert de la cession précédente...

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Bonjour,
  Comment retrouver ma cession précédente et l'historique ?
  Merci

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899464/+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 1899442] Re: Can't change output device from Settings

Updated description and title to indicate that the selected device
choice is not respected for all audio, not just the test audio.

** Summary changed:

- Test Output Device Button does not respect when you change the output device
+ Can't change output device from Settings

** Description changed:

I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition
to the appearance changes in the Sound Settings, there was also a
regression.

Steps to Reproduce:

1. Open Settings app and go to Sound section.
2. Click 'Test' button beside chosen Output Device.
3. Press the 'Front Left', 'Front Right', etc buttons and hear the
corresponding output.
4. Change output device to a different device.
5. Try Step 3 again.

Expected: The test audio plays out of the newly selected device.
Actual: The test audio plays out of the previous device.

Toggling the device does not help. Nor does restarting the Settings app.
+
+ Note: This isn't just the Test Audio. Currently playing audio won't
+ switch to the selected device, nor will any new audio started after the
+ switch.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 12 01:40:21 2020
InstallationDate: Installed on 2018-09-01 (772 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: USB PnP Sound Device - USB PnP Sound Device
Symptom_PulseAudioLog:
Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via
systemd: service name='org.freedesktop.RealtimeKit1'
unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1
Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0
Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded.
Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded.
Symptom_Type: Volume slider, or mixer problems
Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem
UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)
dmi.bios.date: 10/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2b
dmi.board.asset.tag: Default string
dmi.board.name: Z370N WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370N WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1899442

Title:
Can't change output device from Settings

Status in gnome-control-center package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
New

Bug description:
I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in
addition to the appearance changes in the Sound Settings, there was
also a regression.

Steps to Reproduce:

Expected: The test audio plays out of the newly selected device.
Actual: The test audio plays out of the previous device.

Toggling the device does not help. Nor does restarting the Settings
app.

Note: This isn't just the Test Audio. Currently playing audio won't
switch to the selected device, nor will any new audio started after
the switch.

[Desktop-packages] [Bug 1899442] Re: Can't change output device from Settings

*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194

Err, I mean lp:1866194 :P

** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1899442

Title:
  Can't change output device from Settings

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in
  addition to the appearance changes in the Sound Settings, there was
  also a regression.

  Steps to Reproduce:

  1. Open Settings app and go to Sound section.
  2. Click 'Test' button beside chosen Output Device.
  3. Press the 'Front Left', 'Front Right', etc buttons and hear the 
corresponding output.
  4. Change output device to a different device.
  5. Try Step 3 again.

  Expected: The test audio plays out of the newly selected device.
  Actual: The test audio plays out of the previous device.

  Toggling the device does not help. Nor does restarting the Settings
  app.

  Note: This isn't just the Test Audio. Currently playing audio won't
  switch to the selected device, nor will any new audio started after
  the switch.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 12 01:40:21 2020
  InstallationDate: Installed on 2018-09-01 (772 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB PnP Sound Device - USB PnP Sound Device
  Symptom_PulseAudioLog:
   Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1
   Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0
   Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded.
   Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370N WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1899442] Re: Can't change output device from Settings