[Desktop-packages] [Bug 1828123] Re: File names are percent-encoded when connect to webdav server

[Sebastien Bacher]

Thank you for your bug report. What Ubuntu/nautilus version do you use?
Does "gio ls dav://:..." has the same issue or is it specific to nautilus?

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

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

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

Title:
  File names are percent-encoded when connect to webdav server

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When I connected to a Webdav server set up by nginx using the default
  file manager, some non-English characters in file and folder names are
  displayed as percent-encoded(url-encoded).  For example,
  "%E4%B8%8D%E5%AE%89%E4%B8%8E%E6%AC%B2%E6%9C%9B" is displayed instead
  of "不安与欲望", and the " "(space) in a file name is displayed as "%20".
  Once I copied those files to local disk, the file names are displayed
  correctly.

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Daniel van Vugt]

No, the fix is not yet available.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

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

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[PeterPall]

@Luca-mg: What your computer sees is the following:
 - You attach a device whose USB ID doesn't match any udev rule => the device 
is accessible for the root user only.
 - then you as the root user start a program that uploads something to the 
device.
 - the device disconnects and
 - a new device connects, this time using an USB ID there is an udev rule for. 
This rule tells the device is a scanner. You are in the group "scanner" => You 
can use it without root rights.

What you need is an udev rule that tells the system that the USB ID your
device has before its firmware is uploaded is a scanner, too. As soon as
udev knows that this device is a scanner it will give you the necessary
rights to upload the firmware without being root.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Pedro]

My ubuntu 18.04 have already been updated to the latest state! 
But it still crash when I swich workspace.
Is any package I need to install to solve this bug? Or other suggestion?

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

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

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1700465] Re: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell --replace does not work: Can't initialize KMS backend:
  Could not get session ID: No such file or directory

Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  gnome-shell --replace does not work and reports:

  (gnome-shell:15848): mutter-WARNING **: Can't initialize KMS backend:
  Could not get session ID: No such file or directory

  
  (gnome-shell:16495): mutter-WARNING **: Can't initialize KMS backend: Could 
not get session ID: No such file or directory

  
  (gnome-shell:4910): mutter-WARNING **: Can't initialize KMS backend: Could 
not get session ID: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-25.29-generic 4.10.17
  Uname: Linux 4.10.0-25-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 26 09:03:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-07-10 (716 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-06-20 (5 days ago)

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

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

[Desktop-packages] [Bug 1700465] Re: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell --replace does not work: Can't initialize KMS backend:
  Could not get session ID: No such file or directory

Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  gnome-shell --replace does not work and reports:

  (gnome-shell:15848): mutter-WARNING **: Can't initialize KMS backend:
  Could not get session ID: No such file or directory

  
  (gnome-shell:16495): mutter-WARNING **: Can't initialize KMS backend: Could 
not get session ID: No such file or directory

  
  (gnome-shell:4910): mutter-WARNING **: Can't initialize KMS backend: Could 
not get session ID: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-25.29-generic 4.10.17
  Uname: Linux 4.10.0-25-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 26 09:03:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-07-10 (716 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-06-20 (5 days ago)

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[luca.mg]

@ Chris Rainey: no such a thing in my system.

@ PeterPall: the scanner works properly now, it only didn't on the very
first time using it. Weird, isn't it?

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819128] Re: Can't open exFAT-USB-Stick

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't open exFAT-USB-Stick

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I've got an exFAT-USB-Stick. If I'm plugging the stick it seems to be
  mounted (the mounted symbol appears in nautlius). But I'm not able to
  open the stick to open files or for writing new files to the stick.
  Just if I'm formatting the stick with GNOME Disks and mounting it
  directly after formatting about GNOME Disks I can open the stick.
  After unmounting the same problem appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 10:00:28 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'206'
   b'org.gnome.nautilus.window-state' b'geometry' b"'856x481+26+23'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-11-30 (97 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

[Tyler Singer-Clark]

Cool, I will try that!

As a heads up though, this sound quality is only after uninstalling and
reinstalling pulse audio and maybe something else (apologies for not
giving better details there, I didn't think to submit a bug until I ran
out of things to try). Before I did that, a voice recorded by the
microphone was impossible to understand (during a job interview we could
not hold a conversation and we had to switch to phone).

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
 

[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1583801

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 27867]

[Gingerbread-man-2]

*** Bug 1549613 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/27867

Title:
  Background color is always white, top banner is never displayed in
  Firefox

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

Bug description:
  Problem shows whatever the version of Epiphany (before and after today's 
upodate
  ie).

  Whatever the website I visit, the background colour is always white, and the
  logo/banner at the top of the page, is not displayed.

  I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and
  no yellow background.

  http://bugzilla.gnome.org/show_bug.cgi?id=121118:
  http://bugzilla.gnome.org/show_bug.cgi?id=121118

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Daniel van Vugt]

The attached file AudioDevicesInUse.txt suggests that 'audacity' is
stealing the hardware device from pulseaudio -- bypassing it.

If that is the issue then it's unfortunately not a bug. You need to be
sure that all audio software (including audacity) is configured to use
PulseAudio only, and not ALSA directly. Because the latter will prevent
all other audio (via PulseAudio) from working.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1827284] Re: No animation when GNOME Activities overview is opened

[Daniel van Vugt]

Strange. I do now have the animation in bionic today (gnome-shell
version 3.28.3+git20190124-0ubuntu18.04.2), providing I use the mouse
and not Super+A. So the "regression" I was thinking of isn't in bionic
with the Ubuntu Dock at least.

I will still bisect to see what/where things might have changed.

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

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

Title:
  [regression] No window spread animation

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  On Ubuntu 18.04.2, Xorg, Gnome version
  3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when
  you open the activities panel. When you close it, the animation shows
  up normally. The animation used to work, but it stopped by the end of
  April 2019. It doesn't seem to be a video driver issue, since it
  happens both when using Nvidia and Intel graphics. The issue persists
  after disabling all Gnome extensions.

  It's worth mentioning that the animation shows up if you access
  activities through the top right hot corner, but it doesn't if you
  press the button or the Windows key.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May  1 18:00:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-11 (141 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1827284] Re: No animation when GNOME Activities overview is opened

[Daniel van Vugt]

And the same bug is not in 19.10.

** Summary changed:

- No animation when GNOME Activities overview is opened
+ [regression] No window spread animation

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

