date:20191009

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

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1711101/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1711101/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371] Re: firefox 70.0 beta 11 isn't fully translated

** Changed in: firefox
   Importance: Medium => High

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

Figured this out. Having some unrelated build issues right now but
should have a patch up tomorrow.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

Created attachment 9099938
Bug 1586216: Fallback to a synchronous channel load if the url preloader cannot 
load the ftl file. r=kmag

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

2019-10-09 Thread Pulsebot

Pushed by dtowns...@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ee1a9bce6d9e
Fallback to a synchronous channel load if the url preloader cannot load the ftl 
file. r=kmag

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

2019-10-09 Thread Lhenry

Is there anyone who can work on this for 70? This sounds like a serious
problem so I'm concerned since we're at the end of the beta cycle very
soon.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

2019-10-09 Thread Gandalf-aviary

Yeah, one of the main themes of bug 1462839 is to handle missing
resources. The Crux is to find a sweet spot between loading "missing"
contexts and skipping "mostly ok" ones.

I hope someone will tackle that soon since it hinders us.

Thank you Dave for putting works to solve this bug!

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

(In reply to Axel Hecht [:Pike] from comment #22)
> Ah, another one of those. Is this also gonna fix bug 1557713 ?

Looks like it.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

So the main problem here is that as things stand synchronously loading
ftl files from langpacks fail. Synchronous loads use
[`Cu.readUTF8URI`](https://searchfox.org/mozilla-
central/rev/05a22d864814cb1e4352faa4004e1f975c7d2eb9/intl/l10n/L10nRegistry.jsm#754)
which underneath uses the `URLPreloader` which [only supports file or
omnijar urls](https://searchfox.org/mozilla-
central/rev/05a22d864814cb1e4352faa4004e1f975c7d2eb9/js/xpconnect/loader/URLPreloader.cpp#565).
So attempting to load strings for browser.xhtml which uses synchronous
localization fails for the langpack and so falls back to the built-in
localization (yay for fallback!).

Unfortunately we cache these load failures which effectively poison the
langpack for future localization passes. In particular we cache the fact
that `branding/brand.ftl` isn't available in the langpack and then any
attempt to generate bundles that include `branding/brand.ftl` as a
resource (which the majority of pages do) fail because that file is
cached as missing. That seems like a different bug, I had the impression
that fluent would fall back on a per-resource level, not ignore the
entire locale if just one resource is missing, but we don't need to
solve that to fix this.

There are a couple of ways to solve this. Probably the ideal solution
would be to make the `URLPreloader` support loading out of langpacks.
But for a safer patch for beta I've just made `loadSync` fallback to an
alternative method of loading the ftl file in the event that
`Cu.readUTF8URI` fails.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846371]

2019-10-09 Thread L10n-mozilla

Ah, another one of those. Is this also gonna fix bug 1557713 ?

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

The upstream bug suggests this was fixed in PulseAudio 12.99.1, so
should be fixed in Ubuntu 19.10 now. Can anyone test that?

** Bug watch added: PulseAudio #185
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/185

** Changed in: pulseaudio
   Importance: Medium => Unknown

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #96211 => PulseAudio #185

** Tags removed: artful

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1711101/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

2019-10-09 Thread Shane Synan

I've had this issue in the past on Ubuntu 18.04 with the NVidia 340.x
driver series.  Two days ago with driver 340.107 and the latest released
system updates, the lockscreen wallpaper corrupted for about 2 seconds
on resume from suspend, then the wallpaper reloaded, appearing fine.  In
the past, the lockscreen wallpaper would remain corrupted for at least a
minute (presumably indefinitely, but I didn't wait to find out).

This issue might be somehow fixed, but I'll keep a look out to see if it
happens again and stays corrupted for longer than a minute.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Incomplete
Status in mutter source package in Disco:
  In Progress
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.

[Desktop-packages] [Bug 1846955] Re: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN

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

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

Title:
  Gnome crashes on adding system title bars to Chrome under Wayland in
  EOAN

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  To reproduce:
  1. Open Chrome under Wayland session in 19.10 beta
  2. Maximize Chrome
  3. Right click on empty space beside tabs and from the menu select "Use 
system titlebar and borders"

  Chrome immediately crashes and gnome begins to become less and less
  responsive until it finally freezes.

  Does not occur when doing the equivalent in Firefox

  BTW - Gnome is super responsive in Eoan! Keep up the good work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846955/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles

** Tags added: eoan regression-release rls-ee-incoming

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1652179] Re: gnome-tweak-tool "Show location of pointer" (now "Pointer Location") does not work under Wayland

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gnome-tweak-tool "Show location of pointer" (now "Pointer Location")
  does not work under Wayland

Status in GNOME Shell:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I have found that after switching from Xorg to Wayland via the login
  screen on Ubuntu GNOME 16.10 with GNOME 3.22 that the "Show location
  of pointer" gnome-tweak-tool option no longer functions in the sense
  that when the setting is on and I press CTRL nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 22 22:43:16 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1652179/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1827401] Re: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full

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

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

Title:
  gnome-shell crashed in meta_workspace_index ->
  meta_workspace_activate_with_focus -> meta_window_activate_full

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  Shell crashes on meta_workspace_index

  [ Test case ]

  No clear way to reproduce this, although we consider fixed monitoring
  the presence of automatic reports at:

  https://errors.ubuntu.com/problem/f98d5edcc7588c443201f119bc2c4b586a897cfd

  [ Regression potential ]

  None, a window might not be focused although it's an unmanaging one
  so, not really a regression.

  ---

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.1-2ubuntu1.18.10.2, the problem page at 
https://errors.ubuntu.com/problem/f98d5edcc7588c443201f119bc2c4b586a897cfd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  ---

  The gjs part of this is actually the same of bug #1812527

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1827401/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846955] Re: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN

2019-10-09 Thread Jason Gambrel

Thank you very much for the direction.  This will be helpful when I
report any future bugs.  I hadn't had time to look at this till today.
I decided to try and reproduce the bug to generate a new crash file, but
have been unable to reproduce it.  One of the updates from the past few
days must have solved it.

Thank you.

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

Title:
  Gnome crashes on adding system title bars to Chrome under Wayland in
  EOAN

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  To reproduce:
  1. Open Chrome under Wayland session in 19.10 beta
  2. Maximize Chrome
  3. Right click on empty space beside tabs and from the menu select "Use 
system titlebar and borders"

  Chrome immediately crashes and gnome begins to become less and less
  responsive until it finally freezes.

  Does not occur when doing the equivalent in Firefox

  BTW - Gnome is super responsive in Eoan! Keep up the good work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846955/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT: assertion failed
  "window->display->focus_window != window" in meta_window_unmanage

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  GNOME Shell crashes when interacting with some "take-input" windows
  such as the jetbrains products (you can snap install the 2008 versions
  which are affected), see
  https://gitlab.gnome.org/GNOME/mutter/issues/308

  [ Test case ]
   Run this script:
   $ wget -O - https://gitlab.gnome.org/3v1n0/mutter/snippets/453/raw | python3

   - The shell should not crash when the windows are closed.

  [ Regression potential ]

  The patch introduces changes to the window focus handling, so a window
  might not be properly focused in some cases.

  [ Notes to the SRU team ]

  This fix is still in process of being released to eoan / disco too.


  

  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/308

  Originally reported as bug 1422253 and fixed in 18.04, but that crash
  (fixed) was due to a different condition.

  Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453

  ---

  gnome-shell crashed and restarted while I was using it.

  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-1ubuntu1
  Uname: Linux 4.19.0-041900rc3-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 12:39:16 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1536081658
  InstallationDate: Installed on 2017-08-16 (389 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago)
  UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1791574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  App-switcher icons too small with hidpi monitor and 1.25 scaling

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  This is a bug upstream but since Ubuntu has its own fractional scaling
  patch for x11 you might be interested in working together with the
  gnome shell team.  I refer you to my detailed description and some
  preliminary analysis of the cause of the problem in gnome gitlab
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1325.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1831161/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847556] Re: package nvidia-340 340.107-0ubuntu6 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-340 340.107-0ubuntu6 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  occurred during 10.10 upgrade from 19.04

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-340 340.107-0ubuntu6
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  9 20:04:05 2019
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-09-07 (32 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.107-0ubuntu6 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-10-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1847556/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847556] [NEW] package nvidia-340 340.107-0ubuntu6 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10

2019-10-09 Thread Cat Clark

Public bug reported:

