date:20191010

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Firefox text windows pick the wrong language by default

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Fully up-to-date Wily, although this has been going on for a long
  time.  Use Firefox to e.g. view Facebook.  Start writing some new
  status and notice that *all* your English words are flagged as
  misspelled.  Right click to bring up the Languages menu and notice
  that Arabic (Qatar) is the default language, not English.   Locale is
  clearly en_US.UTF-8.  Use the Language menu to choose English (United
  States) and the autospell works correctly.

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

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

[Desktop-packages] [Bug 1847708] Re: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Internal mic is useless in Ubuntu 19.10

** Tags added: ce-qa-concern

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

Title:
  [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording]
  Internal mic is useless in Ubuntu 19.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Navigate to 'System Settings' -> 'Sound'
  4. Verify the input and output working or not

  [Expected result]
  Both input and output work normally, user could hear the sound from internal 
speaker, also could record voice from internal mic

  [Actual result]
  Internal speaker works normally, internal mic is useless and got gray always

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:37:09 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1731454] Re: Video doesn’t play in the right screen on entering full-screen mode while using two monitors

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Video doesn’t play in the right screen on entering full-screen mode
  while using two monitors

Status in firefox package in Ubuntu:
  Expired

Bug description:
  O quando estou com 2 monitores o e ativo o modo Tela Cheia do video o
  video sai do monitor de origem e vai para o outro monitor secundario.

  Google translated this as:

  When I have 2 monitors and activates the Full Screen mode of the video
  the video leaves the source monitor and goes to the other secondary
  monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krashtime   1715 F pulseaudio
  BuildID: 20171003101344
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Nov 10 08:15:13 2017
  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 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.15.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.15.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.15.41  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20171025.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd03/17/2017:svnAcer:pnAspireVX5-591G:pvrV1.05:rvnKBL:rnWish_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.name: Aspire VX5-591G
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1732374] Re: does not store the language change settings

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  does not store the language change settings

Status in firefox package in Ubuntu:
  Expired