Title:
  [regression] No window spread animation

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  On Ubuntu 18.04.2, Xorg, Gnome version
  3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when
  you open the activities panel. When you close it, the animation shows
  up normally. The animation used to work, but it stopped by the end of
  April 2019. It doesn't seem to be a video driver issue, since it
  happens both when using Nvidia and Intel graphics. The issue persists
  after disabling all Gnome extensions.

  It's worth mentioning that the animation shows up if you access
  activities through the top right hot corner, but it doesn't if you
  press the button or the Windows key.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May  1 18:00:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-11 (141 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[BloodyIron]

I have the issue in Disco... and have since I upgraded to it, as I
mentioned
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/35.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You 

[Desktop-packages] [Bug 1827284] Re: No animation when GNOME Activities overview is opened

[Daniel van Vugt]

Sorry, yes, I failed to notice the attached video.

The bug I was thinking of is different and I can still reproduce this
one.

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

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

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

Title:
  [regression] No window spread animation

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  On Ubuntu 18.04.2, Xorg, Gnome version
  3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when
  you open the activities panel. When you close it, the animation shows
  up normally. The animation used to work, but it stopped by the end of
  April 2019. It doesn't seem to be a video driver issue, since it
  happens both when using Nvidia and Intel graphics. The issue persists
  after disabling all Gnome extensions.

  It's worth mentioning that the animation shows up if you access
  activities through the top right hot corner, but it doesn't if you
  press the button or the Windows key.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May  1 18:00:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-11 (141 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I'm a little confused here.  What does audacity have to do with the fact
that there is no sound after a reboot?  Audacity happens to be running
now...perhaps that's why it's the only program using ALSA.  (Is ALSA
deprecated?)  But audacity does not start automatically at boot, so it
is irrelevant to the problem, which is that the sound device is not even
recognized until "alsa force-reload".

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Daniel van Vugt]

It appears 'audacity' is the exclusive user of /dev/snd/seq according to
your AudioDevicesInUse.txt.

Please try:
  1. Reconfiguring Audacity to use PulseAudio and not ALSA or OSS.
  2. Uninstalling 'audacity'.


** Summary changed:

- [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
+ [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Daniel van Vugt]

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

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

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #106834 => PulseAudio #193

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1828066] Re: ubuntu19.04 can not receive key input in virtualbox fullscreen mode

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1828066

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

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

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

Title:
  ubuntu19.04  can not receive key input in virtualbox fullscreen mode

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I install ubuntu19.04 in virtualbox6.0, virtualbox runs in linux,
  If I switch to fullScreen mode ubuntu19.04 can not receive key input anymore.

  I tried a lot of linux distribution, both have this bug.

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

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

[Desktop-packages] [Bug 1828136] [NEW] [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

Public bug reported:

After rebooting I have no sound.  My sound device doesn't show up at all
in the mixer.

Running "sudo alsa force-reload" corrects the problem, until the next
reboot.

This problem started in 18.10 and persists now in 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Tue May  7 21:50:22 2019
InstallationDate: Installed on 2014-04-19 (1844 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
Symptom_Jack: Grey SPDIF Out, Rear
Symptom_Type: No sound at all
Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10212-203
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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


** Tags: amd64 apport-bug disco

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

Title:
  [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1828016] Re: headphone remains mute at every restart. i have to unmute headphone using terminal-alsamixer hiting M

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1583801, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1583801
   No sound via headphones (headset) when Ubuntu boots with them plugged 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/1828016

Title:
  headphone remains mute at every restart. i have to unmute headphone
  using terminal-alsamixer hiting  M

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  At every restart i find headphone MUTE. I have to go to termial -
  alsamixer and UNMUTE headphone hiting  M key. then it is OK.But when I
  OFF the PC and start again it turns MUTE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jayantilal991 F pulseaudio
jayantilal   1985 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  7 15:11:58 2019
  InstallationDate: Installed on 2019-01-28 (99 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61WW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG23116-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Daniel van Vugt]

Also, since the bug was only in 3.30.0 and older (fixed in 3.30.1), that
makes it Invalid for cosmic and later. Because cosmic and later never
had the bug and never needed a fix.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

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

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Daniel van Vugt]

The fix is not released yet. At the top of the bug you will find "Bionic
In Progress".

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

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

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

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

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Rafael Nicolay]

Hi, guys! I saw that this problem has been fixed. My system was updated
today(apt-get update/upgrade), but I'm still facing the crashes. I'm not
familiar with this, but how do I force an update to benefit of this fix?
Sorry for this question.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

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

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Bug Watch Updater]

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

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly are included above under 'Extended test case'.

  = SRU apparmor 

[Desktop-packages] [Bug 1825972] Re: Remove libgnome-keyring, libgnomeui, linsmith from eoan

[Steve Langasek]

Removing packages from eoan:
linsmith 0.99.31-1 in eoan
linsmith 0.99.31-1 in eoan amd64
linsmith 0.99.31-1 in eoan arm64
linsmith 0.99.31-1 in eoan armhf
linsmith 0.99.31-1 in eoan i386
linsmith 0.99.31-1 in eoan ppc64el
linsmith 0.99.31-1 in eoan s390x
Comment: Depends on obsolete libgnomeui, removed from Debian testing; LP: 
#1825972, Debian bug #885742
1 package successfully removed.