occurred during 10.10 upgrade from 19.04

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-340 340.107-0ubuntu6
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Wed Oct  9 20:04:05 2019
ErrorMessage: installed nvidia-340 package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2019-09-07 (32 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.107-0ubuntu6 failed to install/upgrade: installed 
nvidia-340 package post-installation script subprocess returned error exit 
status 10
UpgradeStatus: Upgraded to eoan on 2019-10-10 (0 days ago)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package eoan

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

Title:
  package nvidia-340 340.107-0ubuntu6 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  occurred during 10.10 upgrade from 19.04

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-340 340.107-0ubuntu6
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  9 20:04:05 2019
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-09-07 (32 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.107-0ubuntu6 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-10-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1847556/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles

** Changed in: mutter
   Status: Unknown => New

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841372] Re: Widget Layout Jumping when printing

** Changed in: gnome-control-center
   Status: Unknown => 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/1841372

Title:
  Widget Layout Jumping when printing

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

Bug description:
  While a print job is active, the layout in the printers panel becomes
  unusable. The dropdown for the gears icon is removed almost
  immediately after the click that opened it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Aug 25 12:11:11 2019
  InstallationDate: Installed on 2019-01-12 (224 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-27 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1841372/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

** Changed in: fftw3
   Status: Unknown => New

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in FFTW:
  New
Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

To manage notifications about this bug go to:
https://bugs.launchpad.net/fftw3/+bug/1843733/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847551] [NEW] Mutter 3.34.1 broke Night Light, screen color profiles

2019-10-09 Thread Anders Kaseorg

Public bug reported:

Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
color profile switching.  The commit at fault is
104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
when processing update” (which was intended to fix LP bug 1847044).

Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

** Affects: mutter
 Importance: Unknown
 Status: Unknown

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

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

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

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg

2019-10-09 Thread Treviño

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane  Wed, 09 Oct 2019 12:18:14 +0100


** Changed in: gnome-shell (Ubuntu Eoan)
   Status: In Progress => Fix Released

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

Title:
  Volume up/down repeat keys don't work on Xorg

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Released

Bug description:
  GNOME Shell & mutter on 3.33.91
  When pressing volume up or down on Xorg and keeping it pressed, only the 
first key event is sent, so the volume only goes up or down once, and doesn't 
scale up/down as long as you keep the button pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: U

[Desktop-packages] [Bug 1847545] [NEW] libgdk-pixbuf2.0-dev multiarch conflict

2019-10-09 Thread Benito van der Zander

Public bug reported:

It is not possible to install libgdk-pixbuf2.0-dev:i386 and libgdk-
pixbuf2.0-dev:amd64 together:

# apt install libgtk2.0-dev:i386

...

Get:12 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-gdkpixbuf-2.0 
i386 2.38.1+dfsg-1 [8.220 B]
Get:13 http://de.archive.ubuntu.com/ubuntu disco/universe i386 gir1.2-gtk-2.0 
i386 2.24.32-3ubuntu1 [172 kB]
Get:14 http://de.archive.ubuntu.com/ubuntu disco/main i386 libgdk-pixbuf2.0-dev 
i386 2.38.1+dfsg-1 [42,5 kB]

...

Selecting previously unselected package gir1.2-gdkpixbuf-2.0:i386.
(Reading database ... 286518 files and directories currently installed.)
Preparing to unpack .../00-gir1.2-gdkpixbuf-2.0_2.38.1+dfsg-1_i386.deb ...
Unpacking gir1.2-gdkpixbuf-2.0:i386 (2.38.1+dfsg-1) ...
Selecting previously unselected package gir1.2-gtk-2.0:i386.
Preparing to unpack .../01-gir1.2-gtk-2.0_2.24.32-3ubuntu1_i386.deb ...
Unpacking gir1.2-gtk-2.0:i386 (2.24.32-3ubuntu1) ...
Selecting previously unselected package libgdk-pixbuf2.0-dev:i386.
Preparing to unpack .../02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb ...
Unpacking libgdk-pixbuf2.0-dev:i386 (2.38.1+dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-HqtTOL/02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb 
(--unpack):
 trying to overwrite shared '/usr/share/gir-1.0/GdkPixbuf-2.0.gir', which is 
different from other instances of package libgdk-pixbuf2.0-dev:i386

I need this for cross compiling

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libgdk-pixbuf2.0-dev multiarch conflict

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  It is not possible to install libgdk-pixbuf2.0-dev:i386 and libgdk-
  pixbuf2.0-dev:amd64 together:

  # apt install libgtk2.0-dev:i386

  ...

  Get:12 http://de.archive.ubuntu.com/ubuntu disco/main i386 
gir1.2-gdkpixbuf-2.0 i386 2.38.1+dfsg-1 [8.220 B]
  Get:13 http://de.archive.ubuntu.com/ubuntu disco/universe i386 gir1.2-gtk-2.0 
i386 2.24.32-3ubuntu1 [172 kB]
  Get:14 http://de.archive.ubuntu.com/ubuntu disco/main i386 
libgdk-pixbuf2.0-dev i386 2.38.1+dfsg-1 [42,5 kB]

  ...

  Selecting previously unselected package gir1.2-gdkpixbuf-2.0:i386.
  (Reading database ... 286518 files and directories currently installed.)
  Preparing to unpack .../00-gir1.2-gdkpixbuf-2.0_2.38.1+dfsg-1_i386.deb ...
  Unpacking gir1.2-gdkpixbuf-2.0:i386 (2.38.1+dfsg-1) ...
  Selecting previously unselected package gir1.2-gtk-2.0:i386.
  Preparing to unpack .../01-gir1.2-gtk-2.0_2.24.32-3ubuntu1_i386.deb ...
  Unpacking gir1.2-gtk-2.0:i386 (2.24.32-3ubuntu1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-dev:i386.
  Preparing to unpack .../02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb ...
  Unpacking libgdk-pixbuf2.0-dev:i386 (2.38.1+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-HqtTOL/02-libgdk-pixbuf2.0-dev_2.38.1+dfsg-1_i386.deb 
(--unpack):
   trying to overwrite shared '/usr/share/gir-1.0/GdkPixbuf-2.0.gir', which is 
different from other instances of package libgdk-pixbuf2.0-dev:i386

  I need this for cross compiling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1847545/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1843817] Re: Changing input method on webpages requires pressing twice the hotkey

2019-10-09 Thread Yen-Yung Chang

Crtl+Space behaves normally on Chrome.

Also I've finally found a friend willing to test it for me. He runs
16.04LTS/gcin2.8.4/firefox69.01, and there's no issue at all. Not sure
how much this helps though as mine was also working before. Sorry I
can't find other Ubuntu/firefox user friends who speak the language and
use gcin. Thank.

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

Title:
  Changing input method on webpages requires pressing twice the hotkey

Status in firefox package in Ubuntu:
  Incomplete
Status in gcin package in Ubuntu:
  New

Bug description:
  I'm finding a weird behaviour of changing input method "only on
  webpages." I need to hit hotkey (Ctrl+Space) twice to trigger the
  change if my courser is in text boxes "on the page." If the courser is
  in URL bar or search bar or anywhere firebox window itself, this
  phenomenon doesn't exist. I am using gcin 2.8.9 and is switching
  between English and traditional Chinese. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  Uname: Linux 5.2.5-050205-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yenyung_chang   1727 F pulseaudio
  BuildID: 20190828152820
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 12 11:53:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-03-26 (170 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.108 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=69.0/20190828152820 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843817/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847543] [NEW] libatk1.0-dev multiarch conflict

2019-10-09 Thread Benito van der Zander

Public bug reported:

It is not possible to install libatk1.0-dev:i386 and libatk1.0-dev:amd64
together:

# apt install libatk1.0-dev:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  gir1.2-atk-1.0:i386
The following NEW packages will be installed:
  gir1.2-atk-1.0:i386 libatk1.0-dev:i386
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 109 kB of archives.
After this operation, 1.370 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-atk-1.0 i386 
2.32.0-1 [18,0 kB]
Get:2 http://de.archive.ubuntu.com/ubuntu disco/main i386 libatk1.0-dev i386 
2.32.0-1 [91,3 kB]
Fetched 109 kB in 0s (457 kB/s)  
Selecting previously unselected package gir1.2-atk-1.0:i386.
(Reading database ... 295431 files and directories currently installed.)
Preparing to unpack .../gir1.2-atk-1.0_2.32.0-1_i386.deb ...
Unpacking gir1.2-atk-1.0:i386 (2.32.0-1) ...
Selecting previously unselected package libatk1.0-dev:i386.
Preparing to unpack .../libatk1.0-dev_2.32.0-1_i386.deb ...
Unpacking libatk1.0-dev:i386 (2.32.0-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/gir-1.0/Atk-1.0.gir', which is 
different from other instances of package libatk1.0-dev:i386
Errors were encountered while processing:
 /var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


I need this for cross compiling

** Affects: atk1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libatk1.0-dev multiarch conflict

Status in atk1.0 package in Ubuntu:
  New

Bug description:
  It is not possible to install libatk1.0-dev:i386 and
  libatk1.0-dev:amd64 together:

  # apt install libatk1.0-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
gir1.2-atk-1.0:i386
  The following NEW packages will be installed:
gir1.2-atk-1.0:i386 libatk1.0-dev:i386
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 109 kB of archives.
  After this operation, 1.370 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-atk-1.0 i386 
2.32.0-1 [18,0 kB]
  Get:2 http://de.archive.ubuntu.com/ubuntu disco/main i386 libatk1.0-dev i386 
2.32.0-1 [91,3 kB]
  Fetched 109 kB in 0s (457 kB/s)  
  Selecting previously unselected package gir1.2-atk-1.0:i386.
  (Reading database ... 295431 files and directories currently installed.)
  Preparing to unpack .../gir1.2-atk-1.0_2.32.0-1_i386.deb ...
  Unpacking gir1.2-atk-1.0:i386 (2.32.0-1) ...
  Selecting previously unselected package libatk1.0-dev:i386.
  Preparing to unpack .../libatk1.0-dev_2.32.0-1_i386.deb ...
  Unpacking libatk1.0-dev:i386 (2.32.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb (--unpack):
   trying to overwrite shared '/usr/share/gir-1.0/Atk-1.0.gir', which is 
different from other instances of package libatk1.0-dev:i386
  Errors were encountered while processing:
   /var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  I need this for cross compiling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1847543/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane   Wed, 09 Oct 2019 12:18:14 +0100

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: In Progress => Fix Released

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

Title:
  GNOME Shell seemingly locked up at login

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Released

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the scr

[Desktop-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

2019-10-09 Thread Jason Gralinski

Same issue on Ubuntu 18.04 and 19.04.

I tested multiple Arch distros as well and ran into the same issue.

Sound through headphones and internal speakers is absent, USBC to
Headphone does work.

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1842910] Re: Desktop right click menu appears in the wrong place if a Terminal window is open

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane   Wed, 09 Oct 2019 12:18:14 +0100

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: In Progress => Fix Released

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

Title:
  Desktop right click menu appears in the wrong place if a Terminal
  window is open

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Released

Bug description:
  Desktop right click menu appears in the wrong place if a Terminal
  window is open.

  1. Open a Terminal

  2. Right click on the desktop.

  Expected: The menu appears where you click.
  Observed: The menu appears near the Terminal window instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-sh

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane   Wed, 09 Oct 2019 12:18:14 +0100

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c

[Desktop-packages] [Bug 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane   Wed, 09 Oct 2019 12:18:14 +0100

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Since upgrading to Eoan Ermine the screen doesn't dim progressively
  before turning off and locking the PC, but at once.

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  It wasn't behaving that way in Disco. Not sure if this issue belongs
  to X.org, but as that was the place for suspend/resume, i decided to
  place this bug here. If it's the wrong package, please help me in
  finding the correct one.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ub

[Desktop-packages] [Bug 1846083] Re: App Icons disappear on cursor hover

This bug was fixed in the package gnome-shell - 3.34.1-1ubuntu1

---
gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled
  * Refresh patches through gbp-pq

gnome-shell (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Allow editing app folder names
+ Do not notify systemd before initialization is complete
+ Don't leak NOTIFY_SOCKET environment variable to applications
+ Fix accidentally skipped animations
+ Fix box-shadow glitch with prerendered resources
+ Fix desktop right click menu appearing in the wrong place if a Terminal
  window is open (LP: #1842910)
+ Fix extra icons appearing in "Frequent" view animation
+ Fix fading out desktop icons (Closes: #940612)
+ Fix "Frequent" view icons disappearing on hover (LP: #1846083)
+ Fix lock-up on X11 when ibus is already running on startup (LP:
  #1845198)
+ Fix screen dimming on idle (LP: #1846941)
+ Fix screenshots and window animations when scaled
+ Fix various regressions with dynamic workspaces
+ Improve performance when enabling/disabling all extensions
+ Make menu animations more consistent
+ Skip property transitions while hidden
+ Support SAE secrets in network agent (LP: #1844422)
  * control: Require mutter 3.34.1

 -- Iain Lane   Wed, 09 Oct 2019 12:18:14 +0100

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  App Icons disappear on cursor hover

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell package in Fedora:
  Fix Released

Bug description:
  Click show applications then mouse over the icons.  They disappear
  when they should not.

  This has been reported and fixed upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1502

  $ lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  $ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.34.0-1ubuntu1
    Can

[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system

2019-10-09 Thread paz

@Oliver Tilloy (osomon): What I mean when I say "renders my machine
useless" - the system is freezing. I have to hard boot it after a short
time with only the home page of Firefox open. as long as I'm not
starting Firefox - the system is working without any issues at all. for
your question about updating, Yes I did.Unfortunately it didn't change
the situation for me.

I already tried the usual stuff - refreshed the browser,created a new profile 
but didn't help.
This is my first time ever I face such a strange unsolvable issue in Firefox.I 
have Ubuntu 16.04 (dual boot} And now I just forced to use it on a daily basis 
. if it was an hardware issue that could surface in the other system as well I 
believe.
Thanks for looking at it.
Paz  

** Summary changed:

- Latest Firefox update freezing my system 
+ Latest Firefox update freezing my system

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

Title:
  Latest Firefox update freezing my system

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The latest updates of firefox renders my machine useless. I'm sending
  it as is hopefully before it freezes completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  BuildID: 20190828152935
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 01:22:17 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-05-01 (506 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/20190828152935 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847488] Re: cups-browsed crashed with SIGSEGV in strlcpy()

2019-10-09 Thread Till Kamppeter

** Changed in: cups-filters (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  cups-browsed crashed with SIGSEGV in strlcpy()

Status in cups-filters package in Ubuntu:
  Fix Committed

Bug description:
  wasn't printing, but got this error

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  9 09:00:46 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-08-13 (56 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712)
  MachineType: Dell Inc. XPS 13 7390
  Papersize: letter
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=1f5f8d86-98e7-4c93-ab73-891051ab9a59 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f09e4691ba5 <__strlen_avx2+21>: vpcmpeqb 
(%rdi),%ymm0,%ymm1
   PC (0x7f09e4691ba5) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
   strlcpy () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   generate_sizes () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   ppdCreateFromIPP2 () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   ()
  Title: cups-browsed crashed with SIGSEGV in __strlen_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0192QD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0192QD:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1847488/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841372] Re: Widget Layout Jumping when printing

Thanks, could you also add your 'journalctl -b 0' log after triggering
the issue?

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/649
   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/1841372

Title:
  Widget Layout Jumping when printing

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

Bug description:
  While a print job is active, the layout in the printers panel becomes
  unusable. The dropdown for the gears icon is removed almost
  immediately after the click that opened it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Aug 25 12:11:11 2019
  InstallationDate: Installed on 2019-01-12 (224 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-27 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1841372/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847488] Re: cups-browsed crashed with SIGSEGV in strlcpy()

2019-10-09 Thread Till Kamppeter

Fixed upstream, 1.25.10 is on its way ...

** Changed in: cups-filters (Ubuntu)
   Status: New => In Progress

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

Title:
  cups-browsed crashed with SIGSEGV in strlcpy()

Status in cups-filters package in Ubuntu:
  In Progress

Bug description:
  wasn't printing, but got this error

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  9 09:00:46 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-08-13 (56 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712)
  MachineType: Dell Inc. XPS 13 7390
  Papersize: letter
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=1f5f8d86-98e7-4c93-ab73-891051ab9a59 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f09e4691ba5 <__strlen_avx2+21>: vpcmpeqb 
(%rdi),%ymm0,%ymm1
   PC (0x7f09e4691ba5) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
   strlcpy () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   generate_sizes () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   ppdCreateFromIPP2 () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   ()
  Title: cups-browsed crashed with SIGSEGV in __strlen_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0192QD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0192QD:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1847488/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Teunis Peters

Fixing PMF would be much higher priority than fixing SAE ;)
it's pretty important that behaves properly.

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846217] Re: [MIR] libextutils-depends-perl, libextutils-pkgconfig-perl (dependency of libcairo-gobject-perl)

2019-10-09 Thread Brian Murray

The Foundations team is happy to subscribe to the bugs about the
packages.

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

Title:
  [MIR] libextutils-depends-perl, libextutils-pkgconfig-perl (dependency
  of libcairo-gobject-perl)

Status in libcairo-gobject-perl package in Ubuntu:
  Confirmed
Status in libextutils-depends-perl package in Ubuntu:
  Incomplete
Status in libextutils-pkgconfig-perl package in Ubuntu:
  Incomplete

Bug description:
  [MIR] libextutils-depends-perl, libextutils-pkgconfig-perl (dependency
  of libcairo-gobject-perl)

  seen in component mismatches proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcairo-gobject-perl/+bug/1846217/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847196] Re: BackendException: PyDrive backend requires PyDrive installation

2019-10-09 Thread Michael Terry

Yes correct - ideally Ubuntu is able to package up pydrive. But in the
meantime, you can use the snap which should work.

Instructions here: https://wiki.gnome.org/Apps/DejaDup/Download

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

Title:
  BackendException: PyDrive backend requires PyDrive installation

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have deja-dup configured to do a back up to Google Drive. This
  worked until like a month or two ago, at which point it started to
  print

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'pydrive'

  There does not seem to be a pydrive module in the archive; and I
  thought it is using GOA anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct  8 09:02:38 2019
  InstallationDate: Installed on 2018-03-14 (572 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to eoan on 2018-11-20 (321 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1847196/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841372] Re: Widget Layout Jumping when printing

2019-10-09 Thread Manuel Barkhau

I reported it a while ago, doesn't seem like anybody is picking it up:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/649

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #649
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/649

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

Title:
  Widget Layout Jumping when printing

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

Bug description:
  While a print job is active, the layout in the printers panel becomes
  unusable. The dropdown for the gears icon is removed almost
  immediately after the click that opened it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Aug 25 12:11:11 2019
  InstallationDate: Installed on 2019-01-12 (224 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-27 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1841372/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847021] Re: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set

2019-10-09 Thread Gunnar Hjalmarsson

On 2019-10-09 05:18, Peng Wu wrote:
>> The dictionary built in conjunction with libpinyin 2.2 cannot be
>> ported to version 2.3.
> 
> @Gunnar Hjalmarsson: It will only clean up the user data, and provide
> better dictionary data in libpinyin.
> 
> Please use the tar ball release for packaging, thanks!

The latest libpinyin release, 2.3.0, will be used in Ubuntu 19.10.

But when you say "will only clean up the user data", does it mean that
an upgrade from 2.2.2 to 2.3.0 will automatically delete the users'
whole input history from the cache? Or do you mean something else?

I'm asking with the already released Ubuntu 18.04 and 19.04 in mind.
It's possible to do stable release updates of those, if the most recent
libpinyin version can be considered a pure bug fix release. However, if
the upgrade would automatically delete the users' input history, that
would be an interruption of the user experience which would not be
suitable for a stable release update.

Would appreciate if you could clarify.

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

Title:
  Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set

Status in ibus-libpinyin package in Ubuntu:
  Invalid

Bug description:
  See also https://github.com/libpinyin/ibus-libpinyin/issues/184

  Ubuntu 19.04. If I only install "Chinese (Intelligent Pinyin)", after
  pressing 'super+space' input is switched to Pinyin (can be seen from
  the icon on system bar). However it still input English directly. Even
  if I tried 'shift' button it's still the same.

  If I install "Chinese (Pinyin)" it works all perfect. If I install
  both "Chinese (Pinyin)" and "Chinese (Intelligent Pinyin)", both
  works.

  So, seems something is missing? Something required by Intelligent
  Pinyin but only installed with Pinyin?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ibus-libpinyin 1.11.0-1ubuntu0.19.04
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 17:24:17 2019
  InstallationDate: Installed on 2018-06-07 (487 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: Upgraded to disco on 2019-09-30 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1847021/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.63

** Summary changed:

- Don't update to 2.631
+ Don't update to 2.63

** Summary changed:

- Don't update to 2.63
+ Don't update to 2.63.1

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

Title:
  Don't update to 2.63.1

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Wayland: Image of mouse cursor left on screen after unlock

Status in mutter package in Ubuntu:
  New

Bug description:
  Gnome 3 desktop
  Multi-monitor setup with one screen rotated right into portrait mode
  *Experimental* fractional scaling on Wayland with different scaling on each 
monitor.  Configured using:

  ~~~
  gsettings set org.gnome.mutter experimental-features 
"['scale-monitor-framebuffer']"
  ~~~

  After wake from screen lock I often observe an "image" of an enlarged
  rotated mouse pointer on the second (rotated) monitor which doesn't
  move and doesn't appear on a screenshot.  It overlays all other screen
  in formation and cannot be erased by moving the mouse over the area.
  Depending on where the mouse cursor was when sleeping it seems to
  appear in one of two places, either towards the bottom left or top
  right.  After some time a block around the cursor image gets
  "corrupted".

  This behaviour is not observed if logging in to a X11 session

  Because this doesn't show up on a screenshot I have included a photo,
  which also shows the monitor setup.

  Description:  Ubuntu 19.04
  Release:  19.04

  mutter:
Installed: 3.32.2+git20190711-2ubuntu1~19.04.1
Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1
Version table:
   *** 3.32.2+git20190711-2ubuntu1~19.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.32.0+git20190410-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-08 (178 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-27-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago)
  UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

looks like the assert in in libavahi

** Information type changed from Private to Public

** Package changed: seahorse (Ubuntu) => avahi (Ubuntu)

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

Title:
  seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
  Assertion `!t->dead' failed.

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  -
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  -
  seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
   *** 3.32-1 500
  500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  -

  I have absolutely no idea why or how. Just collected this report from
  apport-cli.

  Some times receiving "internal error" reports, no details provided,
  just "Cancel" or "Send report" options. So, I decided to check apport
  and there was this report.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: seahorse 3.32-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 18:09:01 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2019-03-17 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  Signal: 6
  SourcePackage: seahorse
  StacktraceTop:
   __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at 
assert.c:101
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
  Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847488] Re: cups-browsed crashed with SIGSEGV in strlcpy()

** Information type changed from Private to Public

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

Title:
  cups-browsed crashed with SIGSEGV in strlcpy()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  wasn't printing, but got this error

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  9 09:00:46 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-08-13 (56 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712)
  MachineType: Dell Inc. XPS 13 7390
  Papersize: letter
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=1f5f8d86-98e7-4c93-ab73-891051ab9a59 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f09e4691ba5 <__strlen_avx2+21>: vpcmpeqb 
(%rdi),%ymm0,%ymm1
   PC (0x7f09e4691ba5) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
   strlcpy () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   generate_sizes () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   ppdCreateFromIPP2 () at /lib/x86_64-linux-gnu/libcupsfilters.so.1
   ()
  Title: cups-browsed crashed with SIGSEGV in __strlen_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0192QD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0192QD:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1847488/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1796554] Re: seahorse crashed with SIGSEGV in g_variant_unref()

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

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

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

Title:
  seahorse crashed with SIGSEGV in g_variant_unref()

Status in seahorse package in Ubuntu:
  Incomplete

Bug description:
  crash after pw changed

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: seahorse 3.30-1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 11:43:55 2018
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2018-10-04 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f27b08238c5 :mov
0x24(%rdi),%eax
   PC (0x7f27b08238c5) ok
   source "0x24(%rdi)" (0x983a3ef4) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: seahorse
  StacktraceTop:
   g_variant_unref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsecret-1.so.0
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: seahorse crashed with SIGSEGV in g_variant_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1796554/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1842910] Re: Desktop right click menu appears in the wrong place if a Terminal window is open

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  Desktop right click menu appears in the wrong place if a Terminal
  window is open

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Eoan:
  In Progress

Bug description:
  Desktop right click menu appears in the wrong place if a Terminal
  window is open.

  1. Open a Terminal

  2. Right click on the desktop.

  Expected: The menu appears where you click.
  Observed: The menu appears near the Terminal window instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.3+git20190814.1-1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  5 18:26:24 2019
  InstallationDate: Installed on 2019-05-02 (126 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1842910/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1843895] Re: Unable to launch seahorse

it looks similar to taht upstream report,
https://gitlab.gnome.org/GNOME/seahorse/issues/228

** Bug watch added: gitlab.gnome.org/GNOME/seahorse/issues #228
   https://gitlab.gnome.org/GNOME/seahorse/issues/228

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

Title:
  Unable to launch seahorse

Status in seahorse package in Ubuntu:
  Incomplete

Bug description:
  When I try to run seahorse, I've these errors:

  (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trappe pour point d'arrêt et de trace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1843895/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1798440] Re: passwords and keys crashes on entering zero password in 18.10

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

Title:
  passwords and keys crashes on entering zero password in 18.10

Status in seahorse package in Ubuntu:
  Incomplete

Bug description:
  Entering a blank login password crashes Passwords and Keys without
  saving

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-terminal 3.30.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 17 13:35:57 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-08-12 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to cosmic on 2018-10-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1798440/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

** Changed in: gnome-control-center
   Status: Unknown => 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/1845163

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1845163/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1832811] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

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

** This bug has been marked a duplicate of private bug 1820584

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

Title:
  seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
  Assertion `!t->dead' failed.

Status in seahorse package in Ubuntu:
  Confirmed

Bug description:
  Seahorse app has crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: seahorse 3.32-1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 14 10:02:49 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2019-06-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  Signal: 6
  SourcePackage: seahorse
  StacktraceTop:
   __assert_fail_base (fmt=0x7f21b50c8588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f21b514e02d "!t->dead", file=0x7f21b514e000 
"glib-watch.c", line=195, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f21b514e02d "!t->dead", file=0x7f21b514e000 
"glib-watch.c", line=195, function=0x7f21b514e1d8 "timeout_update") at 
assert.c:101
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
  Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1832811/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Giraffe

@teunis,

The point is NM (when setting WPA3-Personal as the security protocol)
will ALWAYS pass "ieee80211w=0"  this is NOT configurable on the client
even when setting PMF=2 in the config file.

The latest commit fixes this problem and thus is kind of important to
achieving the goal as set out in this bug.

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Teunis Peters

PMF is controlled from AP side over which - mine is always PMF required with 
SAE, for instance, even if it's optional for WPA-PSK on the same SSID.
(that's a configurable option)

PMF should be enabled if at all possible.  PMF optional : mode 1 - recommended 
as long as the driver supports it, and pmf 2 - required - should be the other 
choice.   PMF disabled is only for systems where security is not an issue or 
the driver is known not to function.
It should raise a security alert if PMF is disabled. (eg: warning: this reduces 
security considerably)

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846882] Re: Thunderbird crashes when clicking on menu item

2019-10-09 Thread Olivier Tilloy

Could you try removing extension from the add-on store, closing
thunderbird, installing enigmail from the Ubuntu archive, and see if
this "fixes" the problem?

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

Title:
  Thunderbird crashes when clicking on menu item

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Thunderbird 1:68.1.1+build1-0ubuntu1 On Ubuntu 19.10 fully updated.

  When writing an email, upon clicking on Enigmail in the menu bar,
  Thunderbird crashes.

  I contacted Enigmail’s lead dev about the issue who wrote:

  "…but even if the crash is initiated by Enigmail, the cause is
  certainly in Thunderbird. Enigmail is purely JavaScript and XUL - and by
  definition of the programming languages, these two cannot crash
  Thunderbird."

  I tried Thunderbird 68.1.1 from Mozilla’s site, and can’t
  reproduce the problem with it.

  Here is Thunderbird’s log upon crashing:

  AdapterDeviceID: 0x1912
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 19.3.0.0
  AdapterVendorID: 0x8086
  Add-ons:
  
%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D:68.1.1,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.1.2,antidote7_linux_thunderbird_102%40druide.com:10.1.30,en-CA%40dictionaries.addons.mozilla.org:3.1.0,fr-dicollecte%40dictionaries.addons.mozilla.org:6.3.1webext,wetransfer%40extensions.thunderbird.net:2.0.0,thunderbird-compact-dark%40mozilla.org:1.0,google%40search.mozilla.org:1.0,bing%40search.mozilla.org:1.0,amazon%40search.mozilla.org:1.1,ddg%40search.mozilla.org:1.0,qwant%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,langpack-fr%40thunderbird.mozilla.org:68.0,wetransfer%40extensions.thunderbird.net:2.0.0
  BuildID: 20191001201558
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 0
  CrashTime: 1570225903
  EventLoopNestingLevel: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1570020285
  IsWayland: 0
  Notes: Ubuntu Eoan Ermine (development
  branch)FP(D00-L1000-W-T000) WR? WR- OMTP? OMTP+3
  ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
  ProductName: Thunderbird
  ReleaseChannel: release
  SafeMode: 0
  SecondsSinceLastCrash: 383
  StartupCrash: 0
  StartupTime: 1570225565
  ThreadIdNameMapping: 20357:"Gecko_IOThread",20358:"JS
  Watchdog",20359:"JS Helper",20360:"JS Helper",20361:"JS
  Helper",20362:"JS Helper",20363:"Link Monitor",20364:"Socket
  Thread",20372:"Timer",20373:"Cache2
  I/O",20375:"DataStorage",20376:"Cookie",20379:"GMPThread",20380:"Worker
  Launcher",20381:"SoftwareVsyncThread",20382:"Compositor",20383:"ImgDecoder
  #1",20384:"ImageIO",20390:"ImageBridgeChild",20391:"IPDL
  Background",20392:"DOM Worker",20394:"HTML5
  
Parser",20397:"StyleThread#1",20396:"StyleThread#0",20398:"StyleThread#2",20401:"mozStorage
  #1",20407:"localStorage DB",20408:"ImgDecoder #2",20410:"Cache
  I/O",20411:"DNS Resolver #1",20412:"URL Classifier",20413:"Classifier
  Update",20415:"QuotaManager IO",20426:"DNS Resolver #2",20427:"DNS
  Resolver #3",20429:"ImgDecoder #3",20439:"mozStorage #3",20452:"DOM
  Worker",20467:"mozStorage #5",20468:"mozStorage #6",20469:"mozStorage
  #7",20479:"DOM Worker",20500:"mozStorage #8",27048:"StreamTrans #18",
  Throttleable: 1
  UptimeTS: 337.7284093
  Vendor:
  Version: 68.1.1
  useragent_locale: fr

  This is what I get when running Thunderbird from the console and after
  the crash occurred:

  1570277554871 addons.xpi  WARNCan't get modified time of 
/usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net
  1570277554912 addons.xpi-utilsWARNupdateMetadata: Add-on 
wetrans...@extensions.thunderbird.net is invalid: [Exception... "Component 
returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) 
[nsIFile.isFile]"  nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)" 
 location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: get :: 
line 235"  data: no] Stack trace: 
get()@resource://gre/modules/addons/XPIInstall.jsm:235
  syncLoadManifest()@resource://gre/modules/addons/XPIInstall.jsm:745
  updateMetadata()@resource://gre/modules/addons/XPIDatabase.jsm:2821
  updateExistingAddon()@resource://gre/modules/addons/XPIDatabase.jsm:3036
  processFileChanges()@resource://gre/modules/addons/XPIDatabase.jsm:3125
  checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:2946
  startup()@resource://gre/modules/addons/XPIProvider.jsm:2406
  callProvider()@resource://gre/modules/AddonManager.jsm:213
  _startProvider()@resource://gre/modules/AddonManager.jsm:649
  startup()@resource://gre/modules/AddonManager.jsm:873
  startup()@resource://gre/modules/AddonManager.jsm:3469
  observe()@resource://gre/modules/addonManager.js:70
  1570277554913 addons.xpi-utilsWARNCould not uninstall invalid 
item from locked install loc

[Desktop-packages] [Bug 1847514] Re: libssh-0.8 is detected as 0.7

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

** Changed in: libssh (Ubuntu)
   Status: New => Confirmed

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

Title:
  libssh-0.8 is detected as 0.7

Status in libssh package in Ubuntu:
  Confirmed

Bug description:
  QEMU consumes the library and its configure script use the libssh pkg-config 
cflags.
  The it checks if ssh_get_server_publickey() is present and assume it is a 
libssh-0.8 based.

  Ubuntu libssh is not based on upstream 0.8 but on the 0.7 branch, with commit 
bbd052202 cherry-picked. This commit adds the ssh_get_server_publickey() 
function that QEMU uses to check 0.8 compatibility.
  Now commit 963c46e4f is present in libssh-0.8 but has not been cherry-picked 
by Ubuntu, so QEMU fails at compiling because the ssh_known_hosts_e enums this 
commit introduced are missing.

  QEMU tracker is https://bugs.launchpad.net/qemu/+bug/1838763

  How to reproduce:

  - install libssh-dev

  - try to build QEMU 4.1 (sources from
  https://www.qemu.org/download/#source)

  $ ./configure
  ...
  libssh support yes
  ...

  $ make
  ...
CC block/ssh.o
  block/ssh.c: In function 'check_host_key_knownhosts':
  block/ssh.c:281:28: error: storage size of 'state' isn't known
   enum ssh_known_hosts_e state;
  ^
  block/ssh.c:289:13: error: implicit declaration of function 
'ssh_session_is_known_server' [-Werror=implicit-function-declaration]
   state = ssh_session_is_known_server(s->session);
   ^~~
  block/ssh.c:289:13: error: nested extern declaration of 
'ssh_session_is_known_server' [-Werror=nested-externs]
  block/ssh.c:293:10: error: 'SSH_KNOWN_HOSTS_OK' undeclared (first use in this 
function); did you mean 'SSH_OPTIONS_HOSTKEYS'?
   case SSH_KNOWN_HOSTS_OK:
^~
SSH_OPTIONS_HOSTKEYS
  block/ssh.c:293:10: note: each undeclared identifier is reported only once 
for each function it appears in
  block/ssh.c:297:10: error: 'SSH_KNOWN_HOSTS_CHANGED' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OK'?
   case SSH_KNOWN_HOSTS_CHANGED:
^~~
SSH_KNOWN_HOSTS_OK
  block/ssh.c:301:48: error: 'SSH_PUBLICKEY_HASH_SHA256' undeclared (first use 
in this function); did you mean 'SSH_PUBLICKEY_HASH_SHA1'?
   r = ssh_get_publickey_hash(pubkey, SSH_PUBLICKEY_HASH_SHA256,
  ^
  SSH_PUBLICKEY_HASH_SHA1
  block/ssh.c:307:27: error: implicit declaration of function 
'ssh_get_fingerprint_hash'; did you mean 'ssh_get_pubkey_hash'? 
[-Werror=implicit-function-declaration]
   fingerprint = ssh_get_fingerprint_hash(SSH_PUBLICKEY_HASH_SHA256,
 ^~~~
 ssh_get_pubkey_hash
  block/ssh.c:307:27: error: nested extern declaration of 
'ssh_get_fingerprint_hash' [-Werror=nested-externs]
  block/ssh.c:324:10: error: 'SSH_KNOWN_HOSTS_OTHER' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OK'?
   case SSH_KNOWN_HOSTS_OTHER:
^
SSH_KNOWN_HOSTS_OK
  block/ssh.c:329:10: error: 'SSH_KNOWN_HOSTS_UNKNOWN' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_CHANGED'?
   case SSH_KNOWN_HOSTS_UNKNOWN:
^~~
SSH_KNOWN_HOSTS_CHANGED
  block/ssh.c:333:10: error: 'SSH_KNOWN_HOSTS_NOT_FOUND' undeclared (first use 
in this function); did you mean 'SSH_KNOWN_HOSTS_UNKNOWN'?
   case SSH_KNOWN_HOSTS_NOT_FOUND:
^
SSH_KNOWN_HOSTS_UNKNOWN
  block/ssh.c:337:10: error: 'SSH_KNOWN_HOSTS_ERROR' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OTHER'?
   case SSH_KNOWN_HOSTS_ERROR:
^
SSH_KNOWN_HOSTS_OTHER
  block/ssh.c:281:28: error: unused variable 'state' [-Werror=unused-variable]
   enum ssh_known_hosts_e state;
  ^
  cc1: all warnings being treated as errors
  rules.mak:69: recipe for target 'block/ssh.o' failed
  make: *** [block/ssh.o] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libssh-dev 0.8.0~20170825.94fa1e38-1ubuntu0.2
  Uname: Linux 5.2.17-200.fc30.x86_64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct  9 18:21:25 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: libssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1847514/+subscriptions

-- 
Mailing list: https://launchp

[Desktop-packages] [Bug 1847514] [NEW] libssh-0.8 is detected as 0.7

2019-10-09 Thread Philippe Mathieu-Daudé

Public bug reported:

QEMU consumes the library and its configure script use the libssh pkg-config 
cflags.
The it checks if ssh_get_server_publickey() is present and assume it is a 
libssh-0.8 based.

Ubuntu libssh is not based on upstream 0.8 but on the 0.7 branch, with commit 
bbd052202 cherry-picked. This commit adds the ssh_get_server_publickey() 
function that QEMU uses to check 0.8 compatibility.
Now commit 963c46e4f is present in libssh-0.8 but has not been cherry-picked by 
Ubuntu, so QEMU fails at compiling because the ssh_known_hosts_e enums this 
commit introduced are missing.

QEMU tracker is https://bugs.launchpad.net/qemu/+bug/1838763

How to reproduce:

- install libssh-dev

- try to build QEMU 4.1 (sources from
https://www.qemu.org/download/#source)

$ ./configure
...
libssh support yes
...

$ make
...
  CC block/ssh.o
block/ssh.c: In function 'check_host_key_knownhosts':
block/ssh.c:281:28: error: storage size of 'state' isn't known
 enum ssh_known_hosts_e state;
^
block/ssh.c:289:13: error: implicit declaration of function 
'ssh_session_is_known_server' [-Werror=implicit-function-declaration]
 state = ssh_session_is_known_server(s->session);
 ^~~
block/ssh.c:289:13: error: nested extern declaration of 
'ssh_session_is_known_server' [-Werror=nested-externs]
block/ssh.c:293:10: error: 'SSH_KNOWN_HOSTS_OK' undeclared (first use in this 
function); did you mean 'SSH_OPTIONS_HOSTKEYS'?
 case SSH_KNOWN_HOSTS_OK:
  ^~
  SSH_OPTIONS_HOSTKEYS
block/ssh.c:293:10: note: each undeclared identifier is reported only once for 
each function it appears in
block/ssh.c:297:10: error: 'SSH_KNOWN_HOSTS_CHANGED' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OK'?
 case SSH_KNOWN_HOSTS_CHANGED:
  ^~~
  SSH_KNOWN_HOSTS_OK
block/ssh.c:301:48: error: 'SSH_PUBLICKEY_HASH_SHA256' undeclared (first use in 
this function); did you mean 'SSH_PUBLICKEY_HASH_SHA1'?
 r = ssh_get_publickey_hash(pubkey, SSH_PUBLICKEY_HASH_SHA256,
^
SSH_PUBLICKEY_HASH_SHA1
block/ssh.c:307:27: error: implicit declaration of function 
'ssh_get_fingerprint_hash'; did you mean 'ssh_get_pubkey_hash'? 
[-Werror=implicit-function-declaration]
 fingerprint = ssh_get_fingerprint_hash(SSH_PUBLICKEY_HASH_SHA256,
   ^~~~
   ssh_get_pubkey_hash
block/ssh.c:307:27: error: nested extern declaration of 
'ssh_get_fingerprint_hash' [-Werror=nested-externs]
block/ssh.c:324:10: error: 'SSH_KNOWN_HOSTS_OTHER' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OK'?
 case SSH_KNOWN_HOSTS_OTHER:
  ^
  SSH_KNOWN_HOSTS_OK
block/ssh.c:329:10: error: 'SSH_KNOWN_HOSTS_UNKNOWN' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_CHANGED'?
 case SSH_KNOWN_HOSTS_UNKNOWN:
  ^~~
  SSH_KNOWN_HOSTS_CHANGED
block/ssh.c:333:10: error: 'SSH_KNOWN_HOSTS_NOT_FOUND' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_UNKNOWN'?
 case SSH_KNOWN_HOSTS_NOT_FOUND:
  ^
  SSH_KNOWN_HOSTS_UNKNOWN
block/ssh.c:337:10: error: 'SSH_KNOWN_HOSTS_ERROR' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OTHER'?
 case SSH_KNOWN_HOSTS_ERROR:
  ^
  SSH_KNOWN_HOSTS_OTHER
block/ssh.c:281:28: error: unused variable 'state' [-Werror=unused-variable]
 enum ssh_known_hosts_e state;
^
cc1: all warnings being treated as errors
rules.mak:69: recipe for target 'block/ssh.o' failed
make: *** [block/ssh.o] Error 1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libssh-dev 0.8.0~20170825.94fa1e38-1ubuntu0.2
Uname: Linux 5.2.17-200.fc30.x86_64 x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Wed Oct  9 18:21:25 2019
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
SourcePackage: libssh
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libssh (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic

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

Title:
  libssh-0.8 is detected as 0.7

Status in libssh package in Ubuntu:
  Confirmed

Bug description:
  QEMU consumes the library and its configure script use the libssh pkg-config 
cflags.
  The it checks if ssh_get_server_publickey() is present and assume it is a 
libssh-0.8 based.

  Ubuntu libssh is not based on upstream 0.8 but on the 0.7 branch, with commit 
bbd052202 cherry-picked. This commit ad

[Desktop-packages] [Bug 1846249] Re: Num lock works in reverse on Ubuntu 19.10 wayland

2019-10-09 Thread Bickhaus

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Fix Released

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

Title:
  Num lock works in reverse on Ubuntu 19.10 wayland

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  I updated to the Ubuntu 19.10 beta yesterday, and since updating, the
  num lock key on my keyboard (DASKeyboard Prime 13 from System76) is
  reversed.  When it is on (indicator light is lit), the numbers do not
  work, but the arrows, page up/down, home, end keys, etc. work.  When
  it is off, the numbers work and the arrows, etc. are disabled.
  Viewing the image of my keyboard layout (English US) in the Regions
  and Language section of GNOME settings shows Num Lock lit up when it
  is not lit on the keyboard and vice versa.

  I use the Wayland session, and this issue was not present prior to
  upgrading (I originally installed 18.10 and then upgraded to 19.04.).
  It is not present if I use another keyboard (I booted with a LITE-ON
  SK-9020 which uses USB like the DASKeyboard.).  It is not present
  while using the DASKeyboard, if I log into an X session, rather than
  Wayland.  I also tried changing the keyboard language, deleting the
  English (US) language and then switching back (so I am now back on the
  English (US) layout).  That did not work.

  I ran the commands specified on the Ubuntu Wiki's
  debuggingKeyboardDetection page.  The output of lsusb -v is attached
  as an attachment.  I do not have gconftool-2 installed, so I did not
  run that.  The output of xprop -root | grep XKB > ~/xk is:

  _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: x11-utils 7.7+4build1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 11:17:31 2019
  DistUpgraded: 2019-09-30 20:21:51,653 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [148c:2379]
  InstallationDate: Installed on 2019-03-19 (195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: x11-utils
  UpgradeStatus: Upgraded to eoan on 2019-10-01 (0 days ago)
  dmi.bios.date: 09/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1820
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1846249/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 344257]

2019-10-09 Thread Qa-admin-q

Dear Christopher M. Penalver,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
[upstream] Impress truncates display of slide notes

Status in LibreOffice:
Confirmed
Status in OpenOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Status in openoffice.org package in Ubuntu:
Won't Fix

Bug description:
1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-impress
libreoffice-impress:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
*** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386
Packages
100 /var/lib/dpkg/status
1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

3) What is expected to happen in LibreOffice Impress via the Terminal:

cd ~/Desktop && wget

https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/344257/+attachment/497929/+files/Review.ppt
&& loimpress -nologo Review.ppt

on slide 6 click the Notes tab and all the notes are able to be
scrolled down to.

4) What happen instead is a text box is created whose boundaries are
farther down then one is allowed to scroll down to. Hence, one cannot
see all the available note text.

WORKAROUND: Highlight the text and resize to 10 so all text is visible.
WORKAROUND: Make sure extraneous spaces after text are removed before
exporting via PowerPoint.

Original Report Comments: The slide has been uploaded with the
permission of Professor Sriram Mohan for use in resolving this ticket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/344257/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1825741]

2019-10-09 Thread Mikekaganski

*** Bug 123484 has been marked as a duplicate of this bug. ***

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1825741]

2019-10-09 Thread Samuel Mehrbrodt

*** Bug 122287 has been marked as a duplicate of this bug. ***

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1825741]

2019-10-09 Thread Libreoffice-commits

Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to "libreoffice-6-2":

https://git.libreoffice.org/core/commit/fd95a92d600b751ad6a23f35db446bf063cb722b

tdf#124391 Fix doubled menu in global menu

It will be available in 6.2.9.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1825741]

2019-10-09 Thread Libreoffice-commits

Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to "libreoffice-6-2-8":

https://git.libreoffice.org/core/commit/46a575a64851512584abcddb0d30b907865251ce

tdf#124391 Fix doubled menu in global menu

It will be available in 6.2.8.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1825741]

2019-10-09 Thread Libreoffice-commits

Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to "libreoffice-6-3":

https://git.libreoffice.org/core/commit/eccf0193885d1e46a207966eb52a408dc60e8109

tdf#124391 Fix doubled menu in global menu

It will be available in 6.3.3.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

2019-10-09 Thread Cristiano Gavião

In my case with Ubuntu 18.04.2, In order to reestablish the sound after
have removed the HDMI cable I need: to reattach the HDMI cable and turn
the TV on. Only then I can change the selected sound board to Built-in
Audio again and only after that I can detach the HDMI cable.

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1711101/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Giraffe

@seb128
The Current version will not connect to WPA3-SAE secured Wi-Fi without that 
commit (being able to connect to WPA3-personal secured Wi-Fi is the whole point 
of this bug). 

This is because 802.11w is mandatory for WPA3-SAE (though it can be
disabled for certain configs) and NetworkManager up and until 1.20.4
passes "ieee80211w=0" (which disables 802.11w).

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

Why is it incomplete? Is the current version not working without that
commit?

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1845031] Re: gnome not remembering numlock state in eoan

This bug was fixed in the package mutter - 3.34.1-1ubuntu1

---
mutter (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Fix focusing of Java applications (LP: #1847184)
+ Fix freeze of pointer event delivery on X11
+ Fix initial view perspective
+ Fix memory leak when using implicit animations
+ Fix _NET_ACTIVE_WINDOW emission
+ Fix numlock state for native backend (LP: #1845031)
+ Fix scaling of DND surface actors
+ Fix scaling of stylus input coordinates with HiDPI
+ Fix screenshots and window animations when scaled
+ Fix startup of X11 session services on wayland
+ kms: Predict state changes when processing update (LP: #1847044)
+ Optimize blitting of untransformed offscreen stage views
+ Re-enable coredumps when capabilities are set
  * Drop several upstream backports which are now applied
- d/p/build-Compile-with-ffloat-store-on-x86-32-bit.patch
- d/p/clutter-actor-Cancel-delayed-timelines-on-removal.patch
- d/p/clutter-timeline-Don-t-emit-paused-signal-on-delayed-time.patch
- d/p/clutter-timeline-Use-a-function-to-cancel-the-delay-timeo.patch
- d/p/core-Split-x11-display-initialization-in-2-signals.patch
- d/p/x11-Minor-refactor-of-input-focus-handling-code.patch
- d/p/x11-Use-the-currently-focused-X-window-for-_NET_ACTIVE_WI.patch
  * rules: Skip tests when DEB_BUILD_OPTIONS=nocheck is set

mutter (3.34.0-4) unstable; urgency=medium

  * Team upload.
  * Upload to unstable.

 -- Iain Lane   Wed, 09 Oct 2019 12:18:44 +0100

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome not remembering numlock state in eoan

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  in 3.34, gnome-settings-daemon has removed its handling of numlock
  state persistence, claiming that mutter should be handling that now
  (https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/710a4c4e7828828cb35ea14333882354ae73264f).  However,
  numlock is always off when I start a session, and does not get
  remembered when I turn it on, log out, and log back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 23 11:15:27 2019
  InstallationDate: Installed on 2019-08-17 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847044] Re: gnome-shell crashed with SIGSEGV in meta_output_kms_read_edid() from meta_monitor_manager_handle_get_resources() from ffi_call_unix64() from ffi_call() from g_cclo

This bug was fixed in the package mutter - 3.34.1-1ubuntu1

---
mutter (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Fix focusing of Java applications (LP: #1847184)
+ Fix freeze of pointer event delivery on X11
+ Fix initial view perspective
+ Fix memory leak when using implicit animations
+ Fix _NET_ACTIVE_WINDOW emission
+ Fix numlock state for native backend (LP: #1845031)
+ Fix scaling of DND surface actors
+ Fix scaling of stylus input coordinates with HiDPI
+ Fix screenshots and window animations when scaled
+ Fix startup of X11 session services on wayland
+ kms: Predict state changes when processing update (LP: #1847044)
+ Optimize blitting of untransformed offscreen stage views
+ Re-enable coredumps when capabilities are set
  * Drop several upstream backports which are now applied
- d/p/build-Compile-with-ffloat-store-on-x86-32-bit.patch
- d/p/clutter-actor-Cancel-delayed-timelines-on-removal.patch
- d/p/clutter-timeline-Don-t-emit-paused-signal-on-delayed-time.patch
- d/p/clutter-timeline-Use-a-function-to-cancel-the-delay-timeo.patch
- d/p/core-Split-x11-display-initialization-in-2-signals.patch
- d/p/x11-Minor-refactor-of-input-focus-handling-code.patch
- d/p/x11-Use-the-currently-focused-X-window-for-_NET_ACTIVE_WI.patch
  * rules: Skip tests when DEB_BUILD_OPTIONS=nocheck is set

mutter (3.34.0-4) unstable; urgency=medium

  * Team upload.
  * Upload to unstable.

 -- Iain Lane   Wed, 09 Oct 2019 12:18:44 +0100

** Changed in: mutter (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in meta_output_kms_read_edid() from
  meta_monitor_manager_handle_get_resources() from ffi_call_unix64()
  from ffi_call() from g_cclosure_marshal_generic()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2892a201afc7ebc8b3465969f25711c11085713e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847044/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847184] Re: java Keyboard stops working after a dialog is shown

This bug was fixed in the package mutter - 3.34.1-1ubuntu1

---
mutter (3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.34.1-1) unstable; urgency=medium

  * New upstream release
+ Fix focusing of Java applications (LP: #1847184)
+ Fix freeze of pointer event delivery on X11
+ Fix initial view perspective
+ Fix memory leak when using implicit animations
+ Fix _NET_ACTIVE_WINDOW emission
+ Fix numlock state for native backend (LP: #1845031)
+ Fix scaling of DND surface actors
+ Fix scaling of stylus input coordinates with HiDPI
+ Fix screenshots and window animations when scaled
+ Fix startup of X11 session services on wayland
+ kms: Predict state changes when processing update (LP: #1847044)
+ Optimize blitting of untransformed offscreen stage views
+ Re-enable coredumps when capabilities are set
  * Drop several upstream backports which are now applied
- d/p/build-Compile-with-ffloat-store-on-x86-32-bit.patch
- d/p/clutter-actor-Cancel-delayed-timelines-on-removal.patch
- d/p/clutter-timeline-Don-t-emit-paused-signal-on-delayed-time.patch
- d/p/clutter-timeline-Use-a-function-to-cancel-the-delay-timeo.patch
- d/p/core-Split-x11-display-initialization-in-2-signals.patch
- d/p/x11-Minor-refactor-of-input-focus-handling-code.patch
- d/p/x11-Use-the-currently-focused-X-window-for-_NET_ACTIVE_WI.patch
  * rules: Skip tests when DEB_BUILD_OPTIONS=nocheck is set

mutter (3.34.0-4) unstable; urgency=medium

  * Team upload.
  * Upload to unstable.

 -- Iain Lane   Wed, 09 Oct 2019 12:18:44 +0100

** Changed in: mutter (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  java Keyboard stops working after a dialog is shown

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 19.10 + Gnome + Wayland, after a dialog (any dialog) is
  shown, the keyboard stops working in Intellij - the editor stops
  responding to keystrokes, global shortcuts like Ctrl+N stops working
  etc, until you alt-tab to another application and back to intellij.

  The bug has been reported here to Intellij:
  https://youtrack.jetbrains.com/issue/IDEA-222415

  However, the bug was really present in
  https://gitlab.gnome.org/GNOME/mutter/issues/819

  The fix is already in git:
  https://www.phoronix.com/scan.php?page=news_item&px=Java-Focus-GNOME-
  Wayland

  Could you please upgrade Mutter to include fix for this issue? Thank
  you :) Have a nice day ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  8 07:52:13 2019
  InstallationDate: Installed on 2016-09-05 (1127 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-26 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1847184/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support

2019-10-09 Thread Giraffe

** Description changed:

  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85
  
  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.
  
  It would be great if the aforementioned commits where backported to Eoan
  before release, so that Eoan based systems will associate with WiFi-
  networks using WPA3.
+ 
+ ==
+ Update 09-10-2019:
+ So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
+ 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08
+ 
+ Without this latest commit connecting to WPA3-personal networks will
+ still fail because of a lack of 802.11w support in the network-manager
+ settings.

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  Volume up/down repeat keys don't work on Xorg

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Eoan:
  In Progress

Bug description:
  GNOME Shell & mutter on 3.33.91
  When pressing volume up or down on Xorg and keeping it pressed, only the 
first key event is sent, so the volume only goes up or down once, and doesn't 
scale up/down as long as you keep the button pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 29 13:45:27 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-24 (461 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)

** Changed in: gnome-control-center
   Status: Unknown => 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/1799675

Title:
  /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.30.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1799675/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

I plugged in these https://www.trust.com/it/product/20943-polo-
compact-2-0-speaker-set usb powered speaker (they work good, tried them
via otg cable on smartphone) still get no sound

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

I plugged in these https://www.trust.com/it/product/20943-polo-
compact-2-0-speaker-set usb powered speaker (they work good, tried them
via otg cable on smartphone) still get no sound

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)

2019-10-09 Thread Laurent Bonnaud

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #248
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/248

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/248
   Importance: Unknown
   Status: Unknown

** Bug watch added: Red Hat Bugzilla #1665639
   https://bugzilla.redhat.com/show_bug.cgi?id=1665639

** Also affects: gnome-control-center (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1665639
   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/1799675

Title:
  /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.30.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1799675/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

The issue is still there in 3.34, reported upstream now

https://gitlab.gnome.org/GNOME/gnome-bluetooth/issues/52

** Bug watch added: gitlab.gnome.org/GNOME/gnome-bluetooth/issues #52
   https://gitlab.gnome.org/GNOME/gnome-bluetooth/issues/52

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-bluetooth/issues/52
   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/1845163

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in gnome-control-center:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1845163/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846882] Re: Thunderbird crashes when clicking on menu item

2019-10-09 Thread AO

Thanks Olivier for looking into this issue.

apt policy enigmail
enigmail:
  Installed : (none)
  Candidate : 2:2.1.2-0ubuntu1
 Version table :
 2:2.1.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

I have Enigmail 2.1.2 installed, from Thunderbird add-on store.

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

Title:
  Thunderbird crashes when clicking on menu item

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Thunderbird 1:68.1.1+build1-0ubuntu1 On Ubuntu 19.10 fully updated.

  When writing an email, upon clicking on Enigmail in the menu bar,
  Thunderbird crashes.

  I contacted Enigmail’s lead dev about the issue who wrote:

  "…but even if the crash is initiated by Enigmail, the cause is
  certainly in Thunderbird. Enigmail is purely JavaScript and XUL - and by
  definition of the programming languages, these two cannot crash
  Thunderbird."

  I tried Thunderbird 68.1.1 from Mozilla’s site, and can’t
  reproduce the problem with it.

  Here is Thunderbird’s log upon crashing:

  AdapterDeviceID: 0x1912
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 19.3.0.0
  AdapterVendorID: 0x8086
  Add-ons:
  
%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D:68.1.1,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.1.2,antidote7_linux_thunderbird_102%40druide.com:10.1.30,en-CA%40dictionaries.addons.mozilla.org:3.1.0,fr-dicollecte%40dictionaries.addons.mozilla.org:6.3.1webext,wetransfer%40extensions.thunderbird.net:2.0.0,thunderbird-compact-dark%40mozilla.org:1.0,google%40search.mozilla.org:1.0,bing%40search.mozilla.org:1.0,amazon%40search.mozilla.org:1.1,ddg%40search.mozilla.org:1.0,qwant%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,langpack-fr%40thunderbird.mozilla.org:68.0,wetransfer%40extensions.thunderbird.net:2.0.0
  BuildID: 20191001201558
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 0
  CrashTime: 1570225903
  EventLoopNestingLevel: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1570020285
  IsWayland: 0
  Notes: Ubuntu Eoan Ermine (development
  branch)FP(D00-L1000-W-T000) WR? WR- OMTP? OMTP+3
  ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
  ProductName: Thunderbird
  ReleaseChannel: release
  SafeMode: 0
  SecondsSinceLastCrash: 383
  StartupCrash: 0
  StartupTime: 1570225565
  ThreadIdNameMapping: 20357:"Gecko_IOThread",20358:"JS
  Watchdog",20359:"JS Helper",20360:"JS Helper",20361:"JS
  Helper",20362:"JS Helper",20363:"Link Monitor",20364:"Socket
  Thread",20372:"Timer",20373:"Cache2
  I/O",20375:"DataStorage",20376:"Cookie",20379:"GMPThread",20380:"Worker
  Launcher",20381:"SoftwareVsyncThread",20382:"Compositor",20383:"ImgDecoder
  #1",20384:"ImageIO",20390:"ImageBridgeChild",20391:"IPDL
  Background",20392:"DOM Worker",20394:"HTML5
  
Parser",20397:"StyleThread#1",20396:"StyleThread#0",20398:"StyleThread#2",20401:"mozStorage
  #1",20407:"localStorage DB",20408:"ImgDecoder #2",20410:"Cache
  I/O",20411:"DNS Resolver #1",20412:"URL Classifier",20413:"Classifier
  Update",20415:"QuotaManager IO",20426:"DNS Resolver #2",20427:"DNS
  Resolver #3",20429:"ImgDecoder #3",20439:"mozStorage #3",20452:"DOM
  Worker",20467:"mozStorage #5",20468:"mozStorage #6",20469:"mozStorage
  #7",20479:"DOM Worker",20500:"mozStorage #8",27048:"StreamTrans #18",
  Throttleable: 1
  UptimeTS: 337.7284093
  Vendor:
  Version: 68.1.1
  useragent_locale: fr

  This is what I get when running Thunderbird from the console and after
  the crash occurred:

  1570277554871 addons.xpi  WARNCan't get modified time of 
/usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net
  1570277554912 addons.xpi-utilsWARNupdateMetadata: Add-on 
wetrans...@extensions.thunderbird.net is invalid: [Exception... "Component 
returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) 
[nsIFile.isFile]"  nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)" 
 location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: get :: 
line 235"  data: no] Stack trace: 
get()@resource://gre/modules/addons/XPIInstall.jsm:235
  syncLoadManifest()@resource://gre/modules/addons/XPIInstall.jsm:745
  updateMetadata()@resource://gre/modules/addons/XPIDatabase.jsm:2821
  updateExistingAddon()@resource://gre/modules/addons/XPIDatabase.jsm:3036
  processFileChanges()@resource://gre/modules/addons/XPIDatabase.jsm:3125
  checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:2946
  startup()@resource://gre/modules/addons/XPIProvider.jsm:2406
  callProvider()@resource://gre/modules/AddonManager.jsm:213
  _startProvider()@resource://gre/modules/AddonManager.jsm:649
  startup()@resource://gre/modules/AddonManager.jsm:873
  startup()@resource://gre/modules/AddonManager.jsm:3469
  observe

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

valgrind error log

==4950== Invalid read of size 4
==4950==at 0x600FE3B: bluetooth_pairing_dialog_get_mode 
(bluetooth-pairing-dialog.c:171)
==4950==by 0x60164D0: display_callback (bluetooth-settings-widget.c:526)
==4950==by 0x6005BCE: bluetooth_agent_display_passkey 
(bluetooth-agent.c:193)
==4950==by 0x6005BCE: handle_method_call (bluetooth-agent.c:495)
==4950==by 0x6005BCE: handle_method_call (bluetooth-agent.c:457)
==4950==by 0x497A053: call_in_idle_cb (gdbusconnection.c:4878)
==4950==by 0x4AF872D: ??? (in 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.0)
==4950==  Address 0x14641e70 is 80 bytes inside an unallocated block of size 
1,024 in arena "client"
==4950== 
==4950== Invalid read of size 8
==4950==at 0x4F61175: gtk_widget_destroy (gtkwidget.c:4770)
==4950==by 0x60137F6: setup_pairing_dialog (bluetooth-settings-widget.c:236)
==4950==by 0x60164ED: display_callback (bluetooth-settings-widget.c:527)
==4950==by 0x6005BCE: bluetooth_agent_display_passkey 
(bluetooth-agent.c:193)
==4950==by 0x6005BCE: handle_method_call (bluetooth-agent.c:495)
==4950==by 0x6005BCE: handle_method_call (bluetooth-agent.c:457)
==4950==by 0x497A053: call_in_idle_cb (gdbusconnection.c:4878)
==4950==by 0x4AF872D: ??? (in 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.0)

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

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845163/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

Backtrace after closing with esc on the normal keyboard and trying to
open it again

Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
__tzstring_len (len=4, s=0x57c9cdd9 "CEST") at tzset.c:90
90  tzset.c: Aucun fichier ou dossier de ce type.
(gdb) bt
#0  0x7632ed0b in __tzstring_len (len=4, s=0x57c9cdd9 "CEST")
at tzset.c:90
#1  0x7632ed0b in __tzstring (s=0x57c9cdd9 "CEST") at tzset.c:121
#2  0x76330cd0 in __tzfile_compute
(timer=timer@entry=1570635708, use_localtime=use_localtime@entry=1, 
leap_correct=leap_correct@entry=0x7fffd5f0, 
leap_hit=leap_hit@entry=0x7fffd5ec, tp=tp@entry=0x7644a240 <_tmbuf>) at 
tzfile.c:707
#3  0x7632faa1 in __tz_convert
(timer=1570635708, use_localtime=use_localtime@entry=1, 
tp=tp@entry=0x7644a240 <_tmbuf>) at tzset.c:580
#4  0x7632d4f8 in __GI_localtime (t=t@entry=0x7fffd630)
at localtime.c:54
#5  0x77c9d19e in g_log_writer_format_fields
(log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
fields=fields@entry=0x7fffd810, n_fields=n_fields@entry=4, use_color=1)
at ../../../glib/gmessages.c:2276
#6  0x77c9e0c6 in g_log_writer_standard_streams
(log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
fields=fields@entry=0x7fffd810, n_fields=n_fields@entry=4, 
user_data=user_data@entry=0x0)
at ../../../glib/gmessages.c:2557
#7  0x77c9e1c6 in g_log_writer_default
(log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
fields=fields@entry=0x7fffd810, n_fields=n_fields@entry=4, 
user_data=user_data@entry=0x0)
--Type  for more, q to quit, c to continue without paging--
at ../../../glib/gmessages.c:2670
#8  0x77c9c537 in g_log_structured_array
(n_fields=4, fields=0x7fffd810, log_level=G_LOG_LEVEL_CRITICAL)
at ../../../glib/gmessages.c:1925
#9  0x77c9c537 in g_log_structured_array
(log_level=G_LOG_LEVEL_CRITICAL, fields=0x7fffd810, n_fields=4)
at ../../../glib/gmessages.c:1898
#10 0x77c9c979 in g_log_default_handler
(log_domain=log_domain@entry=0x77924047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
message=message@entry=0x57a4ac70 "gtk_entry_set_text: assertion 
'GTK_IS_ENTRY (entry)' failed", unused_data=unused_data@entry=0x0)
at ../../../glib/gmessages.c:3123
#11 0x77c9cbac in g_logv
(log_domain=0x77924047 "Gtk", log_level=G_LOG_LEVEL_CRITICAL, 
format=, args=args@entry=0x7fffd950) at 
../../../glib/gmessages.c:1350
#12 0x77c9cd93 in g_log
(log_domain=log_domain@entry=0x77924047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
format=format@entry=0x77ced713 "%s: assertion '%s' failed") at 
../../../glib/gmessages.c:1415
#13 0x77c9d58d in g_return_if_fail_warning
(log_domain=log_domain@entry=0x77924047 "Gtk", 
pretty_function=pretty_function@entry=0x77953de0 <__func__.71767> 
"gtk_entry_set_text", expression=expression@entry=0x7795240a "GTK_IS_ENTRY 
(entry)")
--Type  for more, q to quit, c to continue without paging--
at ../../../glib/gmessages.c:2771
#14 0x776f68aa in gtk_entry_set_text
(entry=, text=text@entry=0x578d7cf0 "122649")
at ../../../../gtk/gtkentry.c:7706
#15 0x7680a917 in bluetooth_pairing_dialog_set_mode
(self=, 
mode=mode@entry=BLUETOOTH_PAIRING_MODE_PIN_DISPLAY_KEYBOARD, 
pin=pin@entry=0x578d7cf0 "122649", 
device_name=device_name@entry=0x57804cb0 "Logitech Keyboard K480") at 
../lib/bluetooth-pairing-dialog.c:76
#16 0x7681153d in display_callback
(invocation=, device=, pin=, 
entered=0, user_data=0x577b0d80) at ../lib/bluetooth-settings-widget.c:531
#17 0x76800bcf in bluetooth_agent_display_passkey
(invocation=0x7fffdc0a5490 [GDBusMethodInvocation], entered=0, 
passkey=122649, path=0x578c52d0 "/org/bluez/hci0/dev_00_1F_20_E3_89_EE", 
agent=0x579d1420 [BluetoothAgent]) at ../lib/bluetooth-agent.c:193
#18 0x76800bcf in handle_method_call

(connection=, sender=0x0, object_path=0x1df19 , interface_name=0x57bb61e0 , user_data=0x579d1420, invocation=0x7fffdc0a5490 
[GDBusMethodInvocation], parameters=0x0001df19, method_name=0x578c52d0 
"/org/bluez/hci0/dev_00_1F_20_E3_89_EE") at ../lib/bluetooth-agent.c:495
#19 0x76800bcf in handle_method_call
(connection=, sender=sender@entry=0x7fffdc063e60 ":1.9", 
obje--Type  for more, q to quit, c to continue without paging--
ct_path=object_path@entry=0x7fffdc099d60 "/org/gnome/bluetooth/settings", 
interface_name=interface_name@entry=0x7fffdc088ec0 "org.bluez.Agent1", 
method_name=method_name@entry=0x7fffdc02ffb0 "DisplayPasskey", 
parameters=parameters@entry=0x7fffdc099760, invocation=0x7fffdc0a5490 
[GDBusMethodInvocation], user_data=0x579d1420) at 
../lib/bluetooth-agent.c:457
#20 0x77ed4054 in call_in_idle_cb (user_data=)
at ../../../gio/gdbusconnection.c:4878
#21 0x77c9572e in g_main_d

[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

2019-10-09 Thread Hui Wang

Did you plug the headphone to the headphone jack or lineout jack? from
the log of #5, they are not plugged or the plugging is not detected (all
not available).

Porte:
analog-output-lineout: Line-Out (priority: 9900, not available)
analog-output-headphones: Cuffie analogiche (priority: 9000, not 
available)
Porta attiva: analog-output-lineout

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

I could not post gnome-sound-settings because my environment is xfce4
not gnome

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

hh@hh-desktop:~$ pactl list
Modulo #0
Nome: module-device-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore the volume/mute 
state of devices"
module.version = "11.1"

Modulo #1
Nome: module-stream-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore the 
volume/mute/device state of streams"
module.version = "11.1"

Modulo #2
Nome: module-card-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore profile of cards"
module.version = "11.1"

Modulo #3
Nome: module-augment-properties
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "11.1"

Modulo #4
Nome: module-switch-on-port-available
Argomento: 
Contatore utilizzi: N/D
Proprietà:


Modulo #5
Nome: module-switch-on-connect
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Michael Terry"
module.description = "When a sink/source is added, switch to it 
or conditionally switch to it"
module.version = "11.1"

Modulo #6
Nome: module-udev-detect
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Detect available audio hardware and load 
matching drivers"
module.version = "11.1"

Modulo #7
Nome: module-alsa-card
Argomento: device_id="1" name="pci-_01_00.1" 
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1"
Contatore utilizzi: 1
Proprietà:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "11.1"

Modulo #8
Nome: module-alsa-card
Argomento: device_id="0" name="pci-_00_14.2" 
card_name="alsa_card.pci-_00_14.2" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1"
Contatore utilizzi: 1
Proprietà:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "11.1"

Modulo #9
Nome: module-bluetooth-policy
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Frédéric Dalleau, Pali Rohár"
module.description = "Policy module to make using bluetooth 
devices out-of-the-box easier"
module.version = "11.1"

Modulo #10
Nome: module-bluetooth-discover
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available Bluetooth daemon and 
load the corresponding discovery module"
module.version = "11.1"

Modulo #11
Nome: module-bluez5-discover
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available BlueZ 5 Bluetooth audio 
devices and load BlueZ 5 Bluetooth audio drivers"
module.version = "11.1"

Modulo #12
Nome: module-native-protocol-unix
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "11.1"

Modulo #13
Nome: module-gconf
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "GConf Adapter"
module.version = "11.1"

Modulo #14
Nome: module-default-device-restore
Argomento: 
Contatore utilizzi: N/D
Proprietà:
module.author = "Lennart Poettering"
module.description = "Automatically restore the default sink 
and source"
module.version = "11.1"

Modulo #15
Nome: module-rescue-streams
Argomento: 
Contatore utilizzi: N/D
Proprietà:
modu

[Desktop-packages] [Bug 1847491] StacktraceSource.txt

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


** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1847491/+attachment/5295985/+files/StacktraceSource.txt

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847491] ThreadStacktrace.txt

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


** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847491/+attachment/5295986/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1847491/+attachment/5295959/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847491] Re: gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)

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

** This bug has been marked a duplicate of bug 1799675
   
/usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility:
 assertion failed: (valid)

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847491] Stacktrace.txt

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


** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847491/+attachment/5295984/+files/Stacktrace.txt

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847491] gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)

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

StacktraceTop:
 g_assertion_message.cold () from 
/tmp/apport_sandbox_s_gqakhd/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from 
/tmp/apport_sandbox_s_gqakhd/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 cc_shell_model_set_panel_visibility (self=0x5612dd023510, 
id=id@entry=0x5612db262b85 "wifi", 
visibility=visibility@entry=CC_PANEL_VISIBLE) at ../shell/cc-shell-model.c:458
 update_panel_visibility (client=) at 
../panels/network/cc-wifi-panel.c:114
 cc_wifi_panel_static_init_func () at ../panels/network/cc-wifi-panel.c:143

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847491] Re: gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)

2019-10-09 Thread Laurent Bonnaud

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

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+attachment/5295962/+files/JournalErrors.txt

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1847491] [NEW] gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)

2019-10-09 Thread Laurent Bonnaud

Public bug reported:

When I try to use gnome-control-center under Plasma, it crashes.

Steps to reproduce:
1. start a Plasma session
2. start gnome-control-center

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu1
Uname: Linux 5.3.5-050305-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
CurrentDesktop: KDE
Date: Wed Oct  9 10:46:52 2019
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1570461969
ProcCmdline: gnome-control-center
ProcCwd: /home/bonnaudl
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
 g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
 cc_shell_model_set_panel_visibility ()
 ()
 cc_wifi_panel_static_init_func ()
Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
separator:

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


** Tags: amd64 apport-crash eoan

** Information type changed from Private to Public

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

Title:
  gnome-control-center assert failure: ERROR:../shell/cc-shell-
  model.c:458:cc_shell_model_set_panel_visibility: assertion failed:
  (valid)

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

Bug description:
  When I try to use gnome-control-center under Plasma, it crashes.

  Steps to reproduce:
  1. start a Plasma session
  2. start gnome-control-center

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  CurrentDesktop: KDE
  Date: Wed Oct  9 10:46:52 2019
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1570461969
  ProcCmdline: gnome-control-center
  ProcCwd: /home/bonnaudl
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message (domain=, file=, 
line=, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", message=) at 
../../../glib/gtestutils.c:2912
   g_assertion_message_expr (domain=0x0, file=0x5612db26aeff 
"../shell/cc-shell-model.c", line=458, func=0x5612db26af40 
"cc_shell_model_set_panel_visibility", expr=) at 
../../../glib/gtestutils.c:2938
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center assert failure: 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1832811] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.