Bug description:
  does not restore the language change settings

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simone 1575 F pulseaudio
  BuildID: 20171003101020
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Wed Nov 15 09:29:39 2017
  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 2015-03-29 (961 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.101  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003101020 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20170808.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Spring Peak
  dmi.board.vendor: Olivetti
  dmi.board.version: OLIBOOK S1530
  dmi.chassis.type: 10
  dmi.chassis.vendor: Olivetti
  dmi.chassis.version: OLIBOOK S1530
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0.4:bd07/11/2011:svnOlivetti:pnSpringPeak:pvrOLIBOOKS1530:rvnOlivetti:rnSpringPeak:rvrOLIBOOKS1530:cvnOlivetti:ct10:cvrOLIBOOKS1530:
  dmi.product.name: Spring Peak
  dmi.product.version: OLIBOOK S1530
  dmi.sys.vendor: Olivetti

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

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

[Desktop-packages] [Bug 1847709] Re: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-mute key and its LED can not work on Ubuntu 19.10

** Tags added: ce-qa-concern

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

Title:
  [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-
  mute key and its LED can not work on Ubuntu 19.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Press mic-mute key several times
  4. Verify the result
  5. Open a terminal and $ record test.wav
  6. Leave the terminal here and make voice, meanwhile, press mic-mute key 
several times

  [Expected result]
  Mic-mute key function and its LED work normally.

  [Actual result]
  Mic-mute key and its LED can not work on Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:54:01 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1847710] [NEW] [ThinkPad X1 Yoga 4th Gen][20QGZ4MTUS, Realtek ALC285, Speaker, Internal] The Volume remains the same value.

Public bug reported:

[Steps to reproduce]
1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
2. Login system
3. Navigate to 'System Settings' -> 'Sound'
4. Adjust the 'System Volume' bar and verify the sound result
5. Press 'F2 and F3' to adjust system volume

[Expected result]
System volume should be heard with several sound level.

[Actual result]
No matter what adjusted, the volume remains the same value.

[Notes]
Navigate to 'System Settings' -> 'Sound' -> 'Over-Amplification', turn it 'On'
Then adjust the sound, we could hear the different volume value beyond 100%, 
but it could remains the same value from 0 ~ 100%

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1747 F pulseaudio
 /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 12:01:52 2019
InstallationDate: Installed on 2019-10-09 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 10月 11 10:57:40 u-ThinkPad-X1-Yoga-4th dbus-daemon[745]: [system] Activating 
via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.36' (uid=124 pid=952 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
 10月 11 10:57:57 u-ThinkPad-X1-Yoga-4th systemd[938]: pulseaudio.service: 
Succeeded.
 10月 11 10:57:59 u-ThinkPad-X1-Yoga-4th dbus-daemon[745]: [system] Rejected 
send message, 2 matched rules; type="method_call", sender=":1.785" (uid=124 
pid=2441 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error 
name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=734 
comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
 10月 11 10:58:07 u-ThinkPad-X1-Yoga-4th systemd[938]: pulseaudio.service: 
Succeeded.
 10月 11 10:58:07 u-ThinkPad-X1-Yoga-4th systemd[938]: pulseaudio.socket: 
Succeeded.
Symptom_Type: Volume slider, or mixer problems
Title: [20QGZ4MTUS, Realtek ALC285, Speaker, Internal] volume slider problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET39W (1.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QGZ4MTUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 4th
dmi.product.name: 20QGZ4MTUS
dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
dmi.product.version: ThinkPad X1 Yoga 4th
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ce-qa-concern eoan

** Tags added: ce-qa-concern

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

Title:
  [ThinkPad X1 Yoga 4th Gen][20QGZ4MTUS, Realtek ALC285, Speaker,
  Internal] The Volume remains the same value.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Navigate to 'System Settings' -> 'Sound'
  4. Adjust the 'System Volume' bar and verify the sound result
  5. Press 'F2 and F3' to adjust system volume

  [Expected result]
  System volume should be heard with several sound level.

  [Actual result]
  No matter what adjusted, the volume remains the same value.

  [Notes]
  Navigate to 'System Settings' -> 'Sound' -> 'Over-Amplification', turn it 'On'
  Then adjust the sound, we could hear the different volume value beyond 100%, 
but it could remains the same value from 0 ~ 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 12:01:52 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture:

[Desktop-packages] [Bug 1847709] [NEW] [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-mute key and its LED can not work on Ubuntu 19.10

Public bug reported:

[Steps to reproduce]
1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
2. Login system
3. Press mic-mute key several times
4. Verify the result
5. Open a terminal and $ record test.wav
6. Leave the terminal here and make voice, meanwhile, press mic-mute key 
several times

[Expected result]
Mic-mute key function and its LED work normally.

[Actual result]
Mic-mute key and its LED can not work on Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1747 F pulseaudio
 /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 11:54:01 2019
InstallationDate: Installed on 2019-10-09 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Type: None of the above
Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET39W (1.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QGZ4MTUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 4th
dmi.product.name: 20QGZ4MTUS
dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
dmi.product.version: ThinkPad X1 Yoga 4th
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-
  mute key and its LED can not work on Ubuntu 19.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Press mic-mute key several times
  4. Verify the result
  5. Open a terminal and $ record test.wav
  6. Leave the terminal here and make voice, meanwhile, press mic-mute key 
several times

  [Expected result]
  Mic-mute key function and its LED work normally.

  [Actual result]
  Mic-mute key and its LED can not work on Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:54:01 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1847708] [NEW] [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Internal mic is useless in Ubuntu 19.10

Public bug reported:

[Steps to reproduce]
1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
2. Login system
3. Navigate to 'System Settings' -> 'Sound'
4. Verify the input and output working or not

[Expected result]
Both input and output work normally, user could hear the sound from internal 
speaker, also could record voice from internal mic

[Actual result]
Internal speaker works normally, internal mic is useless and got gray always

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1747 F pulseaudio
 /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 11:37:09 2019
InstallationDate: Installed on 2019-10-09 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Type: None of the above
Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET39W (1.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QGZ4MTUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 4th
dmi.product.name: 20QGZ4MTUS
dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
dmi.product.version: ThinkPad X1 Yoga 4th
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording]
  Internal mic is useless in Ubuntu 19.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Navigate to 'System Settings' -> 'Sound'
  4. Verify the input and output working or not

  [Expected result]
  Both input and output work normally, user could hear the sound from internal 
speaker, also could record voice from internal mic

  [Actual result]
  Internal speaker works normally, internal mic is useless and got gray always

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:37:09 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3

2019-10-10 Thread Nobuto Murata

** Attachment added: "Screenshot from 2019-10-11 12-35-40.png"
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1847706/+attachment/5296436/+files/Screenshot%20from%202019-10-11%2012-35-40.png

** Also affects: deja-dup
   Importance: Undecided
   Status: New

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

Title:
  Deja Dup still tells python-gi (python 2) is required while duplicity
  is now python3

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  Please see the screenshot attached. When running a backup operation
  against a remote server with SSH, Deja Dup stops by saying "python-gi"
  package is required.

  However, duplicity is updated with Python3 now, so it doesn't make
  sense to install Python 2 based package. The prerequisite check needs
  to be updated probably with python3-gi instead.

  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: ubuntu:GNOME
  Date: Fri Oct 11 12:34:15 2019
  InstallationDate: Installed on 2019-08-28 (43 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847706] [NEW] Deja Dup still tells python-gi (python 2) is required while duplicity is now python3

2019-10-10 Thread Nobuto Murata

Public bug reported:

Please see the screenshot attached. When running a backup operation
against a remote server with SSH, Deja Dup stops by saying "python-gi"
package is required.

However, duplicity is updated with Python3 now, so it doesn't make sense
to install Python 2 based package. The prerequisite check needs to be
updated probably with python3-gi instead.

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: ubuntu:GNOME
Date: Fri Oct 11 12:34:15 2019
InstallationDate: Installed on 2019-08-28 (43 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup
 Importance: Undecided
 Status: New

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Summary changed:

- Deja Dup tells python-gi (python 2) is still required while duplicity is now 
python3
+ Deja Dup still tells python-gi (python 2) is required while duplicity is now 
python3

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

Title:
  Deja Dup still tells python-gi (python 2) is required while duplicity
  is now python3

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  Please see the screenshot attached. When running a backup operation
  against a remote server with SSH, Deja Dup stops by saying "python-gi"
  package is required.

  However, duplicity is updated with Python3 now, so it doesn't make
  sense to install Python 2 based package. The prerequisite check needs
  to be updated probably with python3-gi instead.

  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: ubuntu:GNOME
  Date: Fri Oct 11 12:34:15 2019
  InstallationDate: Installed on 2019-08-28 (43 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2019-10-10 Thread Bug Watch Updater

** Changed in: mutter
   Status: New => 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/1847551

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

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

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 1847675] Re: Lenovo thinkpad T440s Trackpoint doesn't work properly

Sounds related to bug 1733083.


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

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

Title:
  Lenovo thinkpad T440s Trackpoint doesn't work properly

Status in libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  1. middle click scroll doesn't work at all. Holding down the the
  middle scroll button while pushing the trackpoint results in the
  cursor freezing for a couple seconds.

  2. Trackpoint motion is extremely slow.

  3. Right-click doesn't work.

  I hadn't observed these problems with ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Oct 11 00:34:54 2019
  DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-11-15 (329 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet 
splash vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: Upgraded to disco on 2019-04-27 (166 days ago)
  dmi.bios.date: 03/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET98WW (2.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQCTO1WW
  dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/libinput/+bug/1847675/+subscriptions

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

[Desktop-packages] [Bug 1847650] Re: When dock is on the right hand side it covers the 'page dots' on the 'all applications' icon view

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  When dock is on the right hand side it covers the 'page dots' on the
  'all applications' icon view

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Steps to duplicate:
  1. Set Ubuntu Dock to be on the right hand side of the screen.
  2. Click on the 'Show Applications' button which will be at the bottom-right 
of the screen.
  3. When all of the application icons appear, you will notice that the 'dots' 
which can be clicked for switch from one page of icons to another are on the 
right of the screen underneath the Ubuntu dock. As such they cannot be clicked 
on.

  Expected result:
  Can the dots either move to the left of the screen (where there is no dock) 
or at least moved to a place where the dock does not obscure them?

  Whilst this may not appear to be a major issue, I am running this on a
  laptop using only a trackpad, and switching from one page of icons to
  another is a but hit and miss as often a gentle swipe on my track pad
  moves me two pages in either direction.

  Thanks
  Nick

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 19:16:05 2019
  InstallationDate: Installed on 2019-09-23 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

Thanks for your input, @Peng Wu!

Hmm.. Looks like we have an unenviable choice to make.

@Sebastien: Can you please read the comments above starting with #20 and
let us know your view. Would an SRU of libpinyin be appropriate given
the circumstances?

-- 
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 1847631] Re: Bug with start of the system Ubuntu 18.04 LTS

Thanks for the bug report. We request that each bug report only describe
one problem, not two as in this case. So let's make this bug about the
wifi issue. If you would like to discuss the other issue then please
open a new bug for it.

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

** Summary changed:

- Bug with start of the system Ubuntu 18.04 LTS
+ RTL8821CE 802.11ac intermittent wifi connection

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

Title:
  RTL8821CE 802.11ac intermittent wifi connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am russian, so my English level is too low, I'll do my best.
  Technical characteristics is: Ryzen 3 2200U, Radeon Vega 3, RAM 8 Gb, 256 Gb 
SSD, IPS display 1920*1080 (if you need). Features is right, if you need a 
model of the laptop: Lenovo Ideapad 330-15ARR.
  Problem: 
  When I launch my laptop, in 3 of 4 cases it start with bugs. The most often 
problem is lack of Wi-fi connection when this module work. It is showing that's 
happening tries to connect to saved network, but nothing else. It resolves to 
open laptop's cover again. Second problem is black screen or hovering screen 
when system turns on. Well, in this case I reboot all computer again and again 
until it won't be normal. Usually, it takes about 3-4 times, no more.
   
  These problems on Russian: Самая частая проблема (в 3 из 4 открытий крышки 
ноутбука) - когда при включении ноутбука из сна, не подключается к сохраненной 
точке доступа wi-fi. Крутиться колесико, что идет попытка подключения, но 
ничего больше не происходит, и исправляется это закрытием и открытием крышки 
ноутбука снова. Я перепробовал все методы из интернета, но проблема так и не 
исчезла. Следующая проблема встречается не так часто как предыдущая, но тоже 
довольно нередкая. При полном включении ноутбука (не как в прошлом случае), 
система полностью зависает либо до предложения ввести пароль с черным экраном, 
либо после ввода пароля, но тоже с черным экраном. Третья и последняя проблема 
- зависание системы с нормальным ходом звука или также с его заглючиванием во 
время работы. Просто работаешь и она вдруг зависает, ничего не помогает кроме 
перезапуска всей системы. Кроме данных багов ничего не раздражает, очень 
нравится система. Переустанавливал уже более 5 раз, всегда наблюдаю такие 
проблемы. Установочный образ не поврежден, так как у друзей все работает без 
каких-либо багов и зависаний. Очень нравится система, жду более стабильную 
19.04 LTS и сразу же обновлюсь на нее.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 20:30:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, v5.2.5_1.26055.20180108.1, 4.15.0-64-generic, x86_64: installed
   rtl8821ce, v5.2.5_1.26055.20180108.1, 4.15.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:38ef]
  InstallationDate: Installed on 2019-07-22 (80 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81D2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=66f72524-149c-45c0-8f82-857606a10e7d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN24WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN24WW:bd06/15/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev

[Desktop-packages] [Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)

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

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

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

Title:
  Panel menu icons are briefly way too big (when opened the first time)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)

** Tags removed: artful
** Tags added: eoan

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

Title:
  Panel menu icons are briefly way too big (when opened the first time)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

@fermulator: Thanks for confirming and, of course, for pointing at the
applicable upstream fix.

Unfortunately it seems like the fix in Ubuntu 18.04 is not sufficient
for some LiDE 100 devices, so the PPA will keep being useful to some
users.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Fix Released
Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Released
Status in sane-backends source package in Disco:
  Fix Released
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1797734] Re: slow calculator startup

** Tags added: performance

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1842662] Re: Gnome Dash (vanilla - no extensions) first icon always missing unless you open the dash soon after login

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

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-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: fixed-in-3.34.2 fixed-upstream

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

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

-- 
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:
  Triaged

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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2019-10-10 Thread fermulator

Certainly, the PPA from `rolfbensch` has the fix (start at
https://gitlab.com/sane-project/backends/issues/7#note_125319290).

https://gitlab.com/sane-project/backends/-/tags/1.0.28, was released on
Jul 31 2019.

At least currently:
https://mirrors.edge.kernel.org/ubuntu/pool/main/s/sane-backends/
libsane-common_1.0.27-1~experimental3ubuntu2.2_..> 30-Aug-2019 15:48267K  
 THIS ONE
libsane-common_1.0.27-3.2ubuntu1.1_all.deb 30-Aug-2019 15:48265K
libsane-common_1.0.27-3.2ubuntu1_all.deb   05-Apr-2019 23:06265K
libsane-common_1.0.27-3.2ubuntu3_all.deb   19-Sep-2019 12:48265K

My system was preset for that PPA (due to above).

```
$ dpkg --list | grep -i libsane-common
ii  libsane-common   
1.0.28+git20191006-bionic0  all  API library 
for scanners -- documentation and support files


/etc/apt/sources.list.d$ grep -rins sane *
rolfbensch-ubuntu-sane-git-bionic.list:1:deb 
http://ppa.launchpad.net/rolfbensch/sane-git/ubuntu bionic main
rolfbensch-ubuntu-sane-git-bionic.list:2:# deb-src 
http://ppa.launchpad.net/rolfbensch/sane-git/ubuntu bionic main
```

Remove that PPA and update/refresh (remove libsane*) then re-install
(there is a lot of awkward pkg removals when I tried to remove libsane*, be 
sure to re-install stuff that you didn't want to remove)

```
$  dpkg --list | grep -i libsane-common
ii  libsane-common   
1.0.27-1~experimental3ubuntu2.2 all  API library 
for scanners -- documentation and support files

$ dpkg --list | grep -i sane-utils
ii  sane-utils   
1.0.27-1~experimental3ubuntu2.2 amd64API library 
for scanners -- utilities
```

Retested, and == VERIFIED FIXED

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Fix Released
Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Released
Status in sane-backends source package in Disco:
  Fix Released
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

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

2019-10-10 Thread paz

** Attachment added: "journal.tar.bz2"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+attachment/5296408/+files/journal.tar.bz2

-- 
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 1844739] Re: Latest Firefox update freezing my system

2019-10-10 Thread paz

Here it is ...

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+attachment/5296407/+files/journal.txt

-- 
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 1844422] Re: WPA3-SAE support

2019-10-10 Thread Teunis Peters

re fix committed : does that mean both network-manager and gnome-shell
will be updated as per posted hashes?

-- 
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:
  Fix Committed

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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-10-10 Thread Davide Sangalli

** Information type changed from Public to Public Security

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.

[Desktop-packages] [Bug 1847603] Re: After upgrading Ubuntu 19.10 second screen not detected

What if you upgrade to the latest kernel 5.3.0-17?

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

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

Title:
  After upgrading Ubuntu 19.10 second screen not detected

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  After upgrading Ubuntu 19.10 second screen not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 10 14:56:33 2019
  LightdmConfig:
   [Seat:*]
   #autologin-guest=false
   #autologin-user=caiofior
   #autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-10-10 Thread Davide Sangalli

Same problem here.
Ubuntu 18.04.3 LTS
I tried kernels 4.15, 5.0 and 5.3 and the problem persists.
With default installation parameters CPU temperatures goes above 95° very 
easily. 

The only way I managed to keep the CPU temp down is:
a) setting
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=disable"
and then choosing "PowerSave" mode in cpufreq

b) Installed laptop-mode-tools
Edited file: /etc/laptop-mode/laptop-mode.conf
It changed the file /proc/sys/vm/laptop_mode to 2
After that no significant changes in temperature when moving from AC to Battery

Attached hardinfo_report.html run after the doing the procedures above
mentioned

** Attachment added: "Output of hardinfo command"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+attachment/5296370/+files/hardinfo_report.html

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1847618] Re: language selector ignores input methods other than xim and none in my current locale

Thanks for your report. However, I can't reproduce the issue you
describe.

If you run this command:

im-config -l

it should output the IM frameworks which are installed on your system
plus xim. The UI in Language Support should show the same options
together with a 'none' option. That's the behavior I see irrespective of
which locale I use.

Any chance you can provide additional info to shed light on the issue?

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

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

Title:
  language selector ignores  input methods other than xim and none in my
  current locale

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as
  ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's
  not listed in unity-control-center>Language Support>Keyboard Input
  Method System. If I launch unity-control-center from terminal which is
  using different locale "LANGUAGE=en_US.utf8 unity-control-center" then
  there is no problem, all of the installed input methods are in the
  list.

  I also tested "python3 
/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py"
  it also ignores input methods other than xim and none.
  If I export "LANGUAGE=en_US.utf8" it lists all the other input methods.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1847618/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

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

-- 
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:
  Fix Committed

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 1847675] [NEW] Lenovo thinkpad T440s Trackpoint doesn't work properly