** Changed in: linsmith (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove libgnome-keyring, libgnomeui, linsmith from eoan

Status in libgnome-keyring package in Ubuntu:
  Incomplete
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring

 
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnome-keyring/+bug/1825972/+subscriptions

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

[Desktop-packages] [Bug 1825972] Re: Remove libgnome-keyring, libgnomeui, linsmith from eoan

[Steve Langasek]

Removing packages from eoan:
libgnomeui 2.24.5-3.2 in eoan
libgnomeui-0 2.24.5-3.2 in eoan amd64
libgnomeui-0 2.24.5-3.2 in eoan arm64
libgnomeui-0 2.24.5-3.2 in eoan armhf
libgnomeui-0 2.24.5-3.2 in eoan i386
libgnomeui-0 2.24.5-3.2 in eoan ppc64el
libgnomeui-0 2.24.5-3.2 in eoan s390x
libgnomeui-0-dbg 2.24.5-3.2 in eoan amd64
libgnomeui-0-dbg 2.24.5-3.2 in eoan arm64
libgnomeui-0-dbg 2.24.5-3.2 in eoan armhf
libgnomeui-0-dbg 2.24.5-3.2 in eoan i386
libgnomeui-0-dbg 2.24.5-3.2 in eoan ppc64el
libgnomeui-0-dbg 2.24.5-3.2 in eoan s390x
libgnomeui-common 2.24.5-3.2 in eoan amd64
libgnomeui-common 2.24.5-3.2 in eoan arm64
libgnomeui-common 2.24.5-3.2 in eoan armhf
libgnomeui-common 2.24.5-3.2 in eoan i386
libgnomeui-common 2.24.5-3.2 in eoan ppc64el
libgnomeui-common 2.24.5-3.2 in eoan s390x
libgnomeui-dev 2.24.5-3.2 in eoan amd64
libgnomeui-dev 2.24.5-3.2 in eoan arm64
libgnomeui-dev 2.24.5-3.2 in eoan armhf
libgnomeui-dev 2.24.5-3.2 in eoan i386
libgnomeui-dev 2.24.5-3.2 in eoan ppc64el
libgnomeui-dev 2.24.5-3.2 in eoan s390x
libgnomeui-doc 2.24.5-3.2 in eoan amd64
libgnomeui-doc 2.24.5-3.2 in eoan arm64
libgnomeui-doc 2.24.5-3.2 in eoan armhf
libgnomeui-doc 2.24.5-3.2 in eoan i386
libgnomeui-doc 2.24.5-3.2 in eoan ppc64el
libgnomeui-doc 2.24.5-3.2 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, 
Debian bug #885767
1 package successfully removed.


** Changed in: libgnomeui (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove libgnome-keyring, libgnomeui, linsmith from eoan

Status in libgnome-keyring package in Ubuntu:
  Incomplete
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring

 
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnome-keyring/+bug/1825972/+subscriptions

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

[Desktop-packages] [Bug 1825972] Re: Remove libgnome-keyring, libgnomeui, linsmith from eoan

[Steve Langasek]

reverse-depends src:libgnome-keyring -b
Reverse-Build-Depends
=
* chromium-browser  (for libgnome-keyring-dev)
* libgnomeui(for libgnome-keyring-dev)

$

So we might want to deal with chromium first...?

** Changed in: libgnome-keyring (Ubuntu)
   Status: New => Incomplete

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

Title:
  Remove libgnome-keyring, libgnomeui, linsmith from eoan

Status in libgnome-keyring package in Ubuntu:
  Incomplete
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring

 
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnome-keyring/+bug/1825972/+subscriptions

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Launchpad Bug Tracker]

This bug was fixed in the package libselinux - 2.9-1

---
libselinux (2.9-1) experimental; urgency=medium

  [ Laurent Bigonville ]
  * New upstream release
- Bump libsepol1-dev build-dependency to >= 2.9 to match the release
  * debian/ruby.mk: Do not override RUBYLIBS anymore, upstream build system
seems to do the right thing now
  * debian/control: Bump Standards-Version to 4.3.0 (no further changes)
  * debian/watch: Adjust the URL
  * debian/selinux-utils.install: Install manpages in Russian
  * debian/libselinux1.symbols: Add new exported symbol
  * debian/patches/python_nodefs.patch: Do not FTBFS if we have missing
symbols because we are not linking against the libpython

  [ Michael Biebl ]
  * Build against PCRE2. (Closes: #913921, LP: #1792544)

 -- Laurent Bigonville   Sun, 17 Mar 2019 20:22:24
+0100

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

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

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

[Desktop-packages] [Bug 1828123] [NEW] File names are percent-encoded when connect to webdav server

[Tom Yang]

Public bug reported:

When I connected to a Webdav server set up by nginx using the default
file manager, some non-English characters in file and folder names are
displayed as percent-encoded(url-encoded).  For example,
"%E4%B8%8D%E5%AE%89%E4%B8%8E%E6%AC%B2%E6%9C%9B" is displayed instead of
"不安与欲望", and the " "(space) in a file name is displayed as "%20". Once I
copied those files to local disk, the file names are displayed
correctly.

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

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

Title:
  File names are percent-encoded when connect to webdav server

Status in nautilus package in Ubuntu:
  New

Bug description:
  When I connected to a Webdav server set up by nginx using the default
  file manager, some non-English characters in file and folder names are
  displayed as percent-encoded(url-encoded).  For example,
  "%E4%B8%8D%E5%AE%89%E4%B8%8E%E6%AC%B2%E6%9C%9B" is displayed instead
  of "不安与欲望", and the " "(space) in a file name is displayed as "%20".
  Once I copied those files to local disk, the file names are displayed
  correctly.

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

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

[Desktop-packages] [Bug 1827735] Re: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped"

[Bug Watch Updater]

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

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

Title:
  DBus/MPRIS2: Totem says it is "Paused" even the stream has ended
  "Stopped"

Status in Totem:
  New
Status in totem package in Ubuntu:
  Triaged

Bug description:
  Hello,

  Question 1:
  ===
  When asking status of Totem via DBus/MPRIS2, it says "Paused" even the song 
has ended. Shouldn't it return "Stopped" state.

  
  I am using a small bash-script to see the DBus-messages.

  $ ./debug1.sh

  org.mpris.MediaPlayer2.rhythmbox says: I AM PLAYING.
  Confirmed state is: (<'Playing'>,)
  -

  Then the song ends.

  org.mpris.MediaPlayer2.rhythmbox says: I AM PAUSED.
  Confirmed state is: (<'Paused'>,)
  

  Question 2:
  ===
  GNOME's Music player is "org.gnome.Music".

  GNOME's Video player is: "org.mpris.MediaPlayer2.totem"

  Why this difference?

  I like both products.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  4 19:24:02 2019
  InstallationDate: Installed on 2019-03-06 (58 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[Bug Watch Updater]

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

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[Launchpad Bug Tracker]

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

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

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1828108] Re: GNOME default to a document font not installed by Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 19.04.4

---
ubuntu-settings (19.04.4) eoan; urgency=medium

  * ubuntu-settings.gsettings-override:
- set the document font to 'Sans 11' for Ubuntu, the GNOME default
  changed to Cantarell which is not installed for us (lp: #1828108)

 -- Sebastien Bacher   Tue, 07 May 2019 20:19:36
+0200

** Changed in: ubuntu-settings (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  GNOME default to a document font not installed by Ubuntu

Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
  font is not installed in Ubuntu so a fallback font is used instead.

  * Test case
  Install gnome-tweaks and look at the document font, it should be 'Sans 11' 
and not 'undefined'

  * Regression potential
  It's just changing the default value to be what it was before, the impact 
should be low (the UI is going to look different in place where the fallback 
was used but that's what the fix is about)

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

regression fixed in 1.10.0-1~ubuntu18.04.2

however please note now that ModemManager is started by default with
filter-policy=strict in order for MM to see Bluetooth modems you need a
udev rule like such:

ACTION!="add|change|move", GOTO="mm_whitelist_internal_modem_end"
#ACTION=="add", KERNEL=="rfcomm0", ENV{ID_MM_DEVICE_PROCESS}="1"
#ATTRS{idVendor}=="8087", ATTRS{idProduct}=="07dc", 
ENV{ID_MM_DEVICE_PROCESS}="1"
ACTION=="add|change|move", KERNEL=="rfcomm*", DEVPATH!="*/virtual/*", 
SUBSYSTEM=="tty", ENV{ID_MM_DEVICE_PROCESS}="1"
LABEL="mm_whitelist_internal_modem_end"

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1823459] Re: guile-2.2 ftbfs in disco (arm64 only)

[Launchpad Bug Tracker]

This bug was fixed in the package guile-2.2 - 2.2.4+1-1ubuntu3.1

---
guile-2.2 (2.2.4+1-1ubuntu3.1) eoan; urgency=medium

  * debian/patches/git_hook_test.patch
- Fix gc.test "after-gc-hook gets called" failures, it was leading
  to an arm64 build failure on disco, thanks andyrock! (lp: #1823459)

 -- Sebastien Bacher   Tue, 07 May 2019 11:34:07
+0200

** Changed in: guile-2.2 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  guile-2.2 ftbfs in disco (arm64 only)

Status in guile-2.2 package in Ubuntu:
  Fix Released
Status in guile-2.2 source package in Disco:
  In Progress

Bug description:
  https://launchpadlibrarian.net/417969614/buildlog_ubuntu-disco-
  arm64.guile-2.2_2.2.4+1-1ubuntu2_BUILDING.txt.gz

  Totals for this test run:
  passes: 41515
  failures:   1
  unexpected passes:  0
  expected failures:  10
  unresolved test cases:  577
  untested test cases:1
  unsupported test cases: 1
  errors: 0

  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  ;;; SSAX warning: Skipping PI: xml

  ;;; SSAX warning: Skipping PI: PI

  ;;; SSAX warning: Skipping PI: PI1

  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: (
   Warning:  Internal DTD subset is not currently handled )
  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: Skipping PI: pi

  ;;; SSAX warning: DOCTYPE DECL T system1 found and skipped
  WARNING: (test-suite sxml-xpath): imported module (sxml xpath) overrides core 
binding `filter'
  FAIL: check-guile
  ==
  1 of 1 test failed
  Please report to bug-gu...@gnu.org
  ==
  make[4]: *** [Makefile:1956: check-TESTS] Error 1
  make[4]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[3]: *** [Makefile:2241: check-am] Error 2
  make[3]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[2]: *** [Makefile:1856: check-recursive] Error 1
  make[2]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[1]: *** [Makefile:2243: check] Error 2
  make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1823459/+subscriptions

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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Olivier Tilloy]

I've toyed with an unpacked example extension that talks to a native
host connector (a simple python script that listens to messages and
echoes all it receives).

This works with the following caveats:

 - the connector has to be installed under
$SNAP_USER_DATA/.config/chromium/NativeMessagingHosts/

 - the path to the connector in the manifest needs to be an absolute path (as 
documented at https://developers.chrome.com/extensions/nativeMessaging), e.g.:
"path": 
"/home/osomon/snap/chromium/current/.config/chromium/NativeMessagingHosts/native-messaging-example-host"

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

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

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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Olivier Tilloy]

chrome-gnome-shell wouldn't work like that unmodified, because the
connector has external dependencies (it's a python3 script that imports
GLib and Gio).

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

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

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

[Desktop-packages] [Bug 1826633] Re: default document text font on Disco is None

[Sebastien Bacher]

Thanks Adam, indeed that's due to GNOME changing to cantarell in 3.31, fixed 
now in 
https://launchpad.net/ubuntu/+source/ubuntu-settings/19.04.4
SRU uploaded as well

** Package changed: gnome-settings-daemon (Ubuntu) => gsettings-desktop-
schemas (Ubuntu)

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Importance: Undecided => Low

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Fix Released

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

Title:
  default document text font on Disco is None

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 19.04 (Disco), the default Document Text font after
  installation is None.  You can see this if you run gnome-tweaks and
  select Fonts in the left sidebar.

  As one consequence of this, messages in Geary are displayed in a serif
  font by default, which doesn't look ideal.  Changing the font to Sans
  Regular fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1826633/+subscriptions

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

[Desktop-packages] [Bug 1828108] [NEW] GNOME default to a document font not installed by Ubuntu

[Sebastien Bacher]

Public bug reported:

* Impact

The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
font is not installed in Ubuntu so a fallback font is used instead.

* Test case
Install gnome-tweaks and look at the document font, it should be 'Sans 11' and 
not 'undefined'

* Regression potential
It's just changing the default value to be what it was before, the impact 
should be low (the UI is going to look different in place where the fallback 
was used but that's what the fix is about)

** Affects: ubuntu-settings (Ubuntu)
 Importance: Low
 Status: In Progress

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => In Progress

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

Title:
  GNOME default to a document font not installed by Ubuntu

Status in ubuntu-settings package in Ubuntu:
  In Progress

Bug description:
  * Impact

  The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
  font is not installed in Ubuntu so a fallback font is used instead.

  * Test case
  Install gnome-tweaks and look at the document font, it should be 'Sans 11' 
and not 'undefined'

  * Regression potential
  It's just changing the default value to be what it was before, the impact 
should be low (the UI is going to look different in place where the fallback 
was used but that's what the fix is about)

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

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

[Desktop-packages] [Bug 1827735] Re: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped"

[Sebastien Bacher]

Thank you for your bug report, indeed that's an issue, I've reported it
upstream on https://gitlab.gnome.org/GNOME/totem/issues/326

** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #326
   https://gitlab.gnome.org/GNOME/totem/issues/326

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

** Changed in: totem (Ubuntu)
   Status: New => Triaged

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

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

Title:
  DBus/MPRIS2: Totem says it is "Paused" even the stream has ended
  "Stopped"

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  Triaged

Bug description:
  Hello,

  Question 1:
  ===
  When asking status of Totem via DBus/MPRIS2, it says "Paused" even the song 
has ended. Shouldn't it return "Stopped" state.

  
  I am using a small bash-script to see the DBus-messages.

  $ ./debug1.sh

  org.mpris.MediaPlayer2.rhythmbox says: I AM PLAYING.
  Confirmed state is: (<'Playing'>,)
  -

  Then the song ends.

  org.mpris.MediaPlayer2.rhythmbox says: I AM PAUSED.
  Confirmed state is: (<'Paused'>,)
  

  Question 2:
  ===
  GNOME's Music player is "org.gnome.Music".

  GNOME's Video player is: "org.mpris.MediaPlayer2.totem"

  Why this difference?

  I like both products.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  4 19:24:02 2019
  InstallationDate: Installed on 2019-03-06 (58 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[PeterPall]

Then the answer is simple: extend the udev file with the usb if of the
scanner without firmware so use will give you write access to this
device, too. Once that is done sane can upload the firmware, the scanner
can identify itself as the model you have bought and you can scan. Seems
like we should collect the Epson usb IDs somewhere...

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Chris Rainey]

@luca.mg: have you checked for firmware updates? My Brother DCP-L2550DW can
update from the web interface in the system tools/administration tab and
there have been a few updates in the last year.


On Tue, May 7, 2019 at 2:45 PM luca.mg  wrote:

> @ PeterPall: regarding the Epson scanner, yes it could be the firmware
> upload, the first root scan took time, I thought it was the scanner
> warming up longer than usual and not catching up, but I allowed time and
> it finally went through, so You may very well be right. I did not run
> lsusb -v, just a plain lsub, but before the root scan the scanner was
> detected as an epkowa driven unknown model, after the root scan it is
> detected with the proper model name.
>
> @ Chris Rainey: regarding the Brother MFP, I can confirm that I ran the
> installer script and not the available deb packages.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728012
>
> Title:
>   Many 3rd party scanner drivers are broken by a sane change
>
> Status in sane-backends package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Many scanners can no more be used since sane has changed something:
>   The 3rd-party plug-in the vendor provides as .deb package will still
>   install. But the scanner is no more recognized.
>
>   Scanners that are affected are(besides others):
>- Epson Perfection V10
>- Epson Perfection V1000
>- Epson WorkForce GT-1500
>- Brother MFC-8510DN
>- Epson Perfection V33
>
>   It is to note that the probability that the scanner manufacturers fix
>   things others broke is below 100%.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: libsane1 1.0.27-1~experimental2ubuntu2
>   Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
>   ApportVersion: 2.20.7-0ubuntu3.1
>   Architecture: amd64
>   Date: Fri Oct 27 12:35:52 2017
>   EcryptfsInUse: Yes
>   SourcePackage: sane-backends
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
>

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1828088] Re: Firefox add-on intermediate signing fix update missing (66.0.4)

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1827727
   All plugins disabled due to expired cert

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

Title:
  Firefox add-on intermediate signing fix update missing (66.0.4)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  This patch from upstream does not appear to be applied, or in the launchpad 
tracker.
  
https://support.mozilla.org/en-US/kb/add-ons-disabled-or-fail-to-install-firefox

  Also described here:
  https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox

  Please update this package.

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

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

[Desktop-packages] [Bug 1828107] [NEW] gvfs can't list shares from smb servers that disabled SMB1

[Andreas Hasenack]

Public bug reported:

After bug #1778322 is fixed (just needs a gvfs rebuild with newer
samba), samba machines will start to show up again in the "windows
network" tab in nautilus. But if a server has disabled the SMB1
protocol, nautilus will show an error when that server is clicked on,
instead of showing the shares list.

Even with SMB1 disabled, it should still be technically possible to get
a share list, since smbclient can do it:

andreas@nsnx:~$ nmblookup -A 192.168.122.101
Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

MAC Address = 00-00-00-00-00-00

andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available

andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1
WARNING: The "syslog" option is deprecated
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2
WARNING: The "syslog" option is deprecated
Try "help" to get a list of possible commands.
smb: \> dir
  .   D0  Fri May  3 18:16:38 2019
  ..  D0  Fri May  3 18:15:24 2019
  hello.txt   N   21  Fri May  3 18:16:12 2019
  hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

20509264 blocks of size 1024. 13121800 blocks available

** Affects: gvfs
 Importance: Unknown
 Status: Unknown

** Affects: gvfs (Ubuntu)
 Importance: Medium
 Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #307
   https://gitlab.gnome.org/GNOME/gvfs/issues/307

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

** Summary changed:

- gvfs can't browse smb servers that disabled SMB1
+ gvfs can't list shares from smb servers that disabled SMB1

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

I filed https://bugs.launchpad.net/gvfs/+bug/1828107 for the remaining
issue of connecting to machines in the windows network tab that have
disabled SMB1. Note that a connection made specifically to the
machine/ip still works (smb:///)

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this 

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

I found an upstream issue about not being able to get a share list from
a machine that has SMB1 disabled:
https://gitlab.gnome.org/GNOME/gvfs/issues/307


** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #307
   https://gitlab.gnome.org/GNOME/gvfs/issues/307

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb 

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

yparitcher, first, thanks for reporting bug 1828102, we need this
separate bug as Cosmic and Disco originally came with ModemManager 1.10
and so did not suffer the bug treated here, only the regression which
you have found. Eoan I have already treated here as the SRU team
requires that the issues which are fixed by an SRU are also fixed in the
current development cycle.

yparitcher, please test the new modemmanager package in bionic-proposed
on your Bionic systems to see whether the regression is actually fixed
and report back here. Thanks.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[luca.mg]

@ PeterPall: regarding the Epson scanner, yes it could be the firmware
upload, the first root scan took time, I thought it was the scanner
warming up longer than usual and not catching up, but I allowed time and
it finally went through, so You may very well be right. I did not run
lsusb -v, just a plain lsub, but before the root scan the scanner was
detected as an epkowa driven unknown model, after the root scan it is
detected with the proper model name.

@ Chris Rainey: regarding the Brother MFP, I can confirm that I ran the
installer script and not the available deb packages.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

Alex Tu, please test the new packages in bionic-proposed whether they
correctly support the modems for which you asked for support for.
Thanks.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1828102] Re: regression in modemmanager

[Till Kamppeter]

** Also affects: modemmanager (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: modemmanager (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: modemmanager (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: modemmanager (Ubuntu Eoan)
   Status: New => Fix Released

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

Title:
  regression in modemmanager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Cosmic:
  New
Status in modemmanager source package in Disco:
  New
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

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

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

[Desktop-packages] [Bug 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop

[Alexandre Forte]

I think it's a bug, because all laptops I've ever seen show "fully
charged" instead of "not charging" when they hit 100% of the battery.
And there's some other strange behavior, like the Gnome indicator
eventually being stuck at "Estimating" and, sometimes, if you disconnect
the power plug while at 100% and connect it again after that, Upower
shows "discharging", as if it didn't recognize the power supply again,
which is only fixed by a reboot.

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

Title:
  UPower and battery indicator show wrong information on fully charged
  ASUS Vivobook X510UR laptop

Status in upower package in Ubuntu:
  New

Bug description:
  When the ASUS Vivobook X510UR laptop is completely charged, the
  correct information is displayed on Windows. However, Ubuntu 18.04.2
  LTS is unable to detect the true battery state. The GNOME battery
  indicator usually shows "Estimating..." or "Not charging", when the
  battery is at 100%.

  If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower
  -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you
  get:

native-path:  BAT0
vendor:   ASUSTeK
model:ASUS Battery
power supply: yes
updated:  sex 03 mai 2019 14:33:43 -03 (4 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  39,191 Wh
  energy-empty:0 Wh
  energy-full: 39,26 Wh
  energy-full-design:  42,082 Wh
  energy-rate: 12,453 W
  voltage: 11,52 V
  percentage:  100%
  capacity:93,294%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1556904821100,000 discharging
History (rate):
  155690482112,453  discharging
  15569048183,744   discharging

  The "state" should be "fully-charged", but instead it is "pending-
  charge".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: upower 0.99.7-2ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May  3 14:34:14 2019
  InstallationDate: Installed on 2018-12-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

added bug for cosmic & disco
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install

[whitefawn]

Same issue on 18.04.
Can PGP server present a problem for users outside of USA?

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

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

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

[Desktop-packages] [Bug 1828102] [NEW] regression in modemmanager

[yparitcher]

Public bug reported:

ModemManager disconnects after ~30 sec

caused by a typo in 1.8

see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 
and
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
for details

needs a SRU for cosmic and dingo

patch attached

yechiel

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

** Patch added: "bugfix.diff"
   
https://bugs.launchpad.net/bugs/1828102/+attachment/5262140/+files/bugfix.diff

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

Title:
  regression in modemmanager

Status in modemmanager package in Ubuntu:
  New

Bug description:
  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

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

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

[Desktop-packages] [Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install

[Launchpad Bug Tracker]

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

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

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

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

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

[Desktop-packages] [Bug 1822590] Re: Found storing user fingerprints without encryption

[Seth Arnold]

I'll include as a comment my reply to an email from the reporter:

Hello,

Note that the Ubuntu security team considers fingerprints to be akin to
usernames, rather than passwords. They cannot be changed, they are left on
thousands of objects daily, and repeated demonstrations of sensors being
'fooled' by artificial constructions from photographs etc basically mean
fingerprints are not worth much as authentication tokens.

In the Main Inclusion Request review for fprintd and libfprint, we
included:

It's important to note that security team considers fingerprints to
be akin to usernames and not passwords. Any potential issues with
this tool will be treated with this threat model in mind.

-- https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1745455

Under this threat model, disclosure of a fingerprint is not a
vulnerability.

Perhaps the fprintd or libfprintd authors will see things differently,
but I suspect most security practitioners have decided that fingerprints
are identifiers, not authenticators.

Thanks



** Changed in: apparmor (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Found storing user fingerprints without encryption

Status in fprintd:
  New
Status in apparmor package in Ubuntu:
  Won't Fix
Status in fprintd package in Ubuntu:
  Triaged
Status in Debian:
  Unknown

Bug description:
  Dear all,

  I would like to report a new issue as follows.
  ‘fprintd’ saves a fingerprint data, ISO/IEC 19794-2 formatted, to a file on 
the host without any encryption.
  Though fprintd generates fingerprint image with root permission for 
protecting the file from attackers, it is not of itself sufficient.
  It is well known threat model that a formatted fingerprint data can be 
restored to original image about a decade ago.
  [1-4] are presented to create sophisticated and natural-looking fingerprints 
only from the numerical template data format as defined in ISO/IEC 19794-2.
  They also successfully evaluated these approaches against a number of 
undisclosed state-of-the-art algorithms and the NIST Fingerprint Image Software.

  We need improvements of those issues.

  [1] R. Cappelli et al., “Fingerprint Image Reconstruction from Standard 
Templates”, IEEE Trans. on Pattern Analysis and Machine Intelligence, vol.29, 
no.9, pp.1489-1503, 2007.
  [2] A. Ross et al., “From template to image: Reconstructing fingerprints from 
minutiae points”, IEEE Trans on Pattern Analysis and Machine Intelligence, 
vol.29, no.4, pp.544-560, 2007.
  [3] R. Cappelli et al., “Can Fingerprints be reconstructed from ISO 
Templates?”, IEEE ICARCV 2006.
  [4] J. Feng et al., “Fingerprint Reconstruction: From Minutiae to Phase”, 
IEEE Trans on Pattern Analysis and Machine Intelligence, vol.33, no.2, 
pp.209-223, 2011.

  Sincerely,
  Seong-Joong Kim

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

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

[Desktop-packages] [Bug 1828088] Re: Firefox add-on intermediate signing fix update missing (66.0.4)

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox add-on intermediate signing fix update missing (66.0.4)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  This patch from upstream does not appear to be applied, or in the launchpad 
tracker.
  
https://support.mozilla.org/en-US/kb/add-ons-disabled-or-fail-to-install-firefox

  Also described here:
  https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox

  Please update this package.

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

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

[Desktop-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

[Andrew Keats]

I was on Bionic Beaver and my '.desktop' Desktop Entry files were
working but after an upgrade to Disco Dingo they just launch gedit.

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

Title:
  xdg-open *.desktop opens text editor

Status in GLib:
  New
Status in gvfs:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

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

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

[Desktop-packages] [Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install

[Mauro Gaspari]

I re-created the same issue on another install, this time Ubuntu-Budgie 19.04.
Same issue happened, same solution fixed it.

Detailed steps I followed to fix the issue:

1. Go to https://developers.hp.com/hp-linux-imaging-and-printing/gethplip .
2. Download latest version for Ubuntu . At the time of writing latest version 
is 3.19.3 .
3. Download hplip-3.19.3.run file, remember to change permissions to make it 
executable.
4. Remove hplip installed by your distribution repositories.
5. Download hplip-3.19.3-plugin.run and hplip-3.19.3-plugin.run.asc from 
https://developers.hp.com/hp-linux-imaging-and-printing/plugins .
6. run hplip-3.19.3.run in a terminal, follow instructions on screen. 
7. During printer setup process, when asked, always use interactive mode 
instead of gui. When asked for plugin, select path instead of download from 
server, provide path including full name of hplip-3.19.3-plugin.run .

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in hplip package in Ubuntu:
  New

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

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

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

[Desktop-packages] [Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...

[Iain Lane]

I'm going to upload this to bionic before it's fixed in disco/eoan.
There we're giving upstream a couple of days to release 3.32.2 which
will contain this. SRU person, If you happen to review this before then,
hope that's OK. :-)

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

Title:
  Shell dialog messages are truncated and ellipsized...

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Disco:
  In Progress

Bug description:
  [ Impact ]

  When plugging in a Thunderbolt device, under certain conditions, there
  could be a pop-up window asking for authentication from the user.

  In the dialog box, the prompt text is truncated. Please refer to
  attached screen shot for more details.

  The issue can be found in the gnome-control-center package for bionic:
  1:3.28.2-0ubuntu0.18.04.2
  1:3.28.1-0ubuntu1

  However, the issue is confirmed to be gone in latest such package for Cosmic:
  1:3.30.2-1ubuntu0.18.10.1

  [ Test case ]

  In a terminal run:
   $ boltctl enroll foo

  Text in the auth message should not be cut, using both Ubuntu theme,
  Yaru or default gnome-shell

  [ Regression Potential ]

  The dialogs text is wrapped when not needed, or dialog text isn't
  ellipsized when requested.

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

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

[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

[Brian Murray]

The plymouth package hook is using apport's
"attach_root_command_outputs" function that same function is also used
by the following package hooks: lightdm, shim-signed, ubuntu-release-
upgrader, update-manager, synaptic, upgrade-system and all the xorg
hooks. So it may be worth working around this is apport.

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  Triaged

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Stuart Jaggers]

In isolation I don't prefer one icon set to the other, but I agree that
Breeze is a better fit for the desktop style, so I would be +1.

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

Disco shouldn't have this bug. It (gvfs) will have issues connecting to
smb servers that have disabled SMB1, just like bionic and everything in
between.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  

[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop

[Treviño]

** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  when you have "world clocks" configured (e.g. from the Gnome Clocks
  application), Gnome Shell crashes on login, resulting in a login loop

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

Bug description:
  Configure some “world clocks” in Gnome Clocks (or maybe using some
  other tool).

  Expected behaviour (how it worked in cosmic & before): Gnome Shell
  shows the time for the cities you configured when you click on the
  date at the top centre.

  What happens: Gnome Shell crashes just after login, creating a “login
  loop” where the user is locked out of their computer.

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

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

[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop

[Treviño]

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gnome-shell (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1827953

Title:
  when you have "world clocks" configured (e.g. from the Gnome Clocks
  application), Gnome Shell crashes on login, resulting in a login loop

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

Bug description:
  Configure some “world clocks” in Gnome Clocks (or maybe using some
  other tool).

  Expected behaviour (how it worked in cosmic & before): Gnome Shell
  shows the time for the cities you configured when you click on the
  date at the top centre.

  What happens: Gnome Shell crashes just after login, creating a “login
  loop” where the user is locked out of their computer.

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

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

[Desktop-packages] [Bug 1828088] [NEW] Firefox add-on intermediate signing fix update missing (66.0.4)

[Paul Oppenheim]

Public bug reported:

This patch from upstream does not appear to be applied, or in the launchpad 
tracker.
https://support.mozilla.org/en-US/kb/add-ons-disabled-or-fail-to-install-firefox

Also described here:
https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox

Please update this package.

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

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

Title:
  Firefox add-on intermediate signing fix update missing (66.0.4)

Status in firefox package in Ubuntu:
  New

Bug description:
  This patch from upstream does not appear to be applied, or in the launchpad 
tracker.
  
https://support.mozilla.org/en-US/kb/add-ons-disabled-or-fail-to-install-firefox

  Also described here:
  https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox

  Please update this package.

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

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

[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/366944

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

Title:
  when you have "world clocks" configured (e.g. from the Gnome Clocks
  application), Gnome Shell crashes on login, resulting in a login loop

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

Bug description:
  Configure some “world clocks” in Gnome Clocks (or maybe using some
  other tool).

  Expected behaviour (how it worked in cosmic & before): Gnome Shell
  shows the time for the cities you configured when you click on the
  date at the top centre.

  What happens: Gnome Shell crashes just after login, creating a “login
  loop” where the user is locked out of their computer.

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

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

[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop

[Treviño]

** Changed in: gnome-shell (Ubuntu Disco)
   Status: New => In Progress

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

** Changed in: gnome-shell (Ubuntu Disco)
 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1827953

Title:
  when you have "world clocks" configured (e.g. from the Gnome Clocks
  application), Gnome Shell crashes on login, resulting in a login loop

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

Bug description:
  Configure some “world clocks” in Gnome Clocks (or maybe using some
  other tool).

  Expected behaviour (how it worked in cosmic & before): Gnome Shell
  shows the time for the cities you configured when you click on the
  date at the top centre.

  What happens: Gnome Shell crashes just after login, creating a “login
  loop” where the user is locked out of their computer.

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

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

[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/366941

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

Title:
  when you have "world clocks" configured (e.g. from the Gnome Clocks
  application), Gnome Shell crashes on login, resulting in a login loop

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

Bug description:
  Configure some “world clocks” in Gnome Clocks (or maybe using some
  other tool).

  Expected behaviour (how it worked in cosmic & before): Gnome Shell
  shows the time for the cities you configured when you click on the
  date at the top centre.

  What happens: Gnome Shell crashes just after login, creating a “login
  loop” where the user is locked out of their computer.

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Łukasz Zemczak]

Hello Till, or anyone else affected,

Accepted modemmanager into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.10.0-1~ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: modemmanager (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1794033]

[Oss-linuxpf]

I got how to reproduce.

Cached memory grows big by reading many files and free RAM becomes empty.
In this situation (repeat release and allocate caches frequently), drawing 
process faces this problem.

Does conflict of memory cause this problem?

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Confirmed

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1827727] Re: All plugins disabled due to expired cert

[eo]

While it may be true the "studies" feature which enabled the temporary
fix is turned on by default it is a highly contentious feature which
many security minded users (isn't that what most firefox users are) have
disabled. Yes, it can be turned back on to get the "fix" but I choose
not to compromise one form of security to regain another that was lost
due to an unfortunate mozilla error. Just the same as I and many others
choose to use LTS and the standard release system to minimize risk and
maximize stability. I hope the maintainers can understand this.

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Launchpad Bug Tracker]

This bug was fixed in the package modemmanager - 1.10.0-1ubuntu1

---
modemmanager (1.10.0-1ubuntu1) eoan; urgency=medium

  * debian/patches/error-propagation-fix.patch: mm-broadband-modem: Fix error
propagation in CDMA service status (LP: #1819615, Upstream Issue #119).

 -- Till Kamppeter   Mon, 06 May 2019 15:40:29
+0200

** Changed in: modemmanager (Ubuntu Eoan)
   Status: In Progress => Fix Released

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  In Progress
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1822590] Re: Found storing user fingerprints without encryption

[Salvatore Bonaccorso]

** Bug watch added: Debian Bug tracker #926749
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926749

** Also affects: apparmor (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926749
   Importance: Unknown
   Status: Unknown

** No longer affects: apparmor (Debian)

** Also affects: debian via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926749
   Importance: Unknown
   Status: Unknown

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

Title:
  Found storing user fingerprints without encryption

Status in fprintd:
  New
Status in apparmor package in Ubuntu:
  New
Status in fprintd package in Ubuntu:
  Triaged
Status in Debian:
  Unknown

Bug description:
  Dear all,

  I would like to report a new issue as follows.
  ‘fprintd’ saves a fingerprint data, ISO/IEC 19794-2 formatted, to a file on 
the host without any encryption.
  Though fprintd generates fingerprint image with root permission for 
protecting the file from attackers, it is not of itself sufficient.
  It is well known threat model that a formatted fingerprint data can be 
restored to original image about a decade ago.
  [1-4] are presented to create sophisticated and natural-looking fingerprints 
only from the numerical template data format as defined in ISO/IEC 19794-2.
  They also successfully evaluated these approaches against a number of 
undisclosed state-of-the-art algorithms and the NIST Fingerprint Image Software.

  We need improvements of those issues.

  [1] R. Cappelli et al., “Fingerprint Image Reconstruction from Standard 
Templates”, IEEE Trans. on Pattern Analysis and Machine Intelligence, vol.29, 
no.9, pp.1489-1503, 2007.
  [2] A. Ross et al., “From template to image: Reconstructing fingerprints from 
minutiae points”, IEEE Trans on Pattern Analysis and Machine Intelligence, 
vol.29, no.4, pp.544-560, 2007.
  [3] R. Cappelli et al., “Can Fingerprints be reconstructed from ISO 
Templates?”, IEEE ICARCV 2006.
  [4] J. Feng et al., “Fingerprint Reconstruction: From Minutiae to Phase”, 
IEEE Trans on Pattern Analysis and Machine Intelligence, vol.33, no.2, 
pp.209-223, 2011.

  Sincerely,
  Seong-Joong Kim

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[BloodyIron]

Um, what about Disco Dingo? 19.04, still having the bug.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  

[Desktop-packages] [Bug 1825447] Re: Indicators Scroll events are not emitted in 19.04

[Lonnie Lee Best]

https://bugs.launchpad.net/radiotray/+bug/1828069

Screenshot here:
https://github.com/ebruck/radiotray-ng/issues/112

** Bug watch added: github.com/ebruck/radiotray-ng/issues #112
   https://github.com/ebruck/radiotray-ng/issues/112

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

Title:
  Indicators Scroll events are not emitted in 19.04

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Disco:
  In Progress

Bug description:
  [ Impact ]

  Scroll events aren't delivered to app-indicators

  [ Test case ]
   - Run an indicator that supports scroll events (i.e. radiotray-ng or run
 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
 with gjs
   - Scroll events should be delivered

  [ Regression potential ]

  Scroll events over other shell actors aren't working (i.e. changing volume 
with scroll)
   

  ---

  It appears the code used in the 19.04 packaging of the appindicator is
  from master and not the tagged ubuntu-19.04 commit from the ubuntu
  branch. The master branch is not delivering scroll events, which stops
  my application (radiotray-ng) from being able to adjust its volume
  levels.

  I've swapped out the code under /usr/share/gnome-shell/extensions
  /ubuntu-appindicat...@ubuntu.com/ with the ubuntu branch and scrolling
  on an indicator icon works again.

  I've filed an issue on github as well.

  https://github.com/ubuntu/gnome-shell-extension-
  appindicator/issues/169

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Will Cooke]

Hm.  Tricky.  I quite like the straightforwardness of the Breeze icons.
But I also tend to use the "feel" of the icons to navigate quickly, and
that comes from colour as well as shape.  So I don't really have a
proper answer at this point.  I will loop in Design for more informed
feedback.

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Carlo Lobrano]

On one side, breeze icons might look a bit colder, but they're actually
graphically closer to yaru's symbolic icons

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

Re: [Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Marcus Tomlinson]

** Attachment added: "Base-After.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262118/+files/Base-After.png

** Attachment added: "Base-Before.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262119/+files/Base-Before.png

** Attachment added: "Calc-After.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262120/+files/Calc-After.png

** Attachment added: "Calc-Before.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262121/+files/Calc-Before.png

** Attachment added: "Draw-After.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262122/+files/Draw-After.png

** Attachment added: "Draw-Before.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262123/+files/Draw-Before.png

** Attachment added: "Impress-After.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262124/+files/Impress-After.png

** Attachment added: "Impress-Before.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262125/+files/Impress-Before.png

** Attachment added: "Math-After.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262126/+files/Math-After.png

** Attachment added: "Math-Before.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5262127/+files/Math-Before.png

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode

[Ufos92]

Ubuntu devs are still dreaming that the OS will conquer "Chromebook"
world, and will be running on tablets as well. Obviously, if a user
turns of wifi, it's not because they most likely docked their notebook,
no, it's because they're on an airplane with their tablet and need the
airplane mode.

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

Title:
  Turning off WiFi enables Airplane mode

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

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Marcus Tomlinson]

** Attachment added: "Before.png"
   https://bugs.launchpad.net/bugs/1827948/+attachment/5262116/+files/Before.png

** Attachment added: "After.png"
   https://bugs.launchpad.net/bugs/1827948/+attachment/5262117/+files/After.png

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1828066] [NEW] ubuntu19.04 can not receive key input in virtualbox fullscreen mode

[widon1104]

Public bug reported:

I install ubuntu19.04 in virtualbox6.0, virtualbox runs in linux,
If I switch to fullScreen mode ubuntu19.04 can not receive key input anymore.

I tried a lot of linux distribution, both have this bug.

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

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

Title:
  ubuntu19.04  can not receive key input in virtualbox fullscreen mode

Status in libinput package in Ubuntu:
  New

Bug description:
  I install ubuntu19.04 in virtualbox6.0, virtualbox runs in linux,
  If I switch to fullScreen mode ubuntu19.04 can not receive key input anymore.

  I tried a lot of linux distribution, both have this bug.

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

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

Re: [Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Chris Rainey]

Just a reminder to those of us using Brother DCP or MFP's: I repeatedly
find that the only way to properly install the printer and scanner drivers
is to use the "Installer Script"(i.e. 09/13/2018
(2.2.1-1)) provided on the model downloads page(see below) and to follow
the directions given _explicitly_(to-the-letter, no exceptions)! I've tried
to install a recently updated scanner driver(i.e. 01/21/2019
(0.4.7-1)) by itself as an upgrade to the currently installed one and even
re-ran the setup command(i.e. Brsaneconfig4 -a name=(name your device)
model=(model name) ip=xx.xx.xx.xx) for my network(Wi-Fi) DCP-L2550DW, but
it does not work that way. I can't stress, enough, the apparent need to
re-run the "Installer Script", exactly as shown--below, in order for
everything to work!


How to Install

Step1. Download the tool.(linux-brprinter-installer-*.*.*-*.gz)

The tool will be downloaded into the default "Download" directory.
(The directory location varies depending on your Linux distribution.)
e.g. /home/(LoginName)/Download

Step2. Open a terminal window.

Step3. Go to the directory you downloaded the file to in the last step. By
using the cd command.

e.g. cd Downloads

Step4. Enter this command to extract the downloaded file:

*Command: gunzip linux-brprinter-installer-*.*.*-*.gz*

e.g. gunzip linux-brprinter-installer-2.1.1-1.gz

Step5. Get superuser authorization with the "*su*" command or "*sudo su*"
command.

Step6. Run the tool:

*Command: bash linux-brprinter-installer-*.*.*-* Brother machine name *
e.g. bash linux-brprinter-installer-2.1.1-1 MFC-J880DW

Step7. The driver installation will start. Follow the installation screen
directions.


 When you see the message "Will you specify the DeviceURI ?",

 For USB Users: Choose N(No)
 For Network Users: Choose Y(Yes) and DeviceURI number.

The install process may take some time. Please wait until it is
complete.

On Tue, May 7, 2019 at 7:41 AM PeterPall <1728...@bugs.launchpad.net>
wrote:

> Then perhaps uploading the firmware to the scanner can only be done as
> root, for some reason.
> Does the output of susb -v change after scanning for the first time?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728012
>
> Title:
>   Many 3rd party scanner drivers are broken by a sane change
>
> Status in sane-backends package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Many scanners can no more be used since sane has changed something:
>   The 3rd-party plug-in the vendor provides as .deb package will still
>   install. But the scanner is no more recognized.
>
>   Scanners that are affected are(besides others):
>- Epson Perfection V10
>- Epson Perfection V1000
>- Epson WorkForce GT-1500
>- Brother MFC-8510DN
>- Epson Perfection V33
>
>   It is to note that the probability that the scanner manufacturers fix
>   things others broke is below 100%.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: libsane1 1.0.27-1~experimental2ubuntu2
>   Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
>   ApportVersion: 2.20.7-0ubuntu3.1
>   Architecture: amd64
>   Date: Fri Oct 27 12:35:52 2017
>   EcryptfsInUse: Yes
>   SourcePackage: sane-backends
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
>

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Will Cooke]

Please could someone add a couple of screenshots for Before and After. 
We can ask design to comment.

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Olivier Tilloy]

libreoffice selects the default icon theme dynamically based on the
desktop environment. breeze is already the default icon theme on KDE and
LXQt, whereas GNOME, Mate and Unity use elementary by default (see
https://cgit.freedesktop.org/libreoffice/core/tree/vcl/source/app/IconThemeSelector.cxx#n51).

We can certainly patch this code to make breeze the default on GNOME,
but I'd like to hear the opinions of other visual designers (including
all yaru contributors) and users before we do.

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

[Sebastien Bacher]

Reopening/Assigning to TImo for eoan since there is a patch which can we
dropped once qemu is fixed

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

** Changed in: mesa (Ubuntu Eoan)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Released
Status in mesa package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in Eoan:
  Triaged
Status in qemu source package in Eoan:
  Triaged

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Sebastien Bacher]

** Changed in: modemmanager (Ubuntu Eoan)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  In Progress
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

[Sebastien Bacher]

We reviewed it in the team meeting, while it would be nice to fix we
don't believe it's an usecase common/important enough to justify team
assignment & tracking, tagging rls-ee-notfixing

** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  Triaged

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

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

[Sebastien Bacher]

Daniel, you seem to have a looked at that/pinged Jonas, I'm assigning to
you

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Also affects: mutter (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu Disco)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mutter (Ubuntu Disco)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags removed: rls-ee-incoming

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in gnome-shell source package in Disco:
  New
Status in mutter source package in Disco:
  New

Bug description:
  https://trello.com/c/i5hENxSO

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

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

[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

[Sebastien Bacher]

** Changed in: mesa (Ubuntu Eoan)
   Status: Triaged => 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/1815889

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in Eoan:
  Fix Released
Status in qemu source package in Eoan:
  Triaged

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1827284] Re: No animation when GNOME Activities overview is opened

[Sebastien Bacher]

Daniel, could you dig the details for bionic there? Did it regress in a
SRU? If so what do you recommend we do next?

** Changed in: gnome-shell (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  No animation when GNOME Activities overview is opened

Status in gnome-shell package in Ubuntu:
  Opinion
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell source package in Eoan:
  Opinion

Bug description:
  On Ubuntu 18.04.2, Xorg, Gnome version
  3.28.3+git20190124-0ubuntu18.04.1, there's no animation anymore when
  you open the activities panel. When you close it, the animation shows
  up normally. The animation used to work, but it stopped by the end of
  April 2019. It doesn't seem to be a video driver issue, since it
  happens both when using Nvidia and Intel graphics. The issue persists
  after disabling all Gnome extensions.

  It's worth mentioning that the animation shows up if you access
  activities through the top right hot corner, but it doesn't if you
  press the button or the Windows key.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May  1 18:00:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-11 (141 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom

[Sebastien Bacher]

** No longer affects: gnome-session (Ubuntu Bionic)

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

Title:
  gnome-session-check-accelerated crashed with SIGSEGV in
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Cosmic:
  Fix Released
Status in gnome-session source package in Disco:
  Fix Released
Status in gnome-session source package in Eoan:
  Fix Released

Bug description:
  Possibly:
  https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
  https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

  ---

  bug at login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  Uname: Linux 4.12.0-041200-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 09:34:09 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated
  InstallationDate: Installed on 2015-04-16 (874 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   ()
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ()
   __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
  Title: gnome-session-check-accelerated crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom

[Sebastien Bacher]

The upstream commit is describing the issue being with "X11 with nested
wayland" which doesn't seem like a frequent/important scenario.
Untargetting from bionic but it can go through rls-bb-incoming process
if someone disagrees and also it doesn't stop a SRU to happen if there
is an owner

** Changed in: gnome-session (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

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

Title:
  gnome-session-check-accelerated crashed with SIGSEGV in
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Bionic:
  Won't Fix
Status in gnome-session source package in Cosmic:
  Fix Released
Status in gnome-session source package in Disco:
  Fix Released
Status in gnome-session source package in Eoan:
  Fix Released

Bug description:
  Possibly:
  https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
  https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

  ---

  bug at login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  Uname: Linux 4.12.0-041200-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 09:34:09 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated
  InstallationDate: Installed on 2015-04-16 (874 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   ()
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ()
   __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
  Title: gnome-session-check-accelerated crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

[Marcus Tomlinson]

** Changed in: libreoffice (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: New => Triaged

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Triaged
Status in libreoffice source package in Cosmic:
  Triaged

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

   * The fix is currently in LibreOffice 6.2.2+ on disco and eoan.

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

It is, that's all that's needed now. I heard another, unrelated, gvfs
SRU was in the works and was hitting problems, though.

I have a no-change rebuild in this PPA for bionic:
https://launchpad.net/~ahasenack/+archive/ubuntu/gvfs-rebuild-1778322/

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When 

[Desktop-packages] [Bug 1827727] Re: All plugins disabled due to expired cert

[Olivier Tilloy]

The bug is marked "Fix Released" because a bug against a source package
always targets the latest development series (in this case 19.10, where
the bug is indeed fixed).

This doesn't mean the supported releases are being treated as second-
class citizens. The updates will be available to everyone very soon.

While this is indeed a critical bug, it has largely been mitigated by
Mozilla issuing a new certificate through Normandy, which is enabled by
default in Ubuntu packages. So unless users have forcefully disabled
Normandy, they shouldn't be affected by the bug anymore.

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Sebastien Bacher]

Seems like a kernel issue, marking invalid for intel but feel free to
reopen if it proves out to be an issue with the driver (not that -intel
is deprecated in favor of modesetting nowadays)

** Changed in: xserver-xorg-video-intel (Ubuntu Disco)
   Status: New => Invalid

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided => High

** Changed in: xserver-xorg-video-intel (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: xserver-xorg-video-intel (Ubuntu Disco)
   Importance: Undecided => High

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Sebastien Bacher]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-intel (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: xserver-xorg-video-intel (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: xserver-xorg-video-intel (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  New

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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