2019-10-10 Thread Rip

Public bug reported:

1. middle click scroll doesn't work at all. Holding down the the middle
scroll button while pushing the trackpoint results in the cursor
freezing for a couple seconds.

2. Trackpoint motion is extremely slow.

3. Right-click doesn't work.

I hadn't observed these problems with ubuntu 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-input-libinput 0.28.2-2
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CurrentDesktop: KDE
Date: Fri Oct 11 00:34:54 2019
DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None
DistroCodename: disco
DistroVariant: ubuntu
InstallationDate: Installed on 2018-11-15 (329 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: LENOVO 20AQCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet 
splash vt.handoff=1
SourcePackage: xserver-xorg-input-libinput
UpgradeStatus: Upgraded to disco on 2019-04-27 (166 days ago)
dmi.bios.date: 03/20/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET98WW (2.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20AQCTO1WW
dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-input-libinput (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  Lenovo thinkpad T440s Trackpoint doesn't work properly

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  1. middle click scroll doesn't work at all. Holding down the the
  middle scroll button while pushing the trackpoint results in the
  cursor freezing for a couple seconds.

  2. Trackpoint motion is extremely slow.

  3. Right-click doesn't work.

  I hadn't observed these problems with ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Oct 11 00:34:54 2019
  DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-11-15 (329 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet 
splash vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: Upgraded to disco on 2019-04-27 (166 days ago)
  dmi.bios.date: 03/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET98WW (2.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQCTO1WW
  dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri

[Desktop-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

2019-10-10 Thread Joshua Powers

Ubuntu discontinued the use of /etc/network/interfaces a number of
releases ago and in 19.10 have removed ifupdown. Please see the
migrating to netplan document:

https://wiki.ubuntu.com/MigratingToNetplan

If you need to continue using /etc/network/interfaces then there are
ways to install ifupdown and disable netplan.

I am closing this as invalid.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  The file /etc/network/interfaces is missing after install guestOS with
  eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi.

  This issue cause a failure for VMware Guest OS Customization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

2019-10-10 Thread Hui Wang

Download  
linux-image-unsigned-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb
Download  
linux-modules-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb

sudo dpkg -i  
linux-modules-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb
sudo dpkg -i 
linux-image-unsigned-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb

reboot


To uninstall the kernel 5.4

sudo dpkg -p linux-image-unsigned-5.4.0-... linux-modules-5.4.0-
reboot

-- 
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 1842740] Re: Critical gtx1650 driver unsuable resulting low graphics mode

2019-10-10 Thread Yossi Biton

I suffers from similar problems.
Just installed this driver on Ubuntu 18.04 (ASUS Zenbook) and can't login into 
the graphical interface (only in text mode). Help will be appreciated !

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

Title:
  Critical gtx1650 driver unsuable resulting low graphics mode

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  Graphic driver of Nvidia's brand new model gtx 1650 ppa driver is unusable.
  Currently it is updated as nvidia 430.26 and it is crashing with system files.
  Whenever I install my graphic driver, I cannot boot the computer up it says 
low graphics mode.

  Please refer to it in the link below

  https://devtalk.nvidia.com/default/topic/1061656/linux/gtx1650
  -notebook-not-working-on-ubuntu16-04-black-screen-amp-login-loop-/3

  There were temporary solutions which helped in booting, but the system
  is consistently giving error messages and crashing with packages such
  as realsense.

  Help thank you

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

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

[Desktop-packages] [Bug 1842740] Re: Critical gtx1650 driver unsuable resulting low graphics mode

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Critical gtx1650 driver unsuable resulting low graphics mode

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  Graphic driver of Nvidia's brand new model gtx 1650 ppa driver is unusable.
  Currently it is updated as nvidia 430.26 and it is crashing with system files.
  Whenever I install my graphic driver, I cannot boot the computer up it says 
low graphics mode.

  Please refer to it in the link below

  https://devtalk.nvidia.com/default/topic/1061656/linux/gtx1650
  -notebook-not-working-on-ubuntu16-04-black-screen-amp-login-loop-/3

  There were temporary solutions which helped in booting, but the system
  is consistently giving error messages and crashing with packages such
  as realsense.

  Help thank you

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

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

[Desktop-packages] [Bug 1847470] Re: [snap] kwallet not detected as password store

2019-10-10 Thread Olivier Tilloy

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [snap] kwallet not detected as password store

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  (initially reported at https://forum.snapcraft.io/t/call-for-testing-
  chromium-browser-deb-to-snap-transition/11772/8)

  « The test command¹ you use to detect backend:

  dbus-send --session --dest=org.freedesktop.secrets
  /org/freedesktop/secrets --print-reply
  org.freedesktop.DBus.Properties.GetAll
  string:'org.freedesktop.Secret.Service' >/dev/null 2>&1

  fails o my system (Ubuntu 19.04 + KDE session + kwallet) saying that
  nothing provides org.freedesktop.Secret.Service and chromium fallbacks
  to plain backend (losing my passwords). When I add --password-
  store=kwallet to desktop file command it works correctly.

  So current approach for backed detection is broken in my case (maybe
  in general for kwallet). Maybe it’s possible to test also kwallet
  equivalent of that command however I don’t know what i should be. »

  
  ¹ 
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=stable#n45

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847470/+subscriptions

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

[Desktop-packages] [Bug 1832374] Re: Media keys stop working due to missing service file

2019-10-10 Thread Bruce Pieterse

Just a quick update, I haven't had this issue since my last comment and
have since moved on to eoan as well.

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

Title:
  Media keys stop working due to missing service file

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Disco:
  Fix Committed

Bug description:
  * Impact 
  Sometime multimedia keys stop working

  * Test case
  - start playing an audio file in VLC/totem/smplayer
  - pause
  - open a video in another player
  - exit the other player
  - try to resume the music play from the first one using the play key

  -> it should work

  * Regression potential
  Make sure that multimedia play/pause keys keep working

  --

  Over the last two releases I've noticed that if you have an audio
  player such as Clementine running, pause the audio playback and watch
  a video via VLC or SMPlayer and then close the video player and try to
  use the media keys again, the following is logged to journald:

  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service
  files.

  From what I can see is that a service file is created for the media
  keys for SMPlayer, when SMPlayer is closed that service file is
  removed and then media keys are still bound to that service.

  I get the above output for previous track, stop, play, pause and next
  track media keys.

  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:

  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

  If you re-open SMPlayer and load a video, the media keys work and the
  GDBus error doesn't occur but the above "Overwriting ..." messages
  still get logged. Closing SMPlayer again does not restore media keys
  so that Clementine can handle them. I had SMPlayer running ~17 hours
  ago.

  Doing a shell reload doesn't seem to fix this either.

  I can't really tell if this is an SMPlay/VLC/Video Player issue or
  actually an issue in GSD, so filing here until someone can reassign to
  the relevant project.

  I hit this a while ago, while trying to get some debugging information
  for a Clementine bug: https://github.com/clementine-
  player/Clementine/issues/6320

  If you need any other information let me know.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-settings-daemon 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun 11 17:36:07 2019
  InstallationDate: Installed on 2019-02-01 (129 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20181202)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

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

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

[Desktop-packages] [Bug 1838605]

2019-10-10 Thread Standard8

*** Bug 1587798 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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1838605

Title:
  bookmark popover overflows screen vertically when selecting Folder:
  Choose

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

Bug description:
  I took a video. It also seems to show a minor bug with the built-in
  video capturing program accessed with ctrl-alt-shift-r

  https://youtu.be/1gHPMakVzSA

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 68.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gabe   1464 F pulseaudio
   /dev/snd/controlC0:  gabe   1464 F pulseaudio
  BuildID: 20190718161435
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  1 01:37:29 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-07-21 (10 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.2.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.2.0/24 dev wlo1 proto kernel scope link src 192.168.2.2 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=68.0.1/20190718161435 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8353
  dmi.board.vendor: HP
  dmi.board.version: 37.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.14:bd07/20/2017:svnHP:pnHPPavilionLaptop15-cd0xx:pvr:rvnHP:rn8353:rvr37.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cd0xx
  dmi.product.sku: 1DJ46AV
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10 Thread Yen-Yung Chang

Hi,

The issue persists.

-- 
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 1801540]

2019-10-10 Thread rodomar705

(In reply to Marco from comment #276)
> Following my previous post, disabling the batch flag on both streams (patch
> 3 from comment 269), Steam is perfect, Discord is lagged again while
> acquiring.
> 
> With the second patch from the comment 269, same identical problem without
> the patch (Discord perfect, Steam crackling for the first minute + audio
> slightly delayed). However when changing volume there was a little bit of
> distortion on the output audio (extremely small, but still audible,
> especially on high volumes), but it seems that using the workaround only on
> acquisition seems to have removed that small issue. If someone here had the
> same problem when changing volume, please try patch n.2 and report back.
> 
> It seems that we can't have both working together simultaneously on my end.
> The default workaround is still the best option on my system, for now.

The second patch cited in my previous post is necessary now (under
5.3.5, not sure about the previous kernel versions); besides the small
crackles when changing volumes, the acquisition from the microphone
under load (compilation, for example) sometimes becomes extremely low
quality (like if the sample rate is changing randomly and often the
audio is clipping). Applying the patch only on the capture stream
completely fix the issue, no crackles when changing volume and no issue
when acquiring audio with Discord under load.

Steam still shows random audio stutters while acquiring for a minute and
a bit of delay, so that is still unchanged, unfortunately.

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10 Thread Adam Conrad

(base)adconrad@nosferatu:~$ change-override -c main -S libextutils-depends-perl
Override component to main
libextutils-depends-perl 0.8000-1 in eoan: universe/perl -> main
libextutils-depends-perl 0.8000-1 in eoan amd64: universe/perl/optional/100% -> 
main
libextutils-depends-perl 0.8000-1 in eoan arm64: universe/perl/optional/100% -> 
main
libextutils-depends-perl 0.8000-1 in eoan armhf: universe/perl/optional/100% -> 
main
libextutils-depends-perl 0.8000-1 in eoan i386: universe/perl/optional/100% -> 
main
libextutils-depends-perl 0.8000-1 in eoan ppc64el: universe/perl/optional/100% 
-> main
libextutils-depends-perl 0.8000-1 in eoan s390x: universe/perl/optional/100% -> 
main
Override [y|N]? y
7 publications overridden.
(base)adconrad@nosferatu:~$ change-override -c main -S 
libextutils-pkgconfig-perl
Override component to main
libextutils-pkgconfig-perl 1.16-1 in eoan: universe/perl -> main
libextutils-pkgconfig-perl 1.16-1 in eoan amd64: universe/perl/optional/100% -> 
main
libextutils-pkgconfig-perl 1.16-1 in eoan arm64: universe/perl/optional/100% -> 
main
libextutils-pkgconfig-perl 1.16-1 in eoan armhf: universe/perl/optional/100% -> 
main
libextutils-pkgconfig-perl 1.16-1 in eoan i386: universe/perl/optional/100% -> 
main
libextutils-pkgconfig-perl 1.16-1 in eoan ppc64el: universe/perl/optional/100% 
-> main
libextutils-pkgconfig-perl 1.16-1 in eoan s390x: universe/perl/optional/100% -> 
main
Override [y|N]? y
7 publications overridden.


Promoted both as trivial perl packages in good standing that don't need further 
MIR review from the team.

** Changed in: libextutils-depends-perl (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: libextutils-pkgconfig-perl (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: libcairo-gobject-perl (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: libextutils-pkgconfig-perl (Ubuntu)
 Assignee: Ubuntu Desktop (ubuntu-desktop) => Adam Conrad (adconrad)

** Changed in: libextutils-depends-perl (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

-- 
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:
  Invalid
Status in libextutils-depends-perl package in Ubuntu:
  Fix Released
Status in libextutils-pkgconfig-perl package in Ubuntu:
  Fix Released

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 1847651] [NEW] NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved

2019-10-10 Thread Jonathan Kamens

Public bug reported:

I imported an openvpn configuration with `nmcli c import type openvpn file 
config.ovpn`.
After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off 
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains:

[main]
# We need to specify "dns=systemd-resolved" as for the time being our
# /etc/resolv.conf points to resolvconf's generated file instead of
# systemd-resolved's, so the auto-detection does not work.
dns=systemd-resolved

Given all this, what I believe _should_ happen is when I start the VPN,
/run/NetworkManager/no-stub-resolv.conf should be updated to list the
DNS server I've specified first, AND NetworkManager should tell systemd-
resolved to associate that DNS server with the tun0 network interface
created for the VPN.

The former happens, i.e., no-stub-resolv.conf is updated, but the latter
doesn't, i.e., systemd-reoslve --status and resolvectl status both do
not show the DNS server I've specified in the VPN settings.

As a result, my DNS server is not getting used.

I've hacked this all over the place and I can't figure out _any_ way,
when using systemd-resolved mode in NetworkManager, to get it to use my
VPN's DNS server when I enable the VPN.

Surely this behavior is not expected?

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
Uname: Linux 5.3.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 10 14:19:17 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-12 (28 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 10.204.0.1 dev wlp0s20f3 proto dhcp metric 600 
 10.204.0.0/21 dev wlp0s20f3 proto kernel scope link src 10.204.3.73 metric 600 
 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to eoan on 2019-09-20 (20 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  NetworkManager isn't pushing DNS server for openvpn connection to
  systemd-resolved

Status in network-manager package in Ubuntu:
  New

Bug description:
  I imported an openvpn configuration with `nmcli c import type openvpn file 
config.ovpn`.
  After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off 
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
  I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains:

  [main]
  # We need to specify "dns=systemd-resolved" as for the time being our
  # /etc/resolv.conf points to resolvconf's generated file instead of
  # systemd-resolved's, so the auto-detection does not work.
  dns=systemd-resolved

  Given all this, what I believe _should_ happen is when I start the
  VPN, /run/NetworkManager/no-stub-resolv.conf should be updated to list
  the DNS server I've specified first, AND NetworkManager should tell
  systemd-resolved to associate that DNS server with the tun0 network
  interface created for the VPN.

  The former happens, i.e., no-stub-resolv.conf is updated, but the
  latter doesn't, i.e., systemd-reoslve --status and resolvectl status
  both do not show the DNS server I've specified in the VPN settings.

  As a result, my DNS server is not getting used.

  I've hacked this all over the place and I can't figure out _any_ way,
  when using systemd-resolved mode in NetworkManager, to get it to use
  my VPN's DNS server when I enable the VPN.

  Surely this behavior is not expected?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 14:19:17 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (28 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-10 Thread Till Kamppeter

Great work, thank you very much!

It will need some testing of which I can only test the reproducer in the
initial description of this bug report, not any regressions which the
first attempt of upstream-update-based SRU, as I could not reproduce
these by myself.

So I would say to take this as a new proposed SRU and also ask the
reporters of the regressions whether this version does not cause them.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions

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

[Desktop-packages] [Bug 1847650] [NEW] When dock is on the right hand side it covers the 'page dots' on the 'all applications' icon view

2019-10-10 Thread Nicholas Harvey

Public bug reported:

Steps to duplicate:
1. Set Ubuntu Dock to be on the right hand side of the screen.
2. Click on the 'Show Applications' button which will be at the bottom-right of 
the screen.
3. When all of the application icons appear, you will notice that the 'dots' 
which can be clicked for switch from one page of icons to another are on the 
right of the screen underneath the Ubuntu dock. As such they cannot be clicked 
on.

Expected result:
Can the dots either move to the left of the screen (where there is no dock) or 
at least moved to a place where the dock does not obscure them?

Whilst this may not appear to be a major issue, I am running this on a
laptop using only a trackpad, and switching from one page of icons to
another is a but hit and miss as often a gentle swipe on my track pad
moves me two pages in either direction.

Thanks
Nick

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2
ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
Uname: Linux 5.3.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 10 19:16:05 2019
InstallationDate: Installed on 2019-09-23 (17 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago)

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  When dock is on the right hand side it covers the 'page dots' on the
  'all applications' icon view

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Steps to duplicate:
  1. Set Ubuntu Dock to be on the right hand side of the screen.
  2. Click on the 'Show Applications' button which will be at the bottom-right 
of the screen.
  3. When all of the application icons appear, you will notice that the 'dots' 
which can be clicked for switch from one page of icons to another are on the 
right of the screen underneath the Ubuntu dock. As such they cannot be clicked 
on.

  Expected result:
  Can the dots either move to the left of the screen (where there is no dock) 
or at least moved to a place where the dock does not obscure them?

  Whilst this may not appear to be a major issue, I am running this on a
  laptop using only a trackpad, and switching from one page of icons to
  another is a but hit and miss as often a gentle swipe on my track pad
  moves me two pages in either direction.

  Thanks
  Nick

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 19:16:05 2019
  InstallationDate: Installed on 2019-09-23 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago)

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

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

[Desktop-packages] [Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings

re: evince -->
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647

Screenshot attached. The Select Network screen, just like I originally
reported.

** Attachment added: "Screenshot from 2019-10-10 14-13-03.png"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847633/+attachment/5296287/+files/Screenshot%20from%202019-10-10%2014-13-03.png

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

Title:
  19.10 wifi networks menu doesn't respect natural scrolling settings

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce
  Be in 19.10
  Set natural scrolling to on/true/yes for mouse/touchpad
  Go to select network
  on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls 
down.

  I've only tested this with touchpad, but I'm guessing it affects mice
  too? Can anyone verify?

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

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

[Desktop-packages] [Bug 1847647] Re: Launchpad report bug is broken in so many ways

Screenshot -- I promise I just clicked submit IMMEDIATELY after this
screenshot, no funny business like retyping "evince" in the unselected
radio button text field and selecting it...

** Attachment added: "Screenshot from 2019-10-10 14-10-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647/+attachment/5296286/+files/Screenshot%20from%202019-10-10%2014-10-29.png

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

Title:
  Launchpad report bug is broken in so many ways

Status in evince package in Ubuntu:
  New

Bug description:
  1. You can't easily go to report a bug on launchpad.net.

  Go to https://bugs.launchpad.net/ubuntu/
  Click Report a Bug
  Expected Behavior: report a bug
  Actual behavior: Taken to stupid words
  Fix: Put a link on ALL major launchpad.net pages where you can click on 
"Report a Bug" and actually @#$(*& report a @#$( bug. Change all link text to 
https://help.ubuntu.com/community/ReportingBugs to "How to report bugs" or "Bug 
reporting FAQ", not "Report a bug".

  2. You can't report a bug in "I don't know" package.

  This bug is proof.
  Got to report a bug. Click "I don't know" radio for "In what package did you 
find this bug?"
  Optional: delete the package in unselected radio button below "I don't know"
  Bug will still be filed under a package; in this case, evince. It should be 
filed under NO PACKAGE or DONTKNOW or some placeholder package for all the 
unknown-package bugs.

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

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

[Desktop-packages] [Bug 1847647] [NEW] Launchpad report bug is broken in so many ways

Public bug reported:

1. You can't easily go to report a bug on launchpad.net.

Go to https://bugs.launchpad.net/ubuntu/
Click Report a Bug
Expected Behavior: report a bug
Actual behavior: Taken to stupid words
Fix: Put a link on ALL major launchpad.net pages where you can click on "Report 
a Bug" and actually @#$(*& report a @#$( bug. Change all link text to 
https://help.ubuntu.com/community/ReportingBugs to "How to report bugs" or "Bug 
reporting FAQ", not "Report a bug".

2. You can't report a bug in "I don't know" package.

This bug is proof.
Got to report a bug. Click "I don't know" radio for "In what package did you 
find this bug?"
Optional: delete the package in unselected radio button below "I don't know"
Bug will still be filed under a package; in this case, evince. It should be 
filed under NO PACKAGE or DONTKNOW or some placeholder package for all the 
unknown-package bugs.

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

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

Title:
  Launchpad report bug is broken in so many ways

Status in evince package in Ubuntu:
  New

Bug description:
  1. You can't easily go to report a bug on launchpad.net.

  Go to https://bugs.launchpad.net/ubuntu/
  Click Report a Bug
  Expected Behavior: report a bug
  Actual behavior: Taken to stupid words
  Fix: Put a link on ALL major launchpad.net pages where you can click on 
"Report a Bug" and actually @#$(*& report a @#$( bug. Change all link text to 
https://help.ubuntu.com/community/ReportingBugs to "How to report bugs" or "Bug 
reporting FAQ", not "Report a bug".

  2. You can't report a bug in "I don't know" package.

  This bug is proof.
  Got to report a bug. Click "I don't know" radio for "In what package did you 
find this bug?"
  Optional: delete the package in unselected radio button below "I don't know"
  Bug will still be filed under a package; in this case, evince. It should be 
filed under NO PACKAGE or DONTKNOW or some placeholder package for all the 
unknown-package bugs.

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10 Thread Brian Murray

$ 
/home/bdmurray/source-trees/ubuntu-qa-tools/ubuntu-qa-tools/launchpadlib-scripts/subscribe-to-package.py
 -u foundations-bugs -p libextutils-pkgconfig-perl 
foundations-bugs is now subscribed to all bugs about libextutils-pkgconfig-perl.

 $ 
/home/bdmurray/source-trees/ubuntu-qa-tools/ubuntu-qa-tools/launchpadlib-scripts/subscribe-to-package.py
 -u foundations-bugs -p
 libextutils-depends-perl  
foundations-bugs is now subscribed to all bugs about libextutils-depends-perl.

-- 
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 1834967] Re: Windows in Activities might be partially off screen

2019-10-10 Thread Treviño

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Windows in Activities might be partially off screen

Status in ubuntu-dock:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+subscriptions

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

[Desktop-packages] [Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings

Thank you for your bug report. Evince is the pdf reader, that doesn't
include wifi settings what UI are you talking about? Could you make
a screenshot show the screen?

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

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

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

Title:
  19.10 wifi networks menu doesn't respect natural scrolling settings

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce
  Be in 19.10
  Set natural scrolling to on/true/yes for mouse/touchpad
  Go to select network
  on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls 
down.

  I've only tested this with touchpad, but I'm guessing it affects mice
  too? Can anyone verify?

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

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

[Desktop-packages] [Bug 1847639] [NEW] Podcast can't resume play once it was paused

2019-10-10 Thread Rob

Public bug reported:

I just installed a fresh Ubuntu 19.10 and added a Podcast. I downloaded
an episode and pressed play. The podcast did not started to play. The
timecode "jumps" to 00:00:00 but it simply does not start.  When I
pressed the pause button, it stopped, but once I pressed the play button
again, it did not resume either. I tried this various times, it does not
matter if the episode is downloaded or streamed. Overall system sound
works just fine out of the box.

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

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

Title:
  Podcast can't resume play once it was paused

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I just installed a fresh Ubuntu 19.10 and added a Podcast. I
  downloaded an episode and pressed play. The podcast did not started to
  play. The timecode "jumps" to 00:00:00 but it simply does not start.
  When I pressed the pause button, it stopped, but once I pressed the
  play button again, it did not resume either. I tried this various
  times, it does not matter if the episode is downloaded or streamed.
  Overall system sound works just fine out of the box.

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

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

[Desktop-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

I'm experiencing this in 19.10

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

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

[Desktop-packages] [Bug 1847633] [NEW] 19.10 wifi networks menu doesn't respect natural scrolling settings

Public bug reported:

Steps to reproduce
Be in 19.10
Set natural scrolling to on/true/yes for mouse/touchpad
Go to select network
on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls 
down.

I've only tested this with touchpad, but I'm guessing it affects mice
too? Can anyone verify?

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

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

Title:
  19.10 wifi networks menu doesn't respect natural scrolling settings

Status in evince package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  Be in 19.10
  Set natural scrolling to on/true/yes for mouse/touchpad
  Go to select network
  on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls 
down.

  I've only tested this with touchpad, but I'm guessing it affects mice
  too? Can anyone verify?

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

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

[Desktop-packages] [Bug 1844829] Re: Windows can be clipped in Activities Overview

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

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

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

Title:
  Windows can be clipped in Activities Overview

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  If the windows you have open are large enough or numerous enough, the
  bottom previews will be clipped. This behavior did not happen
  previously afaik, as the windows would re-scale to avoid this, as they
  do without the dock installed. This is with a default installation of
  Ubuntu 19.10 and Ubuntu-Dock.

  Attached is a screenshot showing the behavior that I am talking about.
  If you mouse over the windows at the bottom, they are so far off the
  screen that you are unable to read their window titles any longer.

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

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

[Desktop-packages] [Bug 1834967] Re: Windows in Activities might be partially off screen

2019-10-10 Thread Treviño

** Summary changed:

- Activities overview doesn't shrink some windows adequately and they are 
partially off screen
+ Windows in Activities might be partially off screen

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

Title:
  Windows in Activities might be partially off screen

Status in ubuntu-dock:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+subscriptions

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

[Desktop-packages] [Bug 1847631] Re: Bug with start of the system Ubuntu 18.04 LTS

2019-10-10 Thread Konstantin

Thanks for this free system. I love Ubuntu but waiting for more stable
system 19.04 LTS in April!)

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

Title:
  Bug with start of the system Ubuntu 18.04 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  I am russian, so my English level is too low, I'll do my best.
  Technical characteristics is: Ryzen 3 2200U, Radeon Vega 3, RAM 8 Gb, 256 Gb 
SSD, IPS display 1920*1080 (if you need). Features is right, if you need a 
model of the laptop: Lenovo Ideapad 330-15ARR.
  Problem: 
  When I launch my laptop, in 3 of 4 cases it start with bugs. The most often 
problem is lack of Wi-fi connection when this module work. It is showing that's 
happening tries to connect to saved network, but nothing else. It resolves to 
open laptop's cover again. Second problem is black screen or hovering screen 
when system turns on. Well, in this case I reboot all computer again and again 
until it won't be normal. Usually, it takes about 3-4 times, no more.
   
  These problems on Russian: Самая частая проблема (в 3 из 4 открытий крышки 
ноутбука) - когда при включении ноутбука из сна, не подключается к сохраненной 
точке доступа wi-fi. Крутиться колесико, что идет попытка подключения, но 
ничего больше не происходит, и исправляется это закрытием и открытием крышки 
ноутбука снова. Я перепробовал все методы из интернета, но проблема так и не 
исчезла. Следующая проблема встречается не так часто как предыдущая, но тоже 
довольно нередкая. При полном включении ноутбука (не как в прошлом случае), 
система полностью зависает либо до предложения ввести пароль с черным экраном, 
либо после ввода пароля, но тоже с черным экраном. Третья и последняя проблема 
- зависание системы с нормальным ходом звука или также с его заглючиванием во 
время работы. Просто работаешь и она вдруг зависает, ничего не помогает кроме 
перезапуска всей системы. Кроме данных багов ничего не раздражает, очень 
нравится система. Переустанавливал уже более 5 раз, всегда наблюдаю такие 
проблемы. Установочный образ не поврежден, так как у друзей все работает без 
каких-либо багов и зависаний. Очень нравится система, жду более стабильную 
19.04 LTS и сразу же обновлюсь на нее.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 20:30:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, v5.2.5_1.26055.20180108.1, 4.15.0-64-generic, x86_64: installed
   rtl8821ce, v5.2.5_1.26055.20180108.1, 4.15.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:38ef]
  InstallationDate: Installed on 2019-07-22 (80 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81D2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=66f72524-149c-45c0-8f82-857606a10e7d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN24WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN24WW:bd06/15/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1847631] [NEW] Bug with start of the system Ubuntu 18.04 LTS

2019-10-10 Thread Konstantin

Public bug reported:

I am russian, so my English level is too low, I'll do my best.
Technical characteristics is: Ryzen 3 2200U, Radeon Vega 3, RAM 8 Gb, 256 Gb 
SSD, IPS display 1920*1080 (if you need). Features is right, if you need a 
model of the laptop: Lenovo Ideapad 330-15ARR.
Problem: 
When I launch my laptop, in 3 of 4 cases it start with bugs. The most often 
problem is lack of Wi-fi connection when this module work. It is showing that's 
happening tries to connect to saved network, but nothing else. It resolves to 
open laptop's cover again. Second problem is black screen or hovering screen 
when system turns on. Well, in this case I reboot all computer again and again 
until it won't be normal. Usually, it takes about 3-4 times, no more.
 
These problems on Russian: Самая частая проблема (в 3 из 4 открытий крышки 
ноутбука) - когда при включении ноутбука из сна, не подключается к сохраненной 
точке доступа wi-fi. Крутиться колесико, что идет попытка подключения, но 
ничего больше не происходит, и исправляется это закрытием и открытием крышки 
ноутбука снова. Я перепробовал все методы из интернета, но проблема так и не 
исчезла. Следующая проблема встречается не так часто как предыдущая, но тоже 
довольно нередкая. При полном включении ноутбука (не как в прошлом случае), 
система полностью зависает либо до предложения ввести пароль с черным экраном, 
либо после ввода пароля, но тоже с черным экраном. Третья и последняя проблема 
- зависание системы с нормальным ходом звука или также с его заглючиванием во 
время работы. Просто работаешь и она вдруг зависает, ничего не помогает кроме 
перезапуска всей системы. Кроме данных багов ничего не раздражает, очень 
нравится система. Переустанавливал уже более 5 раз, всегда наблюдаю такие 
проблемы. Установочный образ не поврежден, так как у друзей все работает без 
каких-либо багов и зависаний. Очень нравится система, жду более стабильную 
19.04 LTS и сразу же обновлюсь на нее.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 10 20:30:19 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 rtl8821ce, v5.2.5_1.26055.20180108.1, 4.15.0-64-generic, x86_64: installed
 rtl8821ce, v5.2.5_1.26055.20180108.1, 4.15.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:38ef]
InstallationDate: Installed on 2019-07-22 (80 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 81D2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=66f72524-149c-45c0-8f82-857606a10e7d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 7VCN24WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN24WW:bd06/15/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
dmi.product.family: ideapad 330-15ARR
dmi.product.name: 81D2
dmi.product.version: Lenovo ideapad 330-15ARR
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic resolution ubuntu

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

Title:
  Bug with start of the system Ubuntu 18.04 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  I am russian, so my English level is too low, I'll do my best.
  Technical characteristics is: Ryzen 3 2200U, Radeon Vega 3, RAM 8 Gb, 256 Gb 
SSD,

[Desktop-packages] [Bug 1797734] Re: slow calculator startup

2019-10-10 Thread Fabio Olaechea

Hi, Ubuntu 18.04.3 LTS running on SSD laptop with 16GB ram and i7 cpu
here, i can confirm that startup was very slow and was solved doing:

$ snap remove gnome-calculator
$ sudo apt-get install gnome-calculator


Before the "snap remove" startup time was as minimum 10 secs, now is 1 sec or 
less.

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2019-10-10 Thread nicola

how do I install kernel 5.4

hp@hp-desktop:~$ sudo apt install linux-image-
Display all 572 possibilities? (y or n)
hp@hp-desktop:~$ sudo apt install linux-image-5.0.0-
linux-image-5.0.0-1010-oem-osp1  linux-image-5.0.0-1013-gke   
linux-image-5.0.0-1017-gke   linux-image-5.0.0-1020-oem-osp1  
linux-image-5.0.0-16-lowlatency  linux-image-5.0.0-23-generic 
linux-image-5.0.0-29-lowlatency
linux-image-5.0.0-1011-aws   linux-image-5.0.0-1014-aws   
linux-image-5.0.0-1018-aws   linux-image-5.0.0-1022-azure 
linux-image-5.0.0-17-generic linux-image-5.0.0-23-lowlatency  
linux-image-5.0.0-31-generic
linux-image-5.0.0-1011-gcp   linux-image-5.0.0-1014-azure 
linux-image-5.0.0-1018-azure linux-image-5.0.0-1022-oem-osp1  
linux-image-5.0.0-17-lowlatency  linux-image-5.0.0-25-generic 
linux-image-5.0.0-31-lowlatency
linux-image-5.0.0-1012-aws   linux-image-5.0.0-1015-gke   
linux-image-5.0.0-1018-oem-osp1  linux-image-5.0.0-1024-oem-osp1  
linux-image-5.0.0-19-generic linux-image-5.0.0-25-lowlatency  
linux-image-5.0.0-1012-azure linux-image-5.0.0-1015-oem-osp1  
linux-image-5.0.0-1020-azure linux-image-5.0.0-15-generic 
linux-image-5.0.0-19-lowlatency  linux-image-5.0.0-27-generic 
linux-image-5.0.0-1012-oem-osp1  linux-image-5.0.0-1016-aws   
linux-image-5.0.0-1020-gcp   linux-image-5.0.0-15-lowlatency  
linux-image-5.0.0-20-generic linux-image-5.0.0-27-lowlatency  
linux-image-5.0.0-1013-gcp   linux-image-5.0.0-1016-azure 
linux-image-5.0.0-1020-gke   linux-image-5.0.0-16-generic 
linux-image-5.0.0-20-lowlatency  linux-image-5.0.0-29-generic 
hp@hp-desktop:~$ sudo apt install linux-image-5.0.0-


these are the images via apt, please give me the command line on how

-- 
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 1847603] Re: After upgrading Ubuntu 19.10 second screen not detected

Whith the kernel linux-image-5.0.0-31-generic the second screen was
detected

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

Title:
  After upgrading Ubuntu 19.10 second screen not detected

Status in lightdm package in Ubuntu:
  New

Bug description:
  After upgrading Ubuntu 19.10 second screen not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 10 14:56:33 2019
  LightdmConfig:
   [Seat:*]
   #autologin-guest=false
   #autologin-user=caiofior
   #autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847603] Re: After upgrading Ubuntu 19.10 second screen not detected

I suppose it is a kernel bug, this is the output of xrandr
 
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080 77.00* 

I do not see another screen

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

Title:
  After upgrading Ubuntu 19.10 second screen not detected

Status in lightdm package in Ubuntu:
  New

Bug description:
  After upgrading Ubuntu 19.10 second screen not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 10 14:56:33 2019
  LightdmConfig:
   [Seat:*]
   #autologin-guest=false
   #autologin-user=caiofior
   #autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-10 Thread Dariusz Gadomski

I have backported what was listed as nm-1-10 fix for the bug in the upstream 
bugzilla [1].
I have also applied fixes for bug #1825946 and bug #1790098 to it.

[1]
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1e486a721de1fec76c81bfc461671a7fbdae531b

After testing this build for some time (available at ppa:dgadomski
/network-manager) I haven't found any problems.

@Till I'd appreciate you having a look at it. Thanks!

** Patch added: "bionic_network-manager_1.10.6-2ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671/+attachment/5296236/+files/bionic_network-manager_1.10.6-2ubuntu1.2.debdiff

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

Thank you for your bug report, could you take a screenshot showing the error?
What desktop environement are you using?
What's the gnome-control-center version installed? (dpkg -l | grep 
gnome-control-center)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  gnome-control-center cannot access google account

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

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

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

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

[Desktop-packages] [Bug 1847618] [NEW] language selector ignores input methods other than xim and none in my current locale

2019-10-10 Thread kenn

Public bug reported:

I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as
ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not
listed in unity-control-center>Language Support>Keyboard Input Method
System. If I launch unity-control-center from terminal which is using
different locale "LANGUAGE=en_US.utf8 unity-control-center" then there
is no problem, all of the installed input methods are in the list.

I also tested "python3 
/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py"
it also ignores input methods other than xim and none.
If I export "LANGUAGE=en_US.utf8" it lists all the other input methods.

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  language selector ignores  input methods other than xim and none in my
  current locale

Status in language-selector package in Ubuntu:
  New

Bug description:
  I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as
  ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's
  not listed in unity-control-center>Language Support>Keyboard Input
  Method System. If I launch unity-control-center from terminal which is
  using different locale "LANGUAGE=en_US.utf8 unity-control-center" then
  there is no problem, all of the installed input methods are in the
  list.

  I also tested "python3 
/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py"
  it also ignores input methods other than xim and none.
  If I export "LANGUAGE=en_US.utf8" it lists all the other input methods.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1847618/+subscriptions

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

[Desktop-packages] [Bug 1847615] Re: After upgrading Ubuntu 19.10 sound not working

the alsa log indicates there is no sound card listed, it's likely a
kernel bug

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

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

Title:
  After upgrading Ubuntu 19.10 sound not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading Ubuntu 19.10 sound not working

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Oct 10 16:03:50 2019
  ProcEnviron:
   LANGUAGE=it_IT
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1847615] [NEW] After upgrading Ubuntu 19.10 sound not working

Public bug reported:

After upgrading Ubuntu 19.10 sound not working

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Oct 10 16:03:50 2019
ProcEnviron:
 LANGUAGE=it_IT
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2019
dmi.bios.vendor: HP
dmi.bios.version: N01 Ver. 02.42
dmi.board.name: 8054
dmi.board.vendor: HP
dmi.board.version: KBC Version 05.36
dmi.chassis.asset.tag: CZC64082W1
dmi.chassis.type: 4
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G2 SFF
dmi.product.sku: X3J10ET#ABZ
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug eoan

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

Title:
  After upgrading Ubuntu 19.10 sound not working

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading Ubuntu 19.10 sound not working

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Oct 10 16:03:50 2019
  ProcEnviron:
   LANGUAGE=it_IT
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

This bug was fixed in the package cups-filters - 1.25.11-0ubuntu1

---
cups-filters (1.25.11-0ubuntu1) eoan; urgency=medium

  - cups-browsed: Fixed printing on remote printers which only
support IPP 1.1 (Upstream issue #124, #163).

 -- Till Kamppeter   Thu, 10 Oct 2019 12:48:32
+0200

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

-- 
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 Released

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 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

2019-10-10 Thread Hui Wang

If there is no change for any pins after plugging the headset, probably
it is a hw design issue or a codec coeff setting issue, we couldn't
handle it.

Please test the latest mainline kernel https://kernel.ubuntu.com
/~kernel-ppa/mainline/v5.4-rc2/

If it doesn't work too.

please test with windows. If windows doesn't work, probably it is a HW
design issue.

If windows works, please file a bug on the bugzilla of mainline kernel,
maybe realtek engineer will look at this bug.

-- 
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 1520033] Re: ftbfs on s390x

2019-10-10 Thread Dimitri John Ledkov

It fails to build in Debian too.

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

Title:
  ftbfs on s390x

Status in mono package in Ubuntu:
  Confirmed

Bug description:
  ftbfs on s390x

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

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

[Desktop-packages] [Bug 1520033] Re: ftbfs on s390x

2019-10-10 Thread Dimitri John Ledkov

** Attachment added: "mono_5.18.0.240+dfsg-5_s390x.build.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1520033/+attachment/5296217/+files/mono_5.18.0.240+dfsg-5_s390x.build.gz

** Changed in: mono (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

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

Title:
  ftbfs on s390x

Status in mono package in Ubuntu:
  Confirmed

Bug description:
  ftbfs on s390x

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

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

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

2019-10-10 Thread Paul White

Comments #17 and #24 closed this bug report as being invalid but it was
reopened as many users required a version of Lightning in a language
other than English which could at the time of reporting only be obtained
from the Thunderbird web-site.

There have been no comments here for almost a year. The release of
Thunderbird 60.9.0 includes translations in the Lightning package (xul-
ext-lightning). This package is updated each time Thunderbird itself
receives an update.

Bug #545778, referring to Lightning being in English only, has been
closed as being fixed so this bug report should be closed as being fixed
too.


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

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

  --

  WORKAROUNDS:

  Until this is fixed (as per the problems listed in #25), pick an
  answer that works best for you (English vs. other languages) at
  https://askubuntu.com/questions/1084059/latest-update-to-
  thunderbird-60-2-1-on-18-04-lightning-calendar-missing .

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

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

[Desktop-packages] [Bug 1847603] [NEW] After upgrading Ubuntu 19.10 second screen not detected

Public bug reported:

After upgrading Ubuntu 19.10 second screen not detected

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: lightdm 1.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 10 14:56:33 2019
LightdmConfig:
 [Seat:*]
 #autologin-guest=false
 #autologin-user=caiofior
 #autologin-user-timeout=0
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  After upgrading Ubuntu 19.10 second screen not detected

Status in lightdm package in Ubuntu:
  New

Bug description:
  After upgrading Ubuntu 19.10 second screen not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 10 14:56:33 2019
  LightdmConfig:
   [Seat:*]
   #autologin-guest=false
   #autologin-user=caiofior
   #autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847602] [NEW] Package libglib2.0-0:armhf fails to install: Exec format error

2019-10-10 Thread Dale Smith

Public bug reported:

Description:Ubuntu 18.04.3 LTS
Release:18.04

uname -a: Linux dtsmith-vallum 4.15.0-65-generic #74-Ubuntu SMP Tue Sep
17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

All updates available to date have been applied.

Command is "sudo apt-get install libglib2.0-0:armhf"

Debian team supposed to fix this bug with package version 2.54.2-5 see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885019

I am doing cross-compile work with the following compilers

arm-linux-gnueabihf-gcc-8 from package gcc-8-arm-linux-gnueabihf

The schemas from the native gcc-7 package are in
/usr/share/glib-2.0/schemas.

"sudo apt-get install libglib2.0-dev:armhf" has the same error.

Work-around is to install libglib2.0-dev for the host. The schema files
are in /usr/share/glib-2.0. I have cross-compiled syslog-ng as armhf and
it works.

Here is the output of the apt install command:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/2,186 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 172895 files and directories currently installed.)
Preparing to unpack .../libglib2.0-0_2.56.4-0ubuntu0.18.04.4_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.4) over 
(2.56.4-0ubuntu0.18.04.4) ...
Preparing to unpack .../libglib2.0-0_2.56.4-0ubuntu0.18.04.4_armhf.deb ...
Unpacking libglib2.0-0:armhf (2.56.4-0ubuntu0.18.04.4) over 
(2.56.4-0ubuntu0.18.04.4) ...
Setting up libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.4) ...
Setting up libglib2.0-0:armhf (2.56.4-0ubuntu0.18.04.4) ...
/var/lib/dpkg/info/libglib2.0-0:armhf.postinst: 39: 
/var/lib/dpkg/info/libglib2.0-0:armhf.postinst: 
/usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas: Exec format error
Processing triggers for libc-bin (2.27-3ubuntu1) ...
dtsmith@dtsmith-vallum:[~]$ 
/usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas
bash: /usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas: cannot 
execute binary file: Exec format error

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libglib2.0-0:armhf 2.56.4-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 10 07:47:58 2019
InstallationDate: Installed on 2019-10-09 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: armhf
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf bionic

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

Title:
  Package libglib2.0-0:armhf fails to install: Exec format error

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  uname -a: Linux dtsmith-vallum 4.15.0-65-generic #74-Ubuntu SMP Tue
  Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  All updates available to date have been applied.

  Command is "sudo apt-get install libglib2.0-0:armhf"

  Debian team supposed to fix this bug with package version 2.54.2-5 see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885019

  I am doing cross-compile work with the following compilers

  arm-linux-gnueabihf-gcc-8 from package gcc-8-arm-linux-gnueabihf

  The schemas from the native gcc-7 package are in
  /usr/share/glib-2.0/schemas.

  "sudo apt-get install libglib2.0-dev:armhf" has the same error.

  Work-around is to install libglib2.0-dev for the host. The schema
  files are in /usr/share/glib-2.0. I have cross-compiled syslog-ng as
  armhf and it works.

  Here is the output of the apt install command:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/2,186 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 172895 files and directories currently installed.)
  Preparing to unpack .../libglib2.0-0_2.56.4-0ubuntu0.18.04.4_amd64.deb ...
  Unpacking libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.4) over 
(2.56.4-0ubuntu0.18.04.4) ...
  Preparing to unpack .../libglib2.0-0_2.56.4-0ubuntu0.18.04.4_armhf.deb ...
  Unpacking libglib2.0-0:armhf (2.56.4-0ubuntu0.18.04.4) over 
(2.56.4-0ubuntu0.18.04.4) ...
  Setting up libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.4) ...
  Setting up

[Desktop-packages] [Bug 1847597] [NEW] gnome-control-center cannot access google account

2019-10-10 Thread Luigi

Public bug reported:

Good morning,

If I run "gnome-control-center online-accounts" from the terminal and
trying to add a Google account, I get this error: "Sign in with Google
is temporarily disabled for this app. This app has not been verified yet
by Google in order to use Google sign in". On the web, Google suggests
to contact you, so here I am. Can you fix please? I would use my drive
folders on my ubuntu 16.04. Thanks in advance.

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

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

Title:
gnome-control-center cannot access google account

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

Bug description:
Good morning,

If I run "gnome-control-center online-accounts" from the terminal and
trying to add a Google account, I get this error: "Sign in with Google
is temporarily disabled for this app. This app has not been verified
yet by Google in order to use Google sign in". On the web, Google
suggests to contact you, so here I am. Can you fix please? I would use
my drive folders on my ubuntu 16.04. Thanks in advance.

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-10-10 Thread Bug Watch Updater

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

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

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

2019-10-10 Thread Olivier Tilloy

Thanks for the feedback. Could you please reproduce the freeze, and
after rebooting, run the following commands in a terminal and attach the
resulting /tmp/journal.tar.bz2 file (or make it available somewhere):

journalctl -b-1 > /tmp/journal.txt
tar cjf /tmp/journal.tar.bz2 /tmp/journal.txt

Thanks!

-- 
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 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

2019-10-10 Thread nicola

I cannot run hdajacksensetest, hdajackretask is a graphical tool to see
pin


hh@hh-desktop:~$ sudo hdajacksensetest -a
sudo: hdajacksensetest: comando non trovato
hh@hh-desktop:~$ sudo hdajacksensetest -a
sudo: hdajacksensetest: comando non trovato
hh@hh-desktop:~$ sudo apt-cache search hdajackretask
alsa-tools-gui - utilità ALSA per hardware specifico basate su interfaccia 
grafica

sorry but from the image (before and after plugging in headset) I do not
see any difference. https://imgur.com/a/n22SkIw

-- 
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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-10-10 Thread Michael Vogt

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

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749
   Importance: Unknown
   Status: Unknown

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

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

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10 Thread Olivier Tilloy

Thanks for the feedback.

There were many changes between 16.04 that your friend is using and
18.04 that you're using, so it would be useful to compare with someone
on 18.04, if you can.

The fact that this works with Chrome suggests something firefox-specific
indeed. Can you try running firefox with a clean profile ("firefox -P")
and see whether the issue persists?

-- 
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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34

2019-10-10 Thread Jeremy Bicha

This bug was fixed in the package gnome-shell-extension-dashtodock -
67-1

---
gnome-shell-extension-dashtodock (67-1) unstable; urgency=high

  * Team upload
  * New upstream release
  * Update for GNOME Shell 3.34 (Closes: #941674)
  * Drop Testsuite field as there is no debian/tests/control
  * Update Standards-Version to 4.4.1

 -- Raphaël Hertzog   Thu, 10 Oct 2019 08:56:56
+0200

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Extensions don't load in gnome-shell 3.33/3.34

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Some extensions don't load in gnome-shell 3.33/3.34

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

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

[Desktop-packages] [Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"

2019-10-10 Thread dennis

[heidi@heidi-pc log]$ hp-setup  -u

HP Linux Imaging and Printing System (ver. 3.19.8)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Searching... (bus=usb, search=(None), desc=0)
error:  Printer queue setup failed.   Error : 
successful-ok-ignored-or-substituted-attributes

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

Title:
  adding printer with IPP network printer via DNS-DS fails due to "There
  was an error during the CUPS operation: 'server-error-internal-error'"

Status in system-config-printer package in Ubuntu:
  Expired

Bug description:
  Adding a Hewlett-Packard HP Color LaserJet MFP M476dn as IPP network
  printer via DNS-DS fails due to "There was an error during the CUPS
  operation: 'server-error-internal-error'". The error message is
  unhelpful and can't be copied. The output of the console is

  > system-config-printer

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_insert_after: assertion 'G_NODE
  (sibling->user_data)->parent == G_NODE (parent->user_data)' failed

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)'
  failed

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)'
  failed

  (system-config-printer.py:21002): Gtk-WARNING **: Failed to fetch network 
locations: Timeout was reached
  Caught non-fatal exception.  Traceback:
  File "/usr/share/system-config-printer/newprinter.py", line 4196, in 
getNPPPD
  ppd = cups.PPD(f)
  RuntimeError: ppdOpenFile failed
  Continuing anyway..

  which looks like the error message could be improved dramatically.

  The same issue happens for Driverless IPP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: system-config-printer 1.5.7+20160812-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 28 14:40:51 2017
  InstallationDate: Installed on 2015-12-12 (594 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat:
   Gerät für HP_Color_LaserJet_MFP_M476dn: 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
   Gerät für QL-570: usb://Brother/QL-570?serial=F4Z735525
  MachineType: LENOVO 20221
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   QL-570: Brother QL-570 CUPS v1.1
   HP_Color_LaserJet_MFP_M476dn: HP Color LaserJet Pro MFP M476 Postscript 
(recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: system-config-printer
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (88 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions

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

[Desktop-packages] [Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"

2019-10-10 Thread dennis

Hi Kevin

[heidi@heidi-pc log]$ driverless 
ipp://HPE4E7498BF1E5.local:631/ipp/print

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

Title:
  adding printer with IPP network printer via DNS-DS fails due to "There
  was an error during the CUPS operation: 'server-error-internal-error'"

Status in system-config-printer package in Ubuntu:
  Expired

Bug description:
  Adding a Hewlett-Packard HP Color LaserJet MFP M476dn as IPP network
  printer via DNS-DS fails due to "There was an error during the CUPS
  operation: 'server-error-internal-error'". The error message is
  unhelpful and can't be copied. The output of the console is

  > system-config-printer

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_insert_after: assertion 'G_NODE
  (sibling->user_data)->parent == G_NODE (parent->user_data)' failed

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)'
  failed

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)'
  failed

  (system-config-printer.py:21002): Gtk-WARNING **: Failed to fetch network 
locations: Timeout was reached
  Caught non-fatal exception.  Traceback:
  File "/usr/share/system-config-printer/newprinter.py", line 4196, in 
getNPPPD
  ppd = cups.PPD(f)
  RuntimeError: ppdOpenFile failed
  Continuing anyway..

  which looks like the error message could be improved dramatically.

  The same issue happens for Driverless IPP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: system-config-printer 1.5.7+20160812-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 28 14:40:51 2017
  InstallationDate: Installed on 2015-12-12 (594 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat:
   Gerät für HP_Color_LaserJet_MFP_M476dn: 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
   Gerät für QL-570: usb://Brother/QL-570?serial=F4Z735525
  MachineType: LENOVO 20221
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   QL-570: Brother QL-570 CUPS v1.1
   HP_Color_LaserJet_MFP_M476dn: HP Color LaserJet Pro MFP M476 Postscript 
(recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: system-config-printer
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (88 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions

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

[Desktop-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL

This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.3

---
mesa (19.0.8-0ubuntu0~18.04.3) bionic; urgency=medium

  * i965-sync-pciids.diff: Add missing pci-id's, fix descriptions. (LP:
#1845317)

 -- Timo Aaltonen   Thu, 26 Sep 2019 07:58:03 +0300

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

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

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

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

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

[Desktop-packages] [Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"

2019-10-10 Thread dennis

** Attachment added: "output from system-config-printer"
   
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+attachment/5296157/+files/log.txt

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

Title:
  adding printer with IPP network printer via DNS-DS fails due to "There
  was an error during the CUPS operation: 'server-error-internal-error'"

Status in system-config-printer package in Ubuntu:
  Expired

Bug description:
  Adding a Hewlett-Packard HP Color LaserJet MFP M476dn as IPP network
  printer via DNS-DS fails due to "There was an error during the CUPS
  operation: 'server-error-internal-error'". The error message is
  unhelpful and can't be copied. The output of the console is

  > system-config-printer

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_insert_after: assertion 'G_NODE
  (sibling->user_data)->parent == G_NODE (parent->user_data)' failed

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)'
  failed

  (system-config-printer.py:21002): Gtk-CRITICAL **:
  gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)'
  failed

  (system-config-printer.py:21002): Gtk-WARNING **: Failed to fetch network 
locations: Timeout was reached
  Caught non-fatal exception.  Traceback:
  File "/usr/share/system-config-printer/newprinter.py", line 4196, in 
getNPPPD
  ppd = cups.PPD(f)
  RuntimeError: ppdOpenFile failed
  Continuing anyway..

  which looks like the error message could be improved dramatically.

  The same issue happens for Driverless IPP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: system-config-printer 1.5.7+20160812-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 28 14:40:51 2017
  InstallationDate: Installed on 2015-12-12 (594 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat:
   Gerät für HP_Color_LaserJet_MFP_M476dn: 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
   Gerät für QL-570: usb://Brother/QL-570?serial=F4Z735525
  MachineType: LENOVO 20221
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   QL-570: Brother QL-570 CUPS v1.1
   HP_Color_LaserJet_MFP_M476dn: HP Color LaserJet Pro MFP M476 Postscript 
(recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: system-config-printer
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (88 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions

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

[Desktop-packages] [Bug 1845317] Update Released

2019-10-10 Thread Łukasz Zemczak

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

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

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

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

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

[Desktop-packages] [Bug 1838878] Re: Branch 430 does not support K1100M

2019-10-10 Thread Douglas Russell

Perhaps even more problematic is that the .430 driver does not have
support for the new T4 cards, whereas .418 does.

I am not an expert on Nvidia drivers, but it is very surprising to me
that the older version of the driver has support for a new piece of
hardware where the new driver does not, but either way, it would be very
useful to be able to install actual .418 driver on Ubuntu 18.04.

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

Title:
  Branch 430 does not support K1100M

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  New

Bug description:
  Branch 430 does not support K1100M, yet it is proposed as an update to
  branch 418 users with an nVidia K1100M GPU.

  Please see supported devices for 430 branch here
  https://www.nvidia.com/Download/driverResults.aspx/149138/en-us

  and 418 branch here
  https://www.nvidia.com/Download/driverResults.aspx/149219/en-us

  It is not possible to downgrade to 418 because the ppa package was
  replaced by a "transition layer" to branch 430.

  No changelog was presented by synaptic prior to upgrade to inform user
  that the nVidia K1100M support was dropped.

  $ apt-cache showpkg nvidia-driver-418
  Package: nvidia-driver-418
  Versions: 
  430.40-0ubuntu0~gpu18.04.1 
(/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages)
   Description Language: 
   File: 
/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages
MD5: 4827e73f0efd6022196ef03ec384d854
   Description Language: en
   File: 
/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_i18n_Translation-en
MD5: 4827e73f0efd6022196ef03ec384d854

  
  Reverse Depends: 
  Dependencies: 
  430.40-0ubuntu0~gpu18.04.1 - nvidia-driver-430 (0 (null)) 
  Provides: 
  430.40-0ubuntu0~gpu18.04.1 - 
  Reverse Provides:

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

Or maybe just for Ubuntu, consider adding module parameter
'only_from_unavailable'. I wonder if that might have any undesirable
consequences?

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2019-10-10 Thread Hui Wang

According to #11, it didn't detect the plugging on the headphone jack.

please run sudo hdajacksensetest -a before headphone jack is plugged,

then plug a headphone in the headphone jack,

rerun the sudo hdajacksensetest -a  and compare which pin is changed.

-- 
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 1841709] Re: [regression] gobject.h:767: syntax error

Fixed in https://gitlab.gnome.org/GNOME/mutter/merge_requests/841

** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)

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

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags added: fixed-in-3.34.2 fixed-upstream

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

Title:
  [regression] gobject.h:767: syntax error

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Building mutter...

  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected '/' in 
'  do { if g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at '/'
  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected ')', 
expecting identifier or '(' in '  do { if 
g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at ')'
  /usr/include/glib-2.0/gobject/gobject.h:770: syntax error, unexpected ')', 
expecting identifier or '(' in '# 770 
"/usr/include/glib-2.0/gobject/gobject.h"' at ')'

  Looks like the offending release glib2.0 (2.61.2-2) is from last
  night's updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libglib2.0-dev 2.61.2-2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Aug 28 11:30:06 2019
  InstallationDate: Installed on 2019-05-02 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

I also wonder if the original reasons for us wanting that module (USB
DACs and Bluetooth) still really need it in the current version.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

I *think* what we want from upstream is for module-switch-on-connect to
ignore new connections which are detected around the same time as the
daemon starting. Because those are not user-initiated but more likely
just a side-effect of logging in.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

[Desktop-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

2019-10-10 Thread Ed Saunders

I've recently just run into the same problem since recent updates, I've
had my XPS since October 2017 and am currently running Ubuntu 18.04.3.
No issues until last week. I think I may have selected "headset with
microphone" by accident once when inserting headphones without a
microphone, but no evidence that this was related; I just remember doing
it when I don't recall doing that before.

The initial workaround in this thread of updating "Headphone Mic Boost"
setting up one notch in alsamixer works for me, so I assume this is a
regression or was this never fixed?

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Desktop-packages] [Bug 1842662] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1842662/+attachment/5296154/+files/ShellJournal.txt

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1842662] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1842662/+attachment/5296155/+files/monitors.xml.txt

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1847570] Re: Preferred output device is not remembered between logins

Workaround: Comment out:

load-module module-switch-on-port-available
load-module module-switch-on-connect

from /etc/pulse/default.pa


** This bug is no longer a duplicate of bug 1631161
   Preferred output device is not remembered between logins

** Summary changed:

- Preferred output device is not remembered between logins
+ PulseAudio automatically switches to HDMI sound output on login

** Changed in: pulseaudio (Ubuntu)
   Importance: High => Medium

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

[Desktop-packages] [Bug 1842662] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1842662/+attachment/5296152/+files/ProcEnviron.txt

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1842662] Re: Gnome Dash (vanilla - no extensions) first icon always missing unless you open the dash soon after login

apport information

** Tags added: apport-collected disco wayland-session

** Description changed:

  Using Vanilla Gnome session, with extensions turned off, the dash icons
  on the left of the screen do not display properly.
  
  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open the
  application).
  
  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical
  
  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.
  
  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.
  
- This is the same behavior as shown at this askubuntu link, and has been
- occurring ever since updating to 19.04:
- https://askubuntu.com/questions/1142990/first-most-application-icon-on-
- dash-hidden-until-gnome-shell-
- restarts?newreg=d0a226571a884b3fb3efed0639123106
+ This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2013-12-07 (2132 days ago)
+ InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
+ Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
+ RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
+ Tags:  wayland-session disco
+ Uname: Linux 5.0.0-31-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
+ UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1842662/+attachment/5296149/+files/Dependencies.txt

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

To

[Desktop-packages] [Bug 1842662] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1842662/+attachment/5296151/+files/ProcCpuinfoMinimal.txt

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1842662] GsettingsChanges.txt