date:20200323

** Changed in: mesa (Ubuntu)
   Status: Confirmed => In Progress

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

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** No longer affects: mesa-demos (Ubuntu)

** No longer affects: mpv (Ubuntu)

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

Title:
  Clients fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784)
  [DRM_FORMAT_XRGB2101010]

Status in Mesa:
  Unknown
Status in MPV:
  Unknown
Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info: 
  fragment shader info: 
  info: 
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1)
  [3104437.111]

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should disable gestures

2020-03-23 Thread Bin Li

@Timo,

 I see your upload is still in upload queue, it's about two weeks, do you know 
who could help for this package? Thanks!
 
 
https://launchpad.net/ubuntu/bionic/+upload/22988587/+files/xf86-input-wacom_0.36.1-0ubuntu1.1_source.changes

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

Title:
  Wacom touchscreens should disable gestures

Status in OEM Priority Project:
  In Progress
Status in xf86-input-wacom package in Ubuntu:
  Fix Released
Status in xf86-input-wacom source package in Bionic:
  In Progress

Bug description:
  [Impact]

  From the original bug:

  "The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either."

  [Test case]

  Install the update, note that the touchscreen behaviour is better.

  [Regression potential]

  From the upstream commit:

  "Note that this change will effectively cause a feature regression for
  users of other environments that do *not* have their own gesture
  engines (Cinnamon, KDE, MATE, XFCE, etc.). Users will want to add an
  xorg.conf.d snippet with `Option "Gesture" "on"` to bring back the
  functionality."

  but at least I (tjaalton) haven't heard of any complaints since we've
  disabled gestures in focal (Nov 21st), so the warning might be a bit
  too pessimistic about the impact.

  
  --

  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1

[Desktop-packages] [Bug 1868659] Re: gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from cogl_framebuffer_pop_matrix() from clutter_actor_paint() from clutter_actor_real_paint() from clut

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from
  cogl_framebuffer_pop_matrix() from clutter_actor_paint() from
  clutter_actor_real_paint() from clutter_actor_continue_paint()

Status in gnome-shell package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_sign

Possibly related (just landed this week in gnome-shell, before version
3.36.1):

https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/3dd8ffc2bb1cef

** Summary changed:

- 
/usr/bin/gnome-shell:11:st_theme_node_get_icon_style:st_texture_cache_load_gicon:st_icon_update:_g_closure_invoke_va:g_signal_emit_valist
+ gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from 
st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() 
from g_signal_emit_valist()

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

Status in gnome-shell package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1868659] Re: gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from cogl_framebuffer_pop_matrix() from clutter_actor_paint() from clutter_actor_real_paint() from clut

** Summary changed:

- 
/usr/bin/gnome-shell:11:cogl_matrix_stack_pop:cogl_framebuffer_pop_matrix:clutter_actor_paint:clutter_actor_real_paint:clutter_actor_continue_paint
+ gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from 
cogl_framebuffer_pop_matrix() from clutter_actor_paint() from 
clutter_actor_real_paint() from clutter_actor_continue_paint()

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from
  cogl_framebuffer_pop_matrix() from clutter_actor_paint() from
  clutter_actor_real_paint() from clutter_actor_continue_paint()

Status in gnome-shell package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1868659] [NEW] gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from cogl_framebuffer_pop_matrix() from clutter_actor_paint() from clutter_actor_real_paint() from cl

2020-03-23 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: focal

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from
  cogl_framebuffer_pop_matrix() from clutter_actor_paint() from
  clutter_actor_real_paint() from clutter_actor_continue_paint()

Status in gnome-shell package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1868660] [NEW] gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_si

2020-03-23 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: bionic focal xenial yakkety

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

Status in gnome-shell package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

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

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Incomplete

** Summary changed:

- Bluetooth headset selected as default sound output, yet sound outputs to 
laptop speakers
+ [Dell Inspiron 7370] Bluetooth headset selected as default sound output, yet 
sound outputs to laptop speakers

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

Title:
  [Dell Inspiron 7370] Bluetooth headset selected as default sound
  output, yet sound outputs to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

I filed an issue upstream:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832

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

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

Title:
[Dell Inspiron 7370] shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker

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

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
2. Make sure it's the one selected as "Output device"
3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
5. Try to switch back to the BT device and click Test
-> same result as in step 3

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the
BT device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output
from the internal laptop speakers, even when the BT device is selected
in the Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

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

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

Title:
[Dell Inspiron 7370] shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker

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

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Description changed:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

- 1. Go to Bluetooth settings panel
- 2. Pair a BT device
- 3. Make sure it's marked as Connected, and go to the Sound settings
- 4. Make sure it's the one selected as "Output device"
- 5. Click "Test"
+ 1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
+ 2. Make sure it's the one selected as "Output device"
+ 3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
- 6. Select "Speakers - Built-in Audio" as Output device and click "Test"
+ 4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
- 7. Try to switch back to the BT device and click Test
- -> same result as in step 5
+ 5. Try to switch back to the BT device and click Test
+ -> same result as in step 3

- Tested with 2 different BT devices (one headset and one speaker)
+ Tested with 2 different BT devices (one headset and one speaker) as well
+ as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

** Description changed:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
+ Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker) as well
as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

[Desktop-packages] [Bug 1845645] Re: Emacs logs AT-SPI warnings to console on startup

2020-03-23 Thread Nicholas P

Launching Emacs outside of gdm seems like a typical use case for a
headless client, for instance using Virtualbox and ssh.  I also noticed
placing this in the environment:

export NO_AT_BRIDGE=1

resolves the error by preventing this AT extension from loading.  My
Emacs load time is much faster.

Why was the change integrated and should it be backed out?

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

Title:
  Emacs logs AT-SPI warnings to console on startup

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  When starting up certain (GTK?) applications from console in a custom
  X session, such as emacs or ubuntu-bug, there is a lot of log output
  like:

  
  """
  ** (emacs:4437): WARNING **: 15:05:10.026: AT-SPI: Could not obtain desktop 
path or name
  """

  or

  """
  ** (apport-gtk:175957): WARNING **: 15:16:16.747: AT-SPI: Could not obtain 
desktop path or name
  """


  The issue seems to be related to at-spi2-atk, or at least that's where
  the code that prints the error is:


  In register_reply in bridge.c:
    if (reply)
  {
    gchar *app_name, *obj_path;

    if (strcmp (dbus_message_get_signature (reply), "(so)") != 0)
  {
    g_warning ("AT-SPI: Could not obtain desktop path or name\n");
  }

  
  Which seems to be triggered by an attempt to register the application to ATK:
  static gboolean
  register_application (SpiBridge * app)
  {
    DBusMessage *message;
    DBusMessageIter iter;
    DBusPendingCall *pending;

    g_free (app->desktop_name);
    g_free (app->desktop_path);

    /* These will be overridden when we get a reply, but in practice these
   defaults should always be correct */
    app->desktop_name = g_strdup (ATSPI_DBUS_NAME_REGISTRY);
    app->desktop_path = g_strdup (ATSPI_DBUS_PATH_ROOT);

    message = dbus_message_new_method_call (SPI_DBUS_NAME_REGISTRY,
    ATSPI_DBUS_PATH_ROOT,
    ATSPI_DBUS_INTERFACE_SOCKET,
    "Embed");

    dbus_message_iter_init_append (message, );
    spi_object_append_reference (, app->root);

  if (!dbus_connection_send_with_reply (app->bus, message, , -1)
  || !pending)
  {
  if (pending)
    dbus_pending_call_unref (pending);

  dbus_message_unref (message);
  return FALSE;
  }

  dbus_pending_call_set_notify (pending, register_reply, app, NULL);


  
  It seems to be caused by nobody being available at the ATSPI_DBUS_PATH_ROOT 
to handle the message. I have not yet been able to figure out what *should* be 
handling the message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1845645/+subscriptions

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

[Desktop-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Summary changed:

- [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options 
but the sound keeps being emitted from the internal laptop speaker
+ [Dell Inspiron 7370] shows up in the sound output options but the sound keeps 
being emitted from the internal laptop speaker

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

Title:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

Please remember to report the issue upstream:

  https://gitlab.freedesktop.org/groups/pulseaudio/-/issues

and then mention the new bug ID here.

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1860634] Re: Gnome shell extensions disabled at every restart

[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/1860634

Title:
  Gnome shell extensions disabled at every restart

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  same like    
  #1813511

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 08:07:50 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-05 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (93 days ago)

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

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

[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

Please remember to report the issue upstream:

https://gitlab.freedesktop.org/groups/pulseaudio/-/issues

and then mention the new bug ID here.

** This bug is no longer a duplicate of bug 1850766
Bluetooth headset selected as default sound output, yet sound outputs to
laptop speakers

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

Title:
[Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
options but the sound keeps being emitted from the internal laptop
speaker

Status in pulseaudio package in Ubuntu:
New

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

1. Go to Bluetooth settings panel
2. Pair a BT device
3. Make sure it's marked as Connected, and go to the Sound settings
4. Make sure it's the one selected as "Output device"
5. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
6. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
7. Try to switch back to the BT device and click Test
-> same result as in step 5

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

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

[Desktop-packages] [Bug 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]

2020-03-23 Thread Chris Halse Rogers

Mutter actually *does* support 10bpc, just not with zwp_linux_dmabuf_v1.
It seems that mesa will incorrectly try to use formats advertised by
wl_drm but not zwp_linux_dmabuf_v1.
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4294 fixes
this for me.

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

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

Title:
  Clients fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784)
  [DRM_FORMAT_XRGB2101010]

Status in Mesa:
  Unknown
Status in MPV:
  Unknown
Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  New
Status in mpv package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info: 
  fragment shader info: 
  info: 
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22,

[Desktop-packages] [Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement

2020-03-23 Thread Rex Tsai

** Changed in: oem-priority
 Assignee: Rex Tsai (chihchun) => hugh chao (hugh712)

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

Title:
  Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Based on Energy Star Computers Specification Version 8.0[1] Table 3:
  Power Management Requirements (page 10)

  The energy star spec requests
  - The machine shall enter Sleep/Alternative Low Power Mode after no more than 
30 minutes of user inactivity. (suspend)
  - The machine shall enter Display Sleep Mode shall be set to activate after 
no more than 15 minutes of user inactivity.

  The default settings in focal are
  - The machine will enter Sleep/Alternative Low Power Mode in 20 minutes with 
battery[2]
  - The machine is always on with the AC[2]
  - Enter Display Sleep Mode in 5 minutes[3]

  OEM device team suggested to change org.gnome.settings-
  daemon.plugins.power sleep-inactive-ac-timeout to 1200 (20 minutes) as
  default to meet the Power Management Requirements of Energy Star
  Computers Specification Version 8.0.

  [1] Computers Specification Version 8.0 | | ENERGY STAR - 
https://www.energystar.gov/products/spec/computers_version_8_0_pd
  [2]  % gsettings list-recursively 
org.gnome.settings-daemon.plugins.power|grep sleep-
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200
  [3] % gsettings list-recursively org.gnome.desktop.session   
  org.gnome.desktop.session session-name 'ubuntu'
  org.gnome.desktop.session idle-delay uint32 300

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

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

[Desktop-packages] [Bug 1868649] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

2020-03-23 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1858414, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340750/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340752/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340756/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340757/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340758/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340760/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1868649/+attachment/5340761/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1858414
   gnome-shell crashed with signal 5 in 
ObjectInstance::disassociate_js_gobject()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This appeared to happen when performing an action that prompted for my
  password (gksu, or the modern equivalent).

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 20:40:03 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

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

Daniel,

this bug is not a duplicate of lp:1850766. In lp:1850766, selecting the
output device back and forth is an enough workaround to make it work.
Here, doing so doesn't do anything, and the only workaround I found is
by manually switching the sink-inputs as I described in comment #7.

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

Title:
[Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
options but the sound keeps being emitted from the internal laptop
speaker

Status in pulseaudio package in Ubuntu:
New

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

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

[Desktop-packages] [Bug 1868614] Re: at log in the resolution changes before going to desktop

Please run this command while the bug is still assigned to xorg:

  apport-collect 1868614

After that we should probably move it to gnome-shell.

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

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

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

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

Title:
  at log in the resolution changes before going to desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This happens on Ubuntu 19.10 and still happening on Ubuntu 20.04

  Let me give a little background

  My laptop (Razer Stealth) has a built in display with default 3840 by 2160.
  I currently have it set up to 1920 by 1080, as it drains the battery faster 
using the higher resolution.

  At login, the resolution show at 1920 by 1080, but after entering the
  password, the screen changes the resolution back to the default (3840
  by 2160), but once the desktop of the user loads it changes back to
  1920 by 1080.

  The change of resolution can be noticeable because the size of the
  mouse pointer becomes much smaller when logging in.

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

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

[Desktop-packages] [Bug 1868561] Re: Xorg Crash on login

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

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 1745345, 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.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** This bug has been marked a duplicate of bug 1745345
   Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: 
dixGetPrivateAddr: Assertion `key->initialized' failed.

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

Title:
  Xorg Crash on login

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes

Thanks.

Next please try this again:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

If that provides nothing new then please:

1. Reproduce the issue again.

2. Reboot and then immediately run:

journalctl -b-1 > prevboot.txt

3. Attach the file 'prevboot.txt' here.

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

Title:
gnome mouse (trackpad ) and keyboard freezes

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
My Thinkpad ist working since years without this problem. Since last
Friday, after a reboot, I got mouse and keyboard freezed. I reboot
multiple time to analyse the problem. Google as a friend shows me that
some problems are reported and I learned a lot but no solution for me.

I find out that the problem occurs after 3 to 10 minutes of mouse and
keyboard inactivity the mouse and keyboard freezes. If I always working with
the mouse or the keyboard no freeze, still for hours. The problem is still
reproducible by mouse and keyboard inactivity. This I figured out:
- Strg+Alt+Del helps but all work are lost
- klicking application (multiple points) entering some character an klicking
application again helps some time
- closing the lid and opening it after about 30 seconds helps, but requires
password.

I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and
reboot. Login and wait till freeze, wait, close lid, and open lid.

I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found
that every freeze time there is an error:
Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for
signal: StatusChanged: Error: value is out of range for Argument 'interval'
(type guint32)

timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13

Result of uname -a
Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

Result of gnome-shell --version
GNOME Shell 3.28.4

apt-cache policy gnome* is in the attached file

Any thing else I can deliver to solve the problem

Thanks and regards Rainer

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Mar 22 16:25:39 2020
DisplayManager: gdm3
EcryptfsInUse: Yes
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/1868480/+subscriptions

[Desktop-packages] [Bug 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]

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

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

Title:
  Clients fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784)
  [DRM_FORMAT_XRGB2101010]

Status in Mesa:
  Unknown
Status in MPV:
  Unknown
Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in mesa-demos package in Ubuntu:
  New
Status in mpv package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info: 
  fragment shader info: 
  info: 
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1)
  [3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1)
  [3104437.125] wl_registry@3.global(26, "wl_eglstream_controller", 1)
  [3104437.140]

[Desktop-packages] [Bug 1868415] Re: Dell l322x Touchpad click drag doesn't work

Sorry, please try again.

That tool only understands when the bug is assigned to 'xorg' but
technically going forward that's the wrong package. So I'll leave it
with 'xorg' until you successfully run that command...

** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu)

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

Title:
  Dell l322x Touchpad click drag doesn't work

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded (fresh installation) my OS from 14.04 to 18.04. And everything 
but the touchpad seems to work properly. 
  When i try to drag and drop something or selecting some text seems dead. I 
tried to do the same things with an external mouse and it works well.
   

  > sudo libinput measure touchpad-pressure
  [sudo] password di matteog: 
  Using CyPS/2 Cypress Trackpad: /dev/input/event6

  Ready for recording data.
  Pressure range used: 30:25
  Palm pressure range used: 130
  Place a single finger on the touchpad to measure pressure values.
  Ctrl+C to exit

  Sequence 116 pressure: min:  46 max:  95 avg:  84 median:  89 tags: down
  Sequence 117 pressure: min:  29 max:  97 avg:  67 median:  86 tags: down
  Sequence 118 pressure: min:  25 max:  50 avg:  41 median:  44 tags: down
  Sequence 119 pressure: min:  13 max:  14 avg:  13 median:  14 tags:
  Sequence 120 pressure: min:  28 max:  31 avg:  29 median:  31 tags: down
  Sequence 121 pressure: min:  15 max:  33 avg:  26 median:  29 tags: down
  Sequence 122 pressure: min:  37 max:  82 avg:  66 median:  73 tags: down
  Sequence 123 pressure: min:  63 max:  94 avg:  83 median:  89 tags: down
  Sequence 124 pressure: min:  66 max: 137 avg: 118 median: 126 tags: down palm
  Sequence 125 pressure: min:  47 max:  73 avg:  63 median:  68 tags: down
  Sequence 126 pressure: min:  33 max:  66 avg:  55 median:  58 tags: down
  Sequence 127 pressure: min:  32 max: 100 avg:  81 median:  91 tags: down
  Sequence 128 pressure: min:  44 max:  86 avg:  72 median:  78 tags: down
  Sequence 129 pressure: min:  62 max: 108 avg:  95 median: 103 tags: down
  Sequence 130 pressure: min:  72 max: 131 avg: 118 median: 124 tags: down palm
  Sequence 131 pressure: min:  52 max: 112 avg:  96 median: 103 tags: down
  Sequence 132 pressure: min:  44 max: 101 avg:  83 median:  88 tags: down
  Sequence 133 pressure: min: 150 max: 150 avg: 150 median: 150 tags: down palm
  Traceback (most recent call last):
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
299, in 
  main(sys.argv)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
289, in main
  loop(device)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
246, in loop
  handle_event(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
233, in handle_event
  handle_abs(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
224, in handle_abs
  print("\r{}".format(s))
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
105, in __str__
  return self._str_state() if self.is_active else self._str_summary()
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
114, in _str_summary
  self.avg(),
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
96, in avg
  return int(sum([p.pressure for p in self.points])/len(self.points))
  ZeroDivisionError: division by zero

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

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

[Desktop-packages] [Bug 1868155] Re: Banner text and user list functionality seem broken

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

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

Title:
  Banner text and user list functionality seem broken

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I am testing out what will become Ubuntu 20.04, and features that are
  useful or simply mandatory in an enterprise environment currently do
  not work.

  These features are the ability to utilize a login banner, as well as
  disable the user list on the login screen.

  For instance, even after enabling org.gnome.login-screen -> banner-
  message-enable and setting banner text via org.gnome.login-screen ->
  banner-message-text, there is no banner text present on the login
  screen.  If you blink, you can maybe see it for a split second upon
  submitting the user's password, but this is not at all useful for
  scenarios where a user must comply with certain terms before logging
  into a workstation.

  Also, it seems that org.gnome.login-screen -> disable-user-list
  currently has no effect, as it will always show my user when starting
  the machine, instead of having an empty username field that must be
  populated.

  Either these are bugs, or there is some new way to achieve this
  functionality.  If there is a new way to achieve this functionality,
  please let me know and then close this issue.  Otherwise, I think that
  this all needs addressed.  This used to work before the recent
  login/lock screen changes that were brought in when GNOME 3.36 was
  brought into the build.  (Although my output below says that GNOME
  shell is 3.35.91, actually.)

  Some more details:

  I am currently using the 2020-03-08 daily-live ISO from
  cdimage.ubuntu.com .

  Other requested information:

  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  $ apt-cache policy gdm3
  gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  $ gnome-shell --version
  GNOME Shell 3.35.91

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 14:33:30 2020
  InstallationDate: Installed on 2020-03-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

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

** This bug has been marked a duplicate of bug 1850766
   Bluetooth headset selected as default sound output, yet sound outputs to 
laptop speakers

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

Title:
  [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
  options but the sound keeps being emitted from the internal laptop
  speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1865169] Re: volume and light not working in Gnome Shell 3.35

2020-03-23 Thread Jeremie Tamburini

Just to confirm gjs version 1.63.92-1 fixes the problem.

(P.S. focal-proposed activated)

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

Title:
  volume and light not working in Gnome Shell 3.35

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to GNOME shell 3.35, the speaker icon in top bar is
  missing and both volume and light sliders are set to 0. Changing
  volume and light from keyboard works, but has no effect in gnome shell
  dropdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-16.19-generic 5.4.22
  Uname: Linux 5.4.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 18:57:54 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-01 (118 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  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/1865169/+subscriptions

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

[Desktop-packages] [Bug 1868621] Re: Lock screen password field is not aligned in center.

2020-03-23 Thread Paul White

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

** This bug has been marked a duplicate of bug 1865563
   password box not centered

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

Title:
  Lock screen password field is not aligned in center.

Status in gdm3 package in Ubuntu:
  New

Bug description:
  When I start the system or manually lock the screen the OS shows the
  Screen Lock page and that's ok. But when I click on my user to input
  password, I see the password field is not aligned center! margins are
  not equal from the borders of screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 01:20:01 2020
  InstallationDate: Installed on 2020-02-25 (27 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-03-21 (1 days ago)

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

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

[Desktop-packages] [Bug 1868415] Re: Dell l322x Touchpad click drag doesn't work

2020-03-23 Thread Matteo Gentile

matteog@matteog-XPS:~$ apport-collect 1868415
Package xorg-server not installed and no hook available, ignoring
Gtk-Message: 22:35:22.139: GtkDialog mapped without a transient parent. This is 
discouraged.


No further information has been collected

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

Title:
  Dell l322x Touchpad click drag doesn't work

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded (fresh installation) my OS from 14.04 to 18.04. And everything 
but the touchpad seems to work properly. 
  When i try to drag and drop something or selecting some text seems dead. I 
tried to do the same things with an external mouse and it works well.
   

  > sudo libinput measure touchpad-pressure
  [sudo] password di matteog: 
  Using CyPS/2 Cypress Trackpad: /dev/input/event6

  Ready for recording data.
  Pressure range used: 30:25
  Palm pressure range used: 130
  Place a single finger on the touchpad to measure pressure values.
  Ctrl+C to exit

  Sequence 116 pressure: min:  46 max:  95 avg:  84 median:  89 tags: down
  Sequence 117 pressure: min:  29 max:  97 avg:  67 median:  86 tags: down
  Sequence 118 pressure: min:  25 max:  50 avg:  41 median:  44 tags: down
  Sequence 119 pressure: min:  13 max:  14 avg:  13 median:  14 tags:
  Sequence 120 pressure: min:  28 max:  31 avg:  29 median:  31 tags: down
  Sequence 121 pressure: min:  15 max:  33 avg:  26 median:  29 tags: down
  Sequence 122 pressure: min:  37 max:  82 avg:  66 median:  73 tags: down
  Sequence 123 pressure: min:  63 max:  94 avg:  83 median:  89 tags: down
  Sequence 124 pressure: min:  66 max: 137 avg: 118 median: 126 tags: down palm
  Sequence 125 pressure: min:  47 max:  73 avg:  63 median:  68 tags: down
  Sequence 126 pressure: min:  33 max:  66 avg:  55 median:  58 tags: down
  Sequence 127 pressure: min:  32 max: 100 avg:  81 median:  91 tags: down
  Sequence 128 pressure: min:  44 max:  86 avg:  72 median:  78 tags: down
  Sequence 129 pressure: min:  62 max: 108 avg:  95 median: 103 tags: down
  Sequence 130 pressure: min:  72 max: 131 avg: 118 median: 124 tags: down palm
  Sequence 131 pressure: min:  52 max: 112 avg:  96 median: 103 tags: down
  Sequence 132 pressure: min:  44 max: 101 avg:  83 median:  88 tags: down
  Sequence 133 pressure: min: 150 max: 150 avg: 150 median: 150 tags: down palm
  Traceback (most recent call last):
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
299, in 
  main(sys.argv)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
289, in main
  loop(device)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
246, in loop
  handle_event(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
233, in handle_event
  handle_abs(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
224, in handle_abs
  print("\r{}".format(s))
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
105, in __str__
  return self._str_state() if self.is_active else self._str_summary()
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
114, in _str_summary
  self.avg(),
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
96, in avg
  return int(sum([p.pressure for p in self.points])/len(self.points))
  ZeroDivisionError: division by zero

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

This bug was fixed in the package glib2.0 - 2.62.4-1~ubuntu19.10.1

---
glib2.0 (2.62.4-1~ubuntu19.10.1) eoan; urgency=medium

  * No-change backport from unstable to eoan (LP: #1850932).
+ Contains fix for LP: #1844853 - "IBus no longer works in Qt applications
  after upgrade"

glib2.0 (2.62.4-1) unstable; urgency=medium

  * Team upload

  [ Steve Langasek ]
  * debian/tests/build: Make cross-test friendly (Closes: #946355)

  [ Iain Lane ]
  * debian/tests/build: Style fixes

  [ Simon McVittie ]
  * New upstream release

glib2.0 (2.62.3-2) unstable; urgency=medium

  * Team upload
  * Rename pkg.glib2.0.noinsttest build profile to noinsttest.
This is now registered on .

glib2.0 (2.62.3-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Drop patches that were applied upstream
  * Don't build libglib2.0-tests under pkg.glib2.0.noinsttest build profile.
This is a prototype of the proposed standard build profile noinsttest.
If the build profiles include both nocheck and pkg.glib2.0.noinsttest,
we can drop the libdbus-1-dev build-dependency without harming test
coverage or altering the contents of binary packages.
  * d/gbp.conf: Use upstream/2.62.x branch

glib2.0 (2.62.2-3) unstable; urgency=medium

  * Team upload

  [ Iain Lane ]
  * control: Drop `debian/experimental` from Vcs-*

  [ Simon McVittie ]
  * Build-depend on libdbus-1-dev for better test coverage
  * Update to upstream commit 2.62.2-28-g3cf25070e:
- d/p/goption-Relax-assertion-to-avoid-being-broken-by-kdeinit5.patch:
  Fix assertion failure when called from a process that overwrites its
  argv, such as kdeinit5
- d/p/gdbus-peer-Specifically-listen-on-127.0.0.1.patch:
  Improve reliability of gdbus-peer test in some container environments
- d/p/gdbusserver-Delete-socket-and-nonce-file-when-stopping-se.patch,
  d/p/gdbusserver-Keep-a-strong-reference-to-the-server-in-call.patch,
  d/p/gdbusauthmechanismsha1-Remove-unnecessary-g_warning-calls.patch,
  d/p/gdbusauthmechanismsha1-Create-.dbus-keyrings-directory-re.patch,
  d/p/tests-Move-main-loop-and-test-GUID-into-test-functions-in.patch,
  d/p/tests-Isolate-directories-in-gdbus-peer-test.patch,
  d/p/gdbus-peer-test-Improve-diagnostics-if-g_rmdir-fails.patch,
  d/p/gdbus-peer-test-Stop-GDBusServer-before-tearing-down-temp.patch,
  d/p/gdbus-peer-test-Use-unix-dir-address-if-exact-format-does.patch,
  d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
  Mark as applied upstream in 2.62.x branch
  * d/p/gdbus-server-auth-test-Include-gcredentialsprivate.h.patch:
Apply patch from 2.63.x to fix missing coverage in test for #941018
  * d/p/Make-ld-executable-configurable.patch:
Apply patch from 2.63.x to use cross ld where necessary
  * d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
Mark as applied upstream in 2.63.x branch
  * Improve patch metadata: use more URLs for bug references

glib2.0 (2.62.2-2) unstable; urgency=medium

  * Team upload
  * Update to upstream commit 2.62.2-14-gfcbb88823:
- d/p/gdesktopappinfo-Allocate-DesktopFileDir-structs-dynamical.patch,
  d/p/gdesktopappinfo-Cancel-file-monitor-when-resetting-a-Desk.patch,
  d/p/glocalfilemonitor-Keep-a-weak-ref-to-the-monitor-in-GFile.patch:
  Fix intermittent test failures for GDesktopAppInfo (Closes: #941550)
- d/p/gvariant-Limit-recursion-in-g_variant_parse.patch:
  Ensure that parsing a text-format GVariant does not run out of stack
  space
- d/p/tests-Use-objcopy-from-the-cross-compilation-file-if-conf.patch,
  d/p/docs-Add-objcopy-to-example-cross-compilation-file.patch:
  Use the appropriate architecture's objcopy when cross-compiling
- d/p/gtestutils-Add-additional-non-NULL-check-in-g_assert_cmpm.patch:
  Avoid false positive NULL dereference warnings in g_assert_cmpmem()
- d/p/gspawn-Port-to-g_poll-from-select.patch:
  Fix launching subprocesses when a very large number of fds are open
- d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
  d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
  d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
  Ensure libdbus clients can authenticate with a GDBusServer like the
  one in ibus (Closes: #941018)
  * d/p/gdbusserver-Delete-socket-and-nonce-file-when-stopping-se.patch,
d/p/gdbusserver-Keep-a-strong-reference-to-the-server-in-call.patch,
d/p/Add-a-test-for-GDBusServer-authentication.patch:
Backport regression test for #941018 from upstream git master
  * d/p/gdbusauthmechanismsha1-Remove-unnecessary-g_warning-calls.patch,
d/p/gdbusauthmechanismsha1-Create-.dbus-keyrings-directory-re.patch,
d/p/tests-Move-main-loop-and-test-GUID-into-test-functions-in.patch,
d/p/tests-Isolate-directories-in-gdbus-peer-test.patch:

[Desktop-packages] [Bug 1844853] Update Released

2020-03-23 Thread Brian Murray

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

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in glib2.0 source package in Disco:
  Won't Fix
Status in glib2.0 source package in Eoan:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.5

---
glib2.0 (2.56.4-0ubuntu0.18.04.5) bionic; urgency=medium

  [ Gunnar Hjalmarsson ]
  * d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
- Ensure libdbus clients can authenticate with a GDBusServer like
  the one in ibus. The patches cherry picked from 2.62.2-2 in focal
  in order to allow the ibus fix of CVE-2019-14822 to be re-enabled
  without breaking ibus for Qt applications (LP: #1844853).

  [ Iain Lane ]
  * d/p/Add-a-test-for-GDBusServer-authentication.patch: Additionally backport
this commit to add a test for the above fixes.
+ BD on libdbus-1-dev so that the above test gets run properly.

 -- Gunnar Hjalmarsson   Thu, 31 Oct 2019 00:16:00
+0100

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: glib2.0 (Ubuntu Eoan)
   Status: Fix Committed => 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/1844853

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in glib2.0 source package in Disco:
  Won't Fix
Status in glib2.0 source package in Eoan:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850932] Re: [SRU] Backport 2.62.4-1

This bug was fixed in the package glib2.0 - 2.62.4-1~ubuntu19.10.1

---
glib2.0 (2.62.4-1~ubuntu19.10.1) eoan; urgency=medium

  * No-change backport from unstable to eoan (LP: #1850932).
+ Contains fix for LP: #1844853 - "IBus no longer works in Qt applications
  after upgrade"

glib2.0 (2.62.4-1) unstable; urgency=medium

  * Team upload

  [ Steve Langasek ]
  * debian/tests/build: Make cross-test friendly (Closes: #946355)

  [ Iain Lane ]
  * debian/tests/build: Style fixes

  [ Simon McVittie ]
  * New upstream release

glib2.0 (2.62.3-2) unstable; urgency=medium

  * Team upload
  * Rename pkg.glib2.0.noinsttest build profile to noinsttest.
This is now registered on .

glib2.0 (2.62.3-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Drop patches that were applied upstream
  * Don't build libglib2.0-tests under pkg.glib2.0.noinsttest build profile.
This is a prototype of the proposed standard build profile noinsttest.
If the build profiles include both nocheck and pkg.glib2.0.noinsttest,
we can drop the libdbus-1-dev build-dependency without harming test
coverage or altering the contents of binary packages.
  * d/gbp.conf: Use upstream/2.62.x branch

glib2.0 (2.62.2-3) unstable; urgency=medium

  * Team upload

  [ Iain Lane ]
  * control: Drop `debian/experimental` from Vcs-*

  [ Simon McVittie ]
  * Build-depend on libdbus-1-dev for better test coverage
  * Update to upstream commit 2.62.2-28-g3cf25070e:
- d/p/goption-Relax-assertion-to-avoid-being-broken-by-kdeinit5.patch:
  Fix assertion failure when called from a process that overwrites its
  argv, such as kdeinit5
- d/p/gdbus-peer-Specifically-listen-on-127.0.0.1.patch:
  Improve reliability of gdbus-peer test in some container environments
- d/p/gdbusserver-Delete-socket-and-nonce-file-when-stopping-se.patch,
  d/p/gdbusserver-Keep-a-strong-reference-to-the-server-in-call.patch,
  d/p/gdbusauthmechanismsha1-Remove-unnecessary-g_warning-calls.patch,
  d/p/gdbusauthmechanismsha1-Create-.dbus-keyrings-directory-re.patch,
  d/p/tests-Move-main-loop-and-test-GUID-into-test-functions-in.patch,
  d/p/tests-Isolate-directories-in-gdbus-peer-test.patch,
  d/p/gdbus-peer-test-Improve-diagnostics-if-g_rmdir-fails.patch,
  d/p/gdbus-peer-test-Stop-GDBusServer-before-tearing-down-temp.patch,
  d/p/gdbus-peer-test-Use-unix-dir-address-if-exact-format-does.patch,
  d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
  Mark as applied upstream in 2.62.x branch
  * d/p/gdbus-server-auth-test-Include-gcredentialsprivate.h.patch:
Apply patch from 2.63.x to fix missing coverage in test for #941018
  * d/p/Make-ld-executable-configurable.patch:
Apply patch from 2.63.x to use cross ld where necessary
  * d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
Mark as applied upstream in 2.63.x branch
  * Improve patch metadata: use more URLs for bug references

glib2.0 (2.62.2-2) unstable; urgency=medium

  * Team upload
  * Update to upstream commit 2.62.2-14-gfcbb88823:
- d/p/gdesktopappinfo-Allocate-DesktopFileDir-structs-dynamical.patch,
  d/p/gdesktopappinfo-Cancel-file-monitor-when-resetting-a-Desk.patch,
  d/p/glocalfilemonitor-Keep-a-weak-ref-to-the-monitor-in-GFile.patch:
  Fix intermittent test failures for GDesktopAppInfo (Closes: #941550)
- d/p/gvariant-Limit-recursion-in-g_variant_parse.patch:
  Ensure that parsing a text-format GVariant does not run out of stack
  space
- d/p/tests-Use-objcopy-from-the-cross-compilation-file-if-conf.patch,
  d/p/docs-Add-objcopy-to-example-cross-compilation-file.patch:
  Use the appropriate architecture's objcopy when cross-compiling
- d/p/gtestutils-Add-additional-non-NULL-check-in-g_assert_cmpm.patch:
  Avoid false positive NULL dereference warnings in g_assert_cmpmem()
- d/p/gspawn-Port-to-g_poll-from-select.patch:
  Fix launching subprocesses when a very large number of fds are open
- d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
  d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
  d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
  Ensure libdbus clients can authenticate with a GDBusServer like the
  one in ibus (Closes: #941018)
  * d/p/gdbusserver-Delete-socket-and-nonce-file-when-stopping-se.patch,
d/p/gdbusserver-Keep-a-strong-reference-to-the-server-in-call.patch,
d/p/Add-a-test-for-GDBusServer-authentication.patch:
Backport regression test for #941018 from upstream git master
  * d/p/gdbusauthmechanismsha1-Remove-unnecessary-g_warning-calls.patch,
d/p/gdbusauthmechanismsha1-Create-.dbus-keyrings-directory-re.patch,
d/p/tests-Move-main-loop-and-test-GUID-into-test-functions-in.patch,
d/p/tests-Isolate-directories-in-gdbus-peer-test.patch:

[Desktop-packages] [Bug 1848202] Update Released

2020-03-23 Thread Brian Murray

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

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

Title:
  Use after free in gdbus leads to eds segfaults

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Released

Bug description:
  [ Description ]

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

  [ Fix ]

  This bug was fixed upstream in 2.62.2 (see the links below). That
  update is being issues to eoan.

  [ QA ]

  Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't
  need to explicitly test that this bug is fixed. Nevertheless, to
  verify this bug please give the desktop a good workout. Ideally
  install the SRU and use your machine as you would normally for a
  variety of tasks. Make sure there are no regressions.

  [ Regression potential ]

  1) The changes involve mutexes and stuff, which is error prone.

  2) It's GLib, a core library, so any bad regressions will be really
  serious for the desktop as a whole.

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

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

[Desktop-packages] [Bug 1848202] Re: Use after free in gdbus leads to eds segfaults

This bug was fixed in the package glib2.0 - 2.62.4-1~ubuntu19.10.1

---
glib2.0 (2.62.4-1~ubuntu19.10.1) eoan; urgency=medium

  * No-change backport from unstable to eoan (LP: #1850932).
+ Contains fix for LP: #1844853 - "IBus no longer works in Qt applications
  after upgrade"

glib2.0 (2.62.4-1) unstable; urgency=medium

  * Team upload

  [ Steve Langasek ]
  * debian/tests/build: Make cross-test friendly (Closes: #946355)

  [ Iain Lane ]
  * debian/tests/build: Style fixes

  [ Simon McVittie ]
  * New upstream release

glib2.0 (2.62.3-2) unstable; urgency=medium

  * Team upload
  * Rename pkg.glib2.0.noinsttest build profile to noinsttest.
This is now registered on .

glib2.0 (2.62.3-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Drop patches that were applied upstream
  * Don't build libglib2.0-tests under pkg.glib2.0.noinsttest build profile.
This is a prototype of the proposed standard build profile noinsttest.
If the build profiles include both nocheck and pkg.glib2.0.noinsttest,
we can drop the libdbus-1-dev build-dependency without harming test
coverage or altering the contents of binary packages.
  * d/gbp.conf: Use upstream/2.62.x branch

glib2.0 (2.62.2-3) unstable; urgency=medium

  * Team upload

  [ Iain Lane ]
  * control: Drop `debian/experimental` from Vcs-*

  [ Simon McVittie ]
  * Build-depend on libdbus-1-dev for better test coverage
  * Update to upstream commit 2.62.2-28-g3cf25070e:
- d/p/goption-Relax-assertion-to-avoid-being-broken-by-kdeinit5.patch:
  Fix assertion failure when called from a process that overwrites its
  argv, such as kdeinit5
- d/p/gdbus-peer-Specifically-listen-on-127.0.0.1.patch:
  Improve reliability of gdbus-peer test in some container environments
- d/p/gdbusserver-Delete-socket-and-nonce-file-when-stopping-se.patch,
  d/p/gdbusserver-Keep-a-strong-reference-to-the-server-in-call.patch,
  d/p/gdbusauthmechanismsha1-Remove-unnecessary-g_warning-calls.patch,
  d/p/gdbusauthmechanismsha1-Create-.dbus-keyrings-directory-re.patch,
  d/p/tests-Move-main-loop-and-test-GUID-into-test-functions-in.patch,
  d/p/tests-Isolate-directories-in-gdbus-peer-test.patch,
  d/p/gdbus-peer-test-Improve-diagnostics-if-g_rmdir-fails.patch,
  d/p/gdbus-peer-test-Stop-GDBusServer-before-tearing-down-temp.patch,
  d/p/gdbus-peer-test-Use-unix-dir-address-if-exact-format-does.patch,
  d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
  Mark as applied upstream in 2.62.x branch
  * d/p/gdbus-server-auth-test-Include-gcredentialsprivate.h.patch:
Apply patch from 2.63.x to fix missing coverage in test for #941018
  * d/p/Make-ld-executable-configurable.patch:
Apply patch from 2.63.x to use cross ld where necessary
  * d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
Mark as applied upstream in 2.63.x branch
  * Improve patch metadata: use more URLs for bug references

glib2.0 (2.62.2-2) unstable; urgency=medium

  * Team upload
  * Update to upstream commit 2.62.2-14-gfcbb88823:
- d/p/gdesktopappinfo-Allocate-DesktopFileDir-structs-dynamical.patch,
  d/p/gdesktopappinfo-Cancel-file-monitor-when-resetting-a-Desk.patch,
  d/p/glocalfilemonitor-Keep-a-weak-ref-to-the-monitor-in-GFile.patch:
  Fix intermittent test failures for GDesktopAppInfo (Closes: #941550)
- d/p/gvariant-Limit-recursion-in-g_variant_parse.patch:
  Ensure that parsing a text-format GVariant does not run out of stack
  space
- d/p/tests-Use-objcopy-from-the-cross-compilation-file-if-conf.patch,
  d/p/docs-Add-objcopy-to-example-cross-compilation-file.patch:
  Use the appropriate architecture's objcopy when cross-compiling
- d/p/gtestutils-Add-additional-non-NULL-check-in-g_assert_cmpm.patch:
  Avoid false positive NULL dereference warnings in g_assert_cmpmem()
- d/p/gspawn-Port-to-g_poll-from-select.patch:
  Fix launching subprocesses when a very large number of fds are open
- d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
  d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
  d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
  Ensure libdbus clients can authenticate with a GDBusServer like the
  one in ibus (Closes: #941018)
  * d/p/gdbusserver-Delete-socket-and-nonce-file-when-stopping-se.patch,
d/p/gdbusserver-Keep-a-strong-reference-to-the-server-in-call.patch,
d/p/Add-a-test-for-GDBusServer-authentication.patch:
Backport regression test for #941018 from upstream git master
  * d/p/gdbusauthmechanismsha1-Remove-unnecessary-g_warning-calls.patch,
d/p/gdbusauthmechanismsha1-Create-.dbus-keyrings-directory-re.patch,
d/p/tests-Move-main-loop-and-test-GUID-into-test-functions-in.patch,
d/p/tests-Isolate-directories-in-gdbus-peer-test.patch:

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu4.5

---
glib2.0 (2.48.2-0ubuntu4.5) xenial; urgency=medium

  * d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
- Ensure libdbus clients can authenticate with a GDBusServer like
  the one in ibus. The patches cherry picked from 2.62.2-2 in focal
  in order to allow the ibus fix of CVE-2019-14822 to be re-enabled
  without breaking ibus for Qt applications (LP: #1844853).

 -- Gunnar Hjalmarsson   Thu, 31 Oct 2019 00:48:00
+0100

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: Fix Committed => 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/1844853

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in glib2.0 source package in Disco:
  Won't Fix
Status in glib2.0 source package in Eoan:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850932] Update Released

2020-03-23 Thread Brian Murray

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

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

Title:
  [SRU] Backport 2.62.4-1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Released

Bug description:
  [ Description ]

  I'm creating this bug report to have a place to describe the proposed
  backport of glib2.0 2.62.4-1 from focal.

  One purpose of this backport is to fix bug #1844853.

  But there are several other changes. Here's the diff of NEWS:

  +Overview of changes in GLib 2.62.4
  +==
  +
  +* Apply recursion depth limits to variants in D-Bus messages (!1290)
  +
  +* Bugs fixed:
  + - #1938 GDateTime doesn't support leap seconds
  + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” 
+to glib-2-62
  + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to 
glib-2-62
  + - !1266 Backport !1265 “build: don't check for protected visibility” to 
+glib-2-62
  + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62
  + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus 
messages” to glib-2-62
  +
  +Overview of changes in GLib 2.62.3
  +==
  +
  +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject 
to
  +  FD limits (#954)
  +
  +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917)
  +
  +* Bugs fixed:
  + - #954 The g_spawn_sync() function uses select() which has limitations
  + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type 
'(null)' in cast to 'GDBusServer'
  + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7
  + - #1903 use-after-free in mimeapps test causes intermittent segfault during 
testing
  + - #1916 objcopy not used from cross-compilation file in GIO tests
  + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and 
new GCC
  + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62
  + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to 
glib-2-62
  + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62`
  + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62
  + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by 
kdeinit5” to glib-2-62
  + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1
  + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error”
  + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring 
events” to glib-2-62
  + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” 
to glib-2-62
  +
  +
  +Overview of changes in GLib 2.62.2
  +==
  +
  +* Bugs fixed:
  + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a 
dedicated thread
  + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” 
to glib-2-62
  + - !1156 Backport !1146 Solaris fixes to glib-2-62

  This release can be considered to be tested under
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  There are patches from the upstream master branch rather than this
  stable release:

  + Add-a-test-for-GDBusServer-authentication.patch
  + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch
  + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch
  + Make-ld-executable-configurable.patch

  They are sensible backports which I hope are appropriate for SRU.

  [ QA ]

  The testsuite fixes will verify themselves during the build and
  autopkgtest.

  For the rest of the fixes, please exercise the desktop thoroughly. Log
  in, log out, run many applications and make sure there are no
  regressions.

  [ Regression potential ]

  test fixes> Build failures or autopkgtest failures.

  GLib is a central desktop library. Regressions could break any part of
  the desktop - so QA is important, the SRU exception notwithstanding.

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

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

[Desktop-packages] [Bug 1704893] Re: Writer closes when finished loading without error

2020-03-23 Thread Sondra Kinsey

The attached file is the result of running this command:
$ rm -Rf ~/.config/libreoffice; libreoffice --calc --backtrace; rm -Rf 
~/.config/libreoffice; libreoffice --help --backtrace

$ libreoffice --help results in this output:
terminate called after throwing an instance of 
'com::sun::star::uno::DeploymentException'
$ libreoffice --calc results in this output:
I18N: Operating system doesn't support locale ""
I18N: Operating system doesn't support locale "en_US"
Fatal exception: Signal 11
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f85d1385568]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c5d6)[0x7f85d13ae5d6]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f85d0fbff20]
/usr/lib/libreoffice/program/libuno_cppu.so.3(uno_type_any_assign+0x705)[0x7f85ca666dc5]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2948148)[0x7f85d3f14148]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2948eea)[0x7f85d3f14eea]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0xcb)[0x7f85d3f0947b]
/usr/lib/libreoffice/program/libmergedlo.so(+0x29a1d95)[0x7f85d3f6dd95]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x125)[0x7f85d3f6f345]
/usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x1a0)[0x7f85d42bba00]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cf11dd)[0x7f85d42bd1dd]
/usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f85d42bd240]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f85d3301fe5]
/usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560ecfdc278b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f85d0fa2b97]
/usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560ecfdc27ca]

## Environment Info
$ apt show libreoffice-calc  |grep -i Version
Version: 1:6.0.7-0ubuntu0.18.04.10
$ lsb_release -d
Description:Ubuntu 18.04.3 LTS
$ java --version
openjdk 11.0.6 2020-01-14
OpenJDK Runtime Environment (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1, mixed 
mode, sharing)


** Attachment added: "gdbtrace.log"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1704893/+attachment/5340700/+files/gdbtrace.log

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

Title:
  Writer closes when finished loading without error

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I attempt to open a document in LibreOffice Writer, by any
  method, I am shown a loading dialog with a progress bar. The progress
  bar advances to about 95%, then disappears, and nothing happens.

  I have tried launching LibreOffice Writer by several methods:
  - Start LibreOffice, click "Create/Writer Document"
  - Open a filetype associated with LibreOffice Writer in a file browser
  - Launch libreoffice --writer in a terminal (This outputs nothing)

  I have confirmed via ps -A that LibreOffice is truly closed, and not
  merely invisible.

  Things I tried, with no difference:
  - sudo apt-get install --reinstall libreoffice-writer
  - rm ~/.config/libreoffice
  - cp -a /usr/lib/libreoffice/share ~/.config/libreoffice/4/user

  This is a fresh install of LibreOffice on a fresh install of Lubuntu.

  Other LibreOffice applications, such as Calc, work fine.

  I believe the same problem may have been reported at
  - https://askubuntu.com/questions/129383/libreoffice-not-opening
  - 
https://askubuntu.com/questions/697309/unable-to-open-libreoffice-writer?rq=1
  Nothing there helped me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-writer 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Jul 17 20:22:50 2017
  InstallationDate: Installed on 2017-07-05 (12 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868614] Re: at log in the resolution changes before going to desktop

2020-03-23 Thread Kain Centeno

** Package changed: ubuntu => gdm3 (Ubuntu)

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

Title:
  at log in the resolution changes before going to desktop

Status in gdm3 package in Ubuntu:
  New

Bug description:
  This happens on Ubuntu 19.10 and still happening on Ubuntu 20.04

  Let me give a little background

  My laptop (Razer Stealth) has a built in display with default 3840 by 2160.
  I currently have it set up to 1920 by 1080, as it drains the battery faster 
using the higher resolution.

  At login, the resolution show at 1920 by 1080, but after entering the
  password, the screen changes the resolution back to the default (3840
  by 2160), but once the desktop of the user loads it changes back to
  1920 by 1080.

  The change of resolution can be noticeable because the size of the
  mouse pointer becomes much smaller when logging in.

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

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

[Desktop-packages] [Bug 1868614] [NEW] at log in the resolution changes before going to desktop

You have been subscribed to a public bug:

This happens on Ubuntu 19.10 and still happening on Ubuntu 20.04

Let me give a little background

My laptop (Razer Stealth) has a built in display with default 3840 by 2160.
I currently have it set up to 1920 by 1080, as it drains the battery faster 
using the higher resolution.

At login, the resolution show at 1920 by 1080, but after entering the
password, the screen changes the resolution back to the default (3840 by
2160), but once the desktop of the user loads it changes back to 1920 by
1080.

The change of resolution can be noticeable because the size of the mouse
pointer becomes much smaller when logging in.

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


** Tags: bot-comment
-- 
at log in the resolution changes before going to desktop
https://bugs.launchpad.net/bugs/1868614
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 in Ubuntu.

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

After successfully downgrading, I upgraded again to 1:13.99.1-1ubuntu1,
rebooted my laptop, and lo and behold, my bluetooth headset works again.

I wonder if simply reinstalling the pulseaudio packages instead of
downgrading and upgrading again would have fixed the problem. I'll test
that if it happens again.

I'm removing the rls-ff-incoming tag for now.

** Tags removed: rls-ff-incoming

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

2020-03-23 Thread Per-Inge

Happened again, but now it refers to icon instead of font.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0

  ---

  This happened when I closed Chrome and moved the curser to "Power
  Off/Log Out, Settings .."

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 22 11:22:08 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-15 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_get_font_features () from /usr/lib/gnome-shell/libst-1.0.so
   _st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1868621] [NEW] Lock screen password field is not aligned in center.

2020-03-23 Thread Sina Carnelious

Public bug reported:

When I start the system or manually lock the screen the OS shows the
Screen Lock page and that's ok. But when I click on my user to input
password, I see the password field is not aligned center! margins are
not equal from the borders of screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 24 01:20:01 2020
InstallationDate: Installed on 2020-02-25 (27 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-03-21 (1 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Lock screen password field is not aligned in center.

Status in gdm3 package in Ubuntu:
  New

Bug description:
  When I start the system or manually lock the screen the OS shows the
  Screen Lock page and that's ok. But when I click on my user to input
  password, I see the password field is not aligned center! margins are
  not equal from the borders of screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 01:20:01 2020
  InstallationDate: Installed on 2020-02-25 (27 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-03-21 (1 days ago)

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

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

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

2020-03-23 Thread Chris Patterson

FWIW, I'm running 20.04 and it appears to affect other snaps too (e.g.
irccloud).

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

2020-03-23 Thread Chris Patterson

I narrowed it down to something happening with a locally installed font
in ~/.fonts.

To reproduce:
$ wget 
https://github.com/adobe-fonts/source-code-pro/blob/release/VAR/SourceCodeVariable-Roman.otf?raw=true
 -O ~/.fonts/SourceCodeVariable-Roman.otf 

$ chromium --enable-logging=stderr
 to see dialog works
 to kill browser

$ chromium --enable-logging=stderr
 to see dialog breaks

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-03-23 Thread Mirko Ducic

I have the same issue on my Dell G3 3590

I "fixed" output (https://www.linuxuprising.com/2018/06/fix-no-sound-
dummy-output-issue-in.html), on similar way as others, but input /
internal microphone remains undetected (unplugged, as pulse audio says).

External microphone works fine and it saves me for now.

Ubuntu version: 18.04.4
Kernel version: 5.0.0-1043-oem-osp1

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Desktop-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system

2020-03-23 Thread Petr Doležal

Thanks for looking into this.

However, this doesn't appear to do anything, because for me the booting
log has a line with the following:

snd_hda_intel: unknown parameter 'dmic_detect' ignored


And indeed there is nothing in the /sys/modules/snd_hda_intel/parameters of 
this sort. Does your system have this parameter in that folder?

I wonder if I should try to update the drivers or something.

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

Title:
  [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone -
  since installation of system

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The inbuilt microphone has never worked on the version of ubuntu on
  this computer. The hardware works completely fine on other operating
  systems (Windows).

  
  Distribution:   Ubuntu 18.04.2 LTS

  alsa-base:  Installed: 1.0.25+dfsg-0ubuntu5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.21-041921-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lune   1908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  6 23:54:58 2019
  InstallationDate: Installed on 2019-01-06 (120 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 0 3 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1273 F pulseaudio
lune   1908 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Carlsberg_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF514-53T
  dmi.product.sku: 
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

I downgraded pulseaudio to 1:13.0-3ubuntu2, and the problem is gone, so
this appears to be a pulseaudio regression.

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2020-03-23 Thread Steve Langasek

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

On March 23, 2020 3:08:07 AM PDT, Kiruahxh <1671...@bugs.launchpad.net> wrote:
>*** This bug is a duplicate of bug 1688018 ***
>https://bugs.launchpad.net/bugs/1688018
>
>It affects me too on Ubuntu 19.04 using OpenConnect VPN

Ubuntu 19.04 has reached end of life and is no longer supported. Please
upgrade.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1868155] Re: Banner text and user list functionality seem broken

2020-03-23 Thread Joe Prostko

Sorry for taking some time to reply, but I have filed the bug as
requested.

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2472

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2472
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2472

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

Title:
  Banner text and user list functionality seem broken

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I am testing out what will become Ubuntu 20.04, and features that are
  useful or simply mandatory in an enterprise environment currently do
  not work.

  These features are the ability to utilize a login banner, as well as
  disable the user list on the login screen.

  For instance, even after enabling org.gnome.login-screen -> banner-
  message-enable and setting banner text via org.gnome.login-screen ->
  banner-message-text, there is no banner text present on the login
  screen.  If you blink, you can maybe see it for a split second upon
  submitting the user's password, but this is not at all useful for
  scenarios where a user must comply with certain terms before logging
  into a workstation.

  Also, it seems that org.gnome.login-screen -> disable-user-list
  currently has no effect, as it will always show my user when starting
  the machine, instead of having an empty username field that must be
  populated.

  Either these are bugs, or there is some new way to achieve this
  functionality.  If there is a new way to achieve this functionality,
  please let me know and then close this issue.  Otherwise, I think that
  this all needs addressed.  This used to work before the recent
  login/lock screen changes that were brought in when GNOME 3.36 was
  brought into the build.  (Although my output below says that GNOME
  shell is 3.35.91, actually.)

  Some more details:

  I am currently using the 2020-03-08 daily-live ISO from
  cdimage.ubuntu.com .

  Other requested information:

  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  $ apt-cache policy gdm3
  gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  $ gnome-shell --version
  GNOME Shell 3.35.91

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 14:33:30 2020
  InstallationDate: Installed on 2020-03-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  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/1868155/+subscriptions

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

[Desktop-packages] [Bug 1868602] [NEW] No progress information while uploading to google drive mounted folder

2020-03-23 Thread Dipun

Public bug reported:

When attempting to upload a large file (a compressed 7z file ~300mb) the
program showed a transfer speed of 0 bytes/s and showed no progress
throughout. I cancelled a few times, but one last time, I decided to
wait more than just a few minutes. The job completed, but there was not
visual feedback.

This is my first bug report, but I assume that seeing as this is an edge
version of Ubuntu, this is where I should report this type of thing.

Description:Ubuntu 19.10
Release:19.10

nautilus:
  Installed: 1:3.34.1-1ubuntu1
  Candidate: 1:3.34.1-1ubuntu1
  Version table:
 *** 1:3.34.1-1ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 23 17:23:29 2020
GsettingsChanges:
 b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'221'
InstallationDate: Installed on 2020-03-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug eoan

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

Title:
  No progress information while uploading to google drive mounted folder

Status in nautilus package in Ubuntu:
  New

Bug description:
  When attempting to upload a large file (a compressed 7z file ~300mb)
  the program showed a transfer speed of 0 bytes/s and showed no
  progress throughout. I cancelled a few times, but one last time, I
  decided to wait more than just a few minutes. The job completed, but
  there was not visual feedback.

  This is my first bug report, but I assume that seeing as this is an
  edge version of Ubuntu, this is where I should report this type of
  thing.

  Description:  Ubuntu 19.10
  Release:  19.10

  nautilus:
Installed: 1:3.34.1-1ubuntu1
Candidate: 1:3.34.1-1ubuntu1
Version table:
   *** 1:3.34.1-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 17:23:29 2020
  GsettingsChanges:
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'221'
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/zsh
  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/1868602/+subscriptions

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

[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-03-23 Thread Roman

Reproduced on `Acer Aspire VN7-592G`. Runnung on Ubuntu 19.10, kernel
version 5.3.

Firstly had no sound devices detected at all. Adding 
`options snd-hda-intel dmic_detect=0` to `/etc/modprobe.d/alsa-base.conf`
Fixed the issue and sound appeared. 

But after that found out, that no input sound device is detected by system, 
along with headset mic.
adding
`options snd-hda-intel mode=aspire-headset-mic`
resolved issue for headset, obviously, but still no default input device is 
detected by system.

Also've been trying to use
`options snd-hda-intel index=0 model=laptop-dmic`
after that. Device appeared in sound panel, but it's recording only static 
noise, nothing more.

Still finding a way to resolve issue for built-in mic.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

2020-03-23 Thread Chris Patterson

Reproduces for me in the same manner as Steven. I removed my profile,
removed cache and config, and still reproduces.

Logging between working run and failed run shows no diff.

$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

$ chromium --enable-logging=stderr
Gtk-Message: 13:24:59.088: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:24:59.089: Failed to load module "canberra-gtk-module"
GLib-GIO-Message: 13:24:59.097: Using the 'memory' GSettings backend.  Your 
settings will not be saved or shared with other applications.
[28309:28309:0323/132459.160785:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[28312:28321:0323/132459.422856:WARNING:spdy_session.cc(3304)] Received HEADERS 
for invalid stream 3
[28174:28174:0323/132459.462323:ERROR:CONSOLE(1)] "Refused to execute inline 
event handler because it violates the following Content Security Policy 
directive: "script-src 'strict-dynamic' 
'sha256-1+GSDjMMklBjZY0QiWq+tGupCvajw4Xbn46ect2mZgM=' 
'sha256-2mX1M62Fd0u8q0dQY2mRsK5S1NS9jJuQAvyE8tD0dkQ=' 
'sha256-6ilhNY6mjQEQ9pQ14zz/I7nMIcfHcceCwbNxtAalnbQ=' 
'sha256-HqdPsO6hNmT/mfSeGdcX3eEGrZVva7AKD2Z2+1ujCZ8=' 
'sha256-5ArfzK+D442gOOu18DQ8eY13vaOV24n4bfqmSi17OoI=' 
'sha256-IEF9PjeyU0vsr61C8cm3JQOerOYWdBsaGddCSPp6tZs=' 
'sha256-RIDhH5uF+ciLoS6AP6ZkoxuwQyczkrTetThxXwVwFJI=' 
'sha256-fLmgOLhnyIaxgfQuiOVP+mhFRdHP2zDXlKpsRJWBbr4='". Either the 
'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is 
required to enable inline execution.
", source: chrome-search://local-ntp/local-ntp.html (1)
[28333:1:0323/132459.611915:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[28333:1:0323/132459.612368:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
Gtk-Message: 13:25:00.348: GtkDialog mapped without a transient parent. This is 
discouraged.
[28174:28316:0323/132500.805810:ERROR:udev_watcher.cc(96)] Failed to begin udev 
enumeration.
[28174:28174:0323/132502.787189:WARNING:pref_notifier_impl.cc(40)] Pref 
observer for media_router.cast_allow_all_ips found at shutdown.
[28174:28174:0323/132502.787211:WARNING:pref_notifier_impl.cc(40)] Pref 
observer for browser.relaunch_notification_period found at shutdown.

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264

2020-03-23 Thread knossos456

Hi? no news ?

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

Title:
  Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i
  H.264

Status in mesa package in Ubuntu:
  New

Bug description:
  uname -a
  Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  inxi -G
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 
240/340 OEM]
 Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 
9.0.0) version: 4.5 Mesa 19.2.8

  For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen
  (top) compressed image.

  To solve the default, i have to revert via synaptic the package mesa-
  va-driver to 19.0.8.

  Other solution is to take nighty builds as complete mesa package via : 
  https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers   that works 
too and is at mesa 20.1 git

  Please correct the problem to the official Ubuntu repos.

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

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

[Desktop-packages] [Bug 1867345] Re: Do not ship "Extensions" application with gnome-shell

2020-03-23 Thread Iain Lane

We'll move it to a separate binary package.

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

Title:
  Do not ship "Extensions" application with gnome-shell

Status in One Hundred Papercuts:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Consider not shipping the "Extensions" application with gnome-shell in
  Ubuntu 20.04. This application is intended to be a standalone
  application and is not much useful in Ubuntu at the moment since new
  extensions can't be installed (because of
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1866841).

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-03-23 Thread Troy Ready

I agree @cpbl -- there are almost certainly better options available.
Maciej Borzecki detailed a good proposal at
https://github.com/snapcore/snapd/pull/7731#issuecomment-585721100 (with
some follow-on thoughts added by jdstrand at
https://github.com/snapcore/snapd/pull/7731#pullrequestreview-362900171),
but at this point it's up to someone to implement it.

I just did the easy/lazy small Zoom PR, since I'm just an internet rando
without time at the moment to develop the real fix.

Unless something dramatically changes here in the next couple of weeks,
I think anyone wanting a simple way to get the old xdg behavior on 20.04
is going to forced to:

1) Use Google-supplied binary Chrome
or
2) Switch distros

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-03-23 Thread Christopher Barrington-Leigh

If the approach so far is to individually whitelist classes of links,
surely can't this be better dealt with by doing something similar to how
Chromium responds to me clicking on a downloaded file: it asks me if
it's okay to have snap launch that file?  Can't we do this for links
that go to xdg-open without downloading a file?

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-03-23 Thread Christopher Barrington-Leigh

Yeah, this can be labelled a COVID-relevant bug, since there are
countless new users flooding to Zoom, etc...

It looks like this is being worked on within the last four days:

https://github.com/snapcore/snapd/pull/8304

But only for zoom?!

And I'm not sure of the nature of the fix or who would get it.

This may reflect the latest inclusions (see line 95 or so) ? It shows
"apt" being included:

https://github.com/snapcore/snapd/blob/master/tests/main/xdg-
open/task.yaml

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

Title:
Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
Triaged
Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:

https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

snapd has a hard-coded list of allowed URL schemes. Currently that is
limited to "http", "https", "mailto", "snap".

We have a number of applications in the store which are trying to use
protocol handlers outside this scope and break when that's not
possible.

e.g.

Telegram Desktop: tg:/
Github Desktop: git:/
IRCCloud Desktop: irc:/

These are the ones I know of, others may also be affected. Can we
please at least expand the list to those that we know of, and perhaps
research other popular protocol handlers?

Ideally we wouldn't have a whitelist, because this delays our ability
to land new applications with as-yet unknown url schemes.

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

[Desktop-packages] [Bug 1868543] Re: New upstream version 68.6.0 available, fixes security vulnerabilities

** Branch linked: lp:thunderbird

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

Title:
  New upstream version 68.6.0 available, fixes security vulnerabilities

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  There is a new upstream version 68.6.0 available which fixes several medium 
and high risk security vulnerabilities.
  Please release a new Ubuntu package ASAP - see the Debian project, which has 
already done so.

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

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

[Desktop-packages] [Bug 1868561] Re: Xorg Crash on login

Here's the bt only.

** Attachment added: "xorg.crash.bt_only.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868561/+attachment/5340610/+files/xorg.crash.bt_only.txt

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

Title:
  Xorg Crash on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1868561] Re: Xorg Crash on login

Also, the latest mainline kernel didn't fix the problem:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc7/linux-modules-5.6.0-050600rc7-generic_5.6.0-050600rc7.202003230230_amd64.deb

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

Title:
  Xorg Crash on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

I'm experiencing the same issue with a Philips SHB7250 headset on a fully 
up-to-date 20.04.
This headset used to work fine until about a couple of weeks ago (I have been 
running 20.04 since the early days, so it's a recent regression).

Switching back and forth between sinks in g-c-c doesn't make the issue
go away, though. Sound output is always through the laptop built-in
speakers. I have also tried resuming the corresponding sink (it's marked
SUSPENDEND) and setting it the default using pactl, to no avail.

** Tags added: rls-ff-incoming

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

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

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

2020-03-23 Thread Marc Deslauriers

** Tags removed: verification-needed verification-needed-disco

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Won't Fix
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868561] Re: Xorg Crash on login

Here's the backtrace.

If I run:

sudo gdb --args /usr/lib/xorg/Xorg -nolisten tcp :1 vt2  -keeptty
-logfile xorg.log

on terminal and on another terminal run:

export DISPLAY=:1
gnome-session

it crashes and the backtrace full is attached.

But if I just run:

export DISPLAY=:1
gnome-shell

it doesn't crash but loads gnome-shell.

So the problem only shows up in gnome-session, that's probably why gdm3
starts fine, but when logging in as a user, it crashes.


** Attachment added: "xorg.crash.bt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868561/+attachment/5340608/+files/xorg.crash.bt

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

Title:
  Xorg Crash on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1868543] Re: New upstream version 68.6.0 available, fixes security vulnerabilities

** Changed in: thunderbird (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  New upstream version 68.6.0 available, fixes security vulnerabilities

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  There is a new upstream version 68.6.0 available which fixes several medium 
and high risk security vulnerabilities.
  Please release a new Ubuntu package ASAP - see the Debian project, which has 
already done so.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-03-23 Thread Julie Brandon

Hate to be another +1 but, any updates on this. This is quite a major
issue for real world use right now.

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

Title:
Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
Triaged
Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:

https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

snapd has a hard-coded list of allowed URL schemes. Currently that is
limited to "http", "https", "mailto", "snap".

We have a number of applications in the store which are trying to use
protocol handlers outside this scope and break when that's not
possible.

e.g.

Telegram Desktop: tg:/
Github Desktop: git:/
IRCCloud Desktop: irc:/

These are the ones I know of, others may also be affected. Can we
please at least expand the list to those that we know of, and perhaps
research other popular protocol handlers?

Ideally we wouldn't have a whitelist, because this delays our ability
to land new applications with as-yet unknown url schemes.

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

[Desktop-packages] [Bug 1868561] Re: Xorg Crash on login

Here's the user xorg log that shows the crash

** Attachment added: "Xorg.1.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868561/+attachment/5340509/+files/Xorg.1.log

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

Title:
  Xorg Crash on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]

2020-03-23 Thread Timo Aaltonen

This is because gallium drivers no longer forcefully disable 10 bpc (by
a distro patch), but if our mutter won't gain support for 10bpc, then
the patch should probably be reapplied.

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

Title:
  Clients fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784)
  [DRM_FORMAT_XRGB2101010]

Status in Mesa:
  Unknown
Status in MPV:
  Unknown
Status in Mutter:
  Unknown
Status in mesa-demos package in Ubuntu:
  New
Status in mpv package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info: 
  fragment shader info: 
  info: 
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1)
  [3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1)
  [3104437.125]

[Desktop-packages] [Bug 1868561] [NEW] Xorg Crash on login

Public bug reported:

Upgraded to focal development and rebooted. When I try to login, it
doesn't allow me. Looking at the logs, there's a crash.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
Date: Mon Mar 23 21:44:35 2020
DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
 88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
 rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
ExtraDebuggingInterest: Yes
GraphicsCard:
 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
   Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
MachineType: Supermicro Super Server
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0b
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A2SDi-16C-HLN4F
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Super Server
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal regression reproducible third-party-packages 
ubuntu uec-images

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

Title:
  Xorg Crash on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx:

[Desktop-packages] [Bug 1824118] Re: wpa_supplicant executes hundreds of failed atempts in a second

2020-03-23 Thread Alexander Rehbein

Same here, trying to share my USB tethered internet connection.

```
Mär 23 14:35:18 are-TP-X240 NetworkManager[5202]:   [1584970518.6359] 
manager: startup complete
Mär 23 14:35:18 are-TP-X240 systemd[1]: Started Network Manager Wait Online.
-- Subject: Unit NetworkManager-wait-online.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit NetworkManager-wait-online.service has finished starting up.
-- 
-- The start-up result is RESULT.
Mär 23 14:35:18 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:19 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:20 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:21 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:22 are-TP-X240 wpa_supplicant[927]: wlp3s0: AP-STA-CONNECTED 
00:16:ea:e5:68:70
Mär 23 14:35:22 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:23 are-TP-X240 dnsmasq-dhcp[5295]: DHCPREQUEST(wlp3s0) 10.42.0.239 
00:16:ea:e5:68:70
Mär 23 14:35:23 are-TP-X240 dnsmasq-dhcp[5295]: DHCPACK(wlp3s0) 10.42.0.239 
00:16:ea:e5:68:70 are-fokus-x200
Mär 23 14:35:23 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:24 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1
Mär 23 14:35:25 are-TP-X240 wpa_supplicant[927]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-95 retry=1

```

and it goes on forever.

The hotspot seems to be working fine, otherwise.

```
$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
```

```
$ wpa_supplicant -v
wpa_supplicant v2.6
Copyright (c) 2003-2016, Jouni Malinen  and contributors
```

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

Title:
  wpa_supplicant executes hundreds of failed atempts in a second

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  I use my computer to create a wifi hotspot to my local wired network.
  Whenever I do so I get short hangs that last for about a second every few 
minutes.
  Looking into the syslog in /var/log/syslog I get the output at the end of 
this message.
  I have tried my best to look for an answer to this bug, but the reported bugs 
on wpa_supplicant are
  all for other ret codes.

  Best,

  Victor

  Apr 10 10:54:40 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:55:13 Amaterasu wpa_supplicant[1048]: message repeated 33 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Activating via systemd: service name='org.gnome.evince.Daemon' 
unit='evince.service' requested by ':1.413' (uid=1000 pid=6414 comm="emacs 
lib/legacy/uv_check.f90 " label="unconfined")
  Apr 10 10:55:14 Amaterasu systemd[1695]: Starting Evince document viewer...
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Successfully activated service 'org.gnome.evince.Daemon'
  Apr 10 10:55:14 Amaterasu systemd[1695]: Started Evince document viewer.
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Activating service name='org.x.reader.Daemon' requested by ':1.413' (uid=1000 
pid=6414 comm="emacs lib/legacy/uv_check.f90 " label="unconfined")
  Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] 
Successfully activated service 'org.x.reader.Daemon'
  Apr 10 10:55:14 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:55:37 Amaterasu wpa_supplicant[1048]: message repeated 23 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:55:38 Amaterasu dbus-daemon[1748]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" 
member="Notify" mask="send" name="org.freedesktop.Notifications" pid=2263 
label="snap.spotify.spotify"
  Apr 10 10:55:38 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:57:39 Amaterasu wpa_supplicant[1048]: message repeated 120 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr 10 10:57:40 Amaterasu dbus-daemon[1748]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" 
path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" 
member="Notify" mask="send" name="org.freedesktop.Notifications" pid=2263 
label="snap.spotify.spotify"
  Apr 10 10:57:40 Amaterasu wpa_supplicant[1048]: wlp3s0: 
CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
  Apr 10 10:58:15 Amaterasu wpa_supplicant[1048]: message repeated 35 times: [ 
wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
  Apr

[Desktop-packages] [Bug 1866721] Re: Unable to use microphone in chrome

2020-03-23 Thread Fidel Ramos

The workaround that Florian posted works for me, thank you. And thank
you Olivier for bringing it upstream.

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

Title:
  Unable to use microphone in chrome

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Running Ubuntu 19.10 and the chromium-browser
  79.0.3945.79-0ubuntu0.19.10.2 package

  I am unable to use my microphone with sites that support it, such as
  discord.

  I can hear audio from websites like Youtube, but sites that want to
  use my microphone fail to do so, even though I give permission.

  I've tested with Hubs by Mozilla, Discord and
  https://www.onlinemictest.com/

  All three properly prompt for permission, but then act as if I refused
  to give it when choose "allow".  If I start chrome from the command
  line, when this happens I see this in the output

  [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation
  is nullptr.

  The https://www.onlinemictest.com/ reports "Microphone not authorized.
  Please check your media permissions settings."

  My microphone works fine in Firefox.

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

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

[Desktop-packages] [Bug 1863506] Re: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1'

2020-03-23 Thread Peter John Allebone

Thanks for fixing this, it is appreciated.

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

Title:
  mate-session[1159]: WARNING: Could not parse desktop file
  /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized
  desktop file Version '1.1'

Status in Déjà Dup:
  Fix Committed
Status in deja-dup package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Remove `~/.xsession-errors` and then login
  3. Open `~/.xsession-errors`

  Expected results:
  * `~/.xsession-errors` do not have warnings

  Actual results:
  * `~/.xsession-errors` have warnings:

  mate-session[1159]: WARNING: Could not parse desktop file
  /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized
  desktop file Version '1.1'

  mate-session[1159]: WARNING: could not read
  /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.5-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Feb 16 21:49:08 2020
  InstallationDate: Installed on 2020-02-16 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200216)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868543] Re: New upstream version 68.6.0 available, fixes security vulnerabilities

2020-03-23 Thread Sebastien Bacher

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

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

** Tags added: upgrade-software-version

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  New upstream version 68.6.0 available, fixes security vulnerabilities

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  There is a new upstream version 68.6.0 available which fixes several medium 
and high risk security vulnerabilities.
  Please release a new Ubuntu package ASAP - see the Debian project, which has 
already done so.

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

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

[Desktop-packages] [Bug 1868544] Re: Missing wireless network interface after kernel 5.3.0-43 installed

2020-03-23 Thread Sebastien Bacher

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Missing wireless network interface after kernel 5.3.0-43 installed

Status in linux package in Ubuntu:
  New

Bug description:
  I apologize if this is a repeat of the bug I filed a couple of days
  ago, but I don't see on launchpad that it shows I filed a bug, so I am
  filling another.  Also didn't know what to file the bug under so I
  chose network-manager.  It appears to be a bug with kernel 5.3.0-43.

  I updated to latest kernel: initrd.img-5.3.0-43-generic and find that my 
network is in airplane mode. ifconfig shows there is no wireless interface 
setup. When I go back to kernel 5.3.0-42 everything is working correctly. I am 
using an HP laptop.
  I can see the wireless network controller with lshw:

  lshw -C network
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: eno1
 version: 15
 serial: b4:b6:86:e7:67:29
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 
link=yes multicast=yes port=MII speed=100Mbit/s
 resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff 
memory:fe90-fe903fff
*-network
 description: Network controller
 product: Dual Band Wireless-AC 3168NGW [Stone Peak]
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 version: 10
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=iwlwifi latency=0
 resources: irq:43 memory:fe80-fe801fff

  lspci |grep Network
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW 
[Stone Peak] (rev 10)

  iwconfig
  lo no wireless extensions.

  eno1 no wireless extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
  Uname: Linux 5.3.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  Date: Mon Mar 23 05:37:31 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-30 (479 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-11-29T22:07:37.505878
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   eno1ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
b6cda306-c004-3fd6-89b9-1be0460aa25d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1868546] Re: Missing volume icon + broken volume/brightness sliders

2020-03-23 Thread Minteck

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

** Attachment removed: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868546/+attachment/5340403/+files/GsettingsChanges.txt

** Attachment removed: "ShellJournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868546/+attachment/5340406/+files/ShellJournal.txt

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

Title:
  Missing volume icon + broken volume/brightness sliders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  First:
  On the status bar, there is no volume icon, just an empty space.
  The icon only appears on logout.

  Second:
  The volume and brightness sliders are broken, are always at 0 regardless to 
the real volume (set either using alternative software/desktop or using 
keyboard keys).
  When you change the volume using the sliders, it really changes the volume 
but keeps the slider at the value it was if you change the volume using another 
way.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
  Uname: Linux 5.4.0-18-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 12:24:18 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868546] Re: Missing volume icon + broken volume/brightness sliders

2020-03-23 Thread Paul White

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

** This bug has been marked a duplicate of bug 1865169
   volume and light not working in Gnome Shell 3.35

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

Title:
  Missing volume icon + broken volume/brightness sliders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  First:
  On the status bar, there is no volume icon, just an empty space.
  The icon only appears on logout.

  Second:
  The volume and brightness sliders are broken, are always at 0 regardless to 
the real volume (set either using alternative software/desktop or using 
keyboard keys).
  When you change the volume using the sliders, it really changes the volume 
but keeps the slider at the value it was if you change the volume using another 
way.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
  Uname: Linux 5.4.0-18-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 12:24:18 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868546] [NEW] Missing volume icon + broken volume/brightness sliders

2020-03-23 Thread Minteck

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

Public bug reported:

First:
On the status bar, there is no volume icon, just an empty space.
The icon only appears on logout.

Second:
The volume and brightness sliders are broken, are always at 0 regardless to the 
real volume (set either using alternative software/desktop or using keyboard 
keys).
When you change the volume using the sliders, it really changes the volume but 
keeps the slider at the value it was if you change the volume using another way.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
Uname: Linux 5.4.0-18-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 23 12:24:18 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-03-22 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot to explain the bug"
   
https://bugs.launchpad.net/bugs/1868546/+attachment/5340401/+files/Screenshot%20from%202020-03-23%2000-42-27.png

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

Title:
  Missing volume icon + broken volume/brightness sliders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  First:
  On the status bar, there is no volume icon, just an empty space.
  The icon only appears on logout.

  Second:
  The volume and brightness sliders are broken, are always at 0 regardless to 
the real volume (set either using alternative software/desktop or using 
keyboard keys).
  When you change the volume using the sliders, it really changes the volume 
but keeps the slider at the value it was if you change the volume using another 
way.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
  Uname: Linux 5.4.0-18-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 12:24:18 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868396] Re: crashes or freezes with nividia/xorg

2020-03-23 Thread SR

Sorry to spam, but with « crash », I mean non-responsive PC, not being
able to change terminal using key shortcuts, no ssh access, noisy fans.
No crash in /var/crash/.

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

Title:
  crashes or freezes with nividia/xorg

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have plugged in my Dell precision 5530 laptop a 4k HDMI screen.
  Using it with 200% zoom makes xorg crash.
  I have used proprietary 430, and changed to recommended proprietary 435 
nvidia driver.
  As the system was still very unstable (no to say unusable) I had a go with 
440 from ppa.
  I also ensured that my system was up to date doing a sudo apt-get update and 
upgrade. I was suprised to discover a few packages that needed an upgrade 
although I had previously used the Software Updater tool. Maybe I was doing 
something wrong.
  Anyway, with these updates and the newer 440 driver, I have successfully 
worked a day (sparsely) without problem, and using only 100% zoom.
  As a test, I decided to try to set the zoom to 200% (through devices > 
display, and I have only the external display enabled).
  After several minutes, I clicked on the « full screen » icon to maximize a 
shell, and the PC froze.
  It was so close to my change in the zoom ratio, that I suspect this is 
related.

  dmesg shew me that NVRM had a problem :
  [97501.301998] NVRM: GPU at PCI::01:00: 
GPU-dee28f75-4083-96a8-1a0b-491b6109101a
  [97501.302000] NVRM: Xid (PCI::01:00): 32, pid=493, Channel ID 0018 
intr 0004
  [97501.302134] NVRM: Xid (PCI::01:00): 32, pid=2052, Channel ID 0018 
intr 0020
  [97501.317307] NVRM: Xid (PCI::01:00): 69, pid=902, Class Error: ChId 
001b, Class 902d, Offset 0250, Data 55d3, ErrorCode 000c

  pid 493 is gone

  pid 2052 is xorg
  stan  2052  2050  1 mars20 tty200:25:38 /usr/lib/xorg/Xorg vt2 
-displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset 
-keeptty -verbose 3

  pid 902 is nvidia driver
  root   902 2  0 mars20 ?   00:02:59 [irq/163-nvidia]

  ppid 2052 is 2050 :
  stan  2050  2004  0 mars20 tty200:00:00 /usr/lib/gdm3/gdm-x-session 
--run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session 
--systemd --session=ubuntu

  After such an event, the previous days, the system became unstable,
  and I have got problems with other devices such as audio and network.

  If I run the manufacturer self-check test, everything is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  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: Sat Mar 21 18:36:53 2020
  DistUpgraded: 2019-11-04 11:06:46,434 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: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d]
 Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d]
  InstallationDate: Installed on 2019-04-26 (329 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Precision 5530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 
acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force 
drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 
mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-11-04 (138 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.

[Desktop-packages] [Bug 1868396] Re: crashes or freezes with nividia/xorg

2020-03-23 Thread SR

Another info : it crashed today with 100% zoom ratio.
Switching to intel drivers.

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

Title:
  crashes or freezes with nividia/xorg

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have plugged in my Dell precision 5530 laptop a 4k HDMI screen.
  Using it with 200% zoom makes xorg crash.
  I have used proprietary 430, and changed to recommended proprietary 435 
nvidia driver.
  As the system was still very unstable (no to say unusable) I had a go with 
440 from ppa.
  I also ensured that my system was up to date doing a sudo apt-get update and 
upgrade. I was suprised to discover a few packages that needed an upgrade 
although I had previously used the Software Updater tool. Maybe I was doing 
something wrong.
  Anyway, with these updates and the newer 440 driver, I have successfully 
worked a day (sparsely) without problem, and using only 100% zoom.
  As a test, I decided to try to set the zoom to 200% (through devices > 
display, and I have only the external display enabled).
  After several minutes, I clicked on the « full screen » icon to maximize a 
shell, and the PC froze.
  It was so close to my change in the zoom ratio, that I suspect this is 
related.

  dmesg shew me that NVRM had a problem :
  [97501.301998] NVRM: GPU at PCI::01:00: 
GPU-dee28f75-4083-96a8-1a0b-491b6109101a
  [97501.302000] NVRM: Xid (PCI::01:00): 32, pid=493, Channel ID 0018 
intr 0004
  [97501.302134] NVRM: Xid (PCI::01:00): 32, pid=2052, Channel ID 0018 
intr 0020
  [97501.317307] NVRM: Xid (PCI::01:00): 69, pid=902, Class Error: ChId 
001b, Class 902d, Offset 0250, Data 55d3, ErrorCode 000c

  pid 493 is gone

  pid 2052 is xorg
  stan  2052  2050  1 mars20 tty200:25:38 /usr/lib/xorg/Xorg vt2 
-displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset 
-keeptty -verbose 3

  pid 902 is nvidia driver
  root   902 2  0 mars20 ?   00:02:59 [irq/163-nvidia]

  ppid 2052 is 2050 :
  stan  2050  2004  0 mars20 tty200:00:00 /usr/lib/gdm3/gdm-x-session 
--run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session 
--systemd --session=ubuntu

  After such an event, the previous days, the system became unstable,
  and I have got problems with other devices such as audio and network.

  If I run the manufacturer self-check test, everything is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  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: Sat Mar 21 18:36:53 2020
  DistUpgraded: 2019-11-04 11:06:46,434 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: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d]
 Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d]
  InstallationDate: Installed on 2019-04-26 (329 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Precision 5530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 
acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force 
drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 
mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-11-04 (138 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0N0DK2
  dmi.board.vendor: Dell Inc.
  dmi.board.version:

[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes

I have done:
sudo apt remove gnome-shell-extension-*
apt-cache policy gnome*
reboot

Problem still exists.

** Attachment added: "apt-cache policy gnome* after apt remove ..."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868480/+attachment/5340400/+files/aagnome.txt

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

Title:
  gnome mouse (trackpad ) and keyboard freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad ist working since years without this problem. Since last
  Friday, after a reboot, I got mouse and keyboard freezed. I reboot
  multiple time to analyse the problem. Google as a friend shows me that
  some problems are reported and I learned a lot but no solution for me.

  I find out that the problem occurs after 3 to 10 minutes of mouse and 
keyboard inactivity the mouse and keyboard freezes. If I always working with 
the mouse or the keyboard no freeze, still for hours. The problem is still 
reproducible by mouse and keyboard inactivity. This I figured out:
  - Strg+Alt+Del helps but all work are lost
  - klicking application (multiple points) entering some character an klicking 
application again helps some time
  - closing the lid and opening it after about 30 seconds helps, but requires 
password.

  I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and
  reboot. Login and wait till freeze, wait, close lid, and open lid.

  I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found 
that every freeze time there is an error:
  Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for 
signal: StatusChanged: Error: value is out of range for Argument 'interval' 
(type guint32)

timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13

  
  Result of uname -a
  Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Result of gnome-shell --version
  GNOME Shell 3.28.4

  apt-cache policy gnome* is in the attached file

  Any thing else I can deliver to solve the problem

  Thanks and regards Rainer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 16:25:39 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  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/1868480/+subscriptions

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

[Desktop-packages] [Bug 1868544] [NEW] Missing wireless network interface after kernel 5.3.0-43 installed

2020-03-23 Thread Rustin Schenk

Public bug reported:

I apologize if this is a repeat of the bug I filed a couple of days ago,
but I don't see on launchpad that it shows I filed a bug, so I am
filling another.  Also didn't know what to file the bug under so I chose
network-manager.  It appears to be a bug with kernel 5.3.0-43.

I updated to latest kernel: initrd.img-5.3.0-43-generic and find that my 
network is in airplane mode. ifconfig shows there is no wireless interface 
setup. When I go back to kernel 5.3.0-42 everything is working correctly. I am 
using an HP laptop.
I can see the wireless network controller with lshw:

lshw -C network
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: eno1
   version: 15
   serial: b4:b6:86:e7:67:29
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full 
firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 link=yes 
multicast=yes port=MII speed=100Mbit/s
   resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff 
memory:fe90-fe903fff
  *-network
   description: Network controller
   product: Dual Band Wireless-AC 3168NGW [Stone Peak]
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   version: 10
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: driver=iwlwifi latency=0
   resources: irq:43 memory:fe80-fe801fff

lspci |grep Network
03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW 
[Stone Peak] (rev 10)

iwconfig
lo no wireless extensions.

eno1 no wireless extensions.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.4-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
Uname: Linux 5.3.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.7
Architecture: amd64
Date: Mon Mar 23 05:37:31 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-11-30 (479 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
IwConfig:
 eno1  no wireless extensions.
 
 lono wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
 [connection]
 wifi.powersave = 2
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-11-29T22:07:37.505878
nmcli-dev:
 DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
 eno1ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
b6cda306-c004-3fd6-89b9-1be0460aa25d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug eoan

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

Title:
  Missing wireless network interface after kernel 5.3.0-43 installed

Status in network-manager package in Ubuntu:
  New

Bug description:
  I apologize if this is a repeat of the bug I filed a couple of days
  ago, but I don't see on launchpad that it shows I filed a bug, so I am
  filling another.  Also didn't know what to file the bug under so I
  chose network-manager.  It appears to be a bug with kernel 5.3.0-43.

  I updated to latest kernel: initrd.img-5.3.0-43-generic and find that my 
network is in airplane mode. ifconfig shows there is no wireless interface 
setup. When I go back to kernel 5.3.0-42 everything is working

[Desktop-packages] [Bug 1868543] [NEW] New upstream version 68.6.0 available, fixes security vulnerabilities

2020-03-23 Thread Juri Haberland

*** This bug is a security vulnerability ***

Public security bug reported:

There is a new upstream version 68.6.0 available which fixes several medium and 
high risk security vulnerabilities.
Please release a new Ubuntu package ASAP - see the Debian project, which has 
already done so.

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

** Information type changed from Private Security to Public Security

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

Title:
  New upstream version 68.6.0 available, fixes security vulnerabilities

Status in thunderbird package in Ubuntu:
  New

Bug description:
  There is a new upstream version 68.6.0 available which fixes several medium 
and high risk security vulnerabilities.
  Please release a new Ubuntu package ASAP - see the Debian project, which has 
already done so.

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

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

[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes

That attachment shows a number of packages named 'gnome-shell-
extension-*' as still installed.

Please uninstall them using:  apt remove ...

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

Title:
  gnome mouse (trackpad ) and keyboard freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad ist working since years without this problem. Since last
  Friday, after a reboot, I got mouse and keyboard freezed. I reboot
  multiple time to analyse the problem. Google as a friend shows me that
  some problems are reported and I learned a lot but no solution for me.

  I find out that the problem occurs after 3 to 10 minutes of mouse and 
keyboard inactivity the mouse and keyboard freezes. If I always working with 
the mouse or the keyboard no freeze, still for hours. The problem is still 
reproducible by mouse and keyboard inactivity. This I figured out:
  - Strg+Alt+Del helps but all work are lost
  - klicking application (multiple points) entering some character an klicking 
application again helps some time
  - closing the lid and opening it after about 30 seconds helps, but requires 
password.

  I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and
  reboot. Login and wait till freeze, wait, close lid, and open lid.

  I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found 
that every freeze time there is an error:
  Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for 
signal: StatusChanged: Error: value is out of range for Argument 'interval' 
(type guint32)

timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13

  
  Result of uname -a
  Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Result of gnome-shell --version
  GNOME Shell 3.28.4

  apt-cache policy gnome* is in the attached file

  Any thing else I can deliver to solve the problem

  Thanks and regards Rainer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 16:25:39 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  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/1868480/+subscriptions

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

[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes

I uninstalled all extensions under https://extensions.gnome.org/local/
Check /usr/share/gnome-shell/extensions Empty
Check ~/.local/share/gnome-shell/extensions Empty
Reboot
Error still exists!!!

Is more info needed?

** Attachment added: "apt-cache policy gnome* after uninstall extensions"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868480/+attachment/5340388/+files/aagnome.txt

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

Title:
  gnome mouse (trackpad ) and keyboard freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad ist working since years without this problem. Since last
  Friday, after a reboot, I got mouse and keyboard freezed. I reboot
  multiple time to analyse the problem. Google as a friend shows me that
  some problems are reported and I learned a lot but no solution for me.

  I find out that the problem occurs after 3 to 10 minutes of mouse and 
keyboard inactivity the mouse and keyboard freezes. If I always working with 
the mouse or the keyboard no freeze, still for hours. The problem is still 
reproducible by mouse and keyboard inactivity. This I figured out:
  - Strg+Alt+Del helps but all work are lost
  - klicking application (multiple points) entering some character an klicking 
application again helps some time
  - closing the lid and opening it after about 30 seconds helps, but requires 
password.

  I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and
  reboot. Login and wait till freeze, wait, close lid, and open lid.

  I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found 
that every freeze time there is an error:
  Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for 
signal: StatusChanged: Error: value is out of range for Argument 'interval' 
(type guint32)

timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13

  
  Result of uname -a
  Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Result of gnome-shell --version
  GNOME Shell 3.28.4

  apt-cache policy gnome* is in the attached file

  Any thing else I can deliver to solve the problem

  Thanks and regards Rainer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 16:25:39 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  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/1868480/+subscriptions

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

[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2020-03-23 Thread Kiruahxh

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

It affects me too on Ubuntu 19.04 using OpenConnect VPN

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes

To #4 
the newest chrash file is 4 day old! So it can't be a crash which cause the 
problem because yesterday I documented every thing I known about the error.

To #3 I start working on it. Came back soon.

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

Title:
  gnome mouse (trackpad ) and keyboard freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad ist working since years without this problem. Since last
  Friday, after a reboot, I got mouse and keyboard freezed. I reboot
  multiple time to analyse the problem. Google as a friend shows me that
  some problems are reported and I learned a lot but no solution for me.

  I find out that the problem occurs after 3 to 10 minutes of mouse and 
keyboard inactivity the mouse and keyboard freezes. If I always working with 
the mouse or the keyboard no freeze, still for hours. The problem is still 
reproducible by mouse and keyboard inactivity. This I figured out:
  - Strg+Alt+Del helps but all work are lost
  - klicking application (multiple points) entering some character an klicking 
application again helps some time
  - closing the lid and opening it after about 30 seconds helps, but requires 
password.

  I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and
  reboot. Login and wait till freeze, wait, close lid, and open lid.

  I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found 
that every freeze time there is an error:
  Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for 
signal: StatusChanged: Error: value is out of range for Argument 'interval' 
(type guint32)

timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13

  
  Result of uname -a
  Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Result of gnome-shell --version
  GNOME Shell 3.28.4

  apt-cache policy gnome* is in the attached file

  Any thing else I can deliver to solve the problem

  Thanks and regards Rainer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 16:25:39 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  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/1868480/+subscriptions

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

[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2020-03-23 Thread Harald Hannelius

I too had this problem in 18.04, and now in 20.04. I am unable to use
the headphones for conferencing.

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

Title:
  Annoying "call from" message when connecting Bose devices

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

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Desktop-packages] [Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)

Sounds related: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2467

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2467
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2467

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

Title:
  gnome-shell freezes and continuously logs "JS ERROR: TypeError: null
  has no properties" in _addWindowEffect from vfunc_show (both in
  closeDialog.js)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I was closing the dialog of the "software and updates" tools (I was
  checking the repositories and ppa), but the entire desktop went into
  freeze, no mouse movement, at the click no action, I pressed the keys
  "ctrl + alt + f3 "and I went into a tty session, from there I recorded
  the logs via:" journalctl -f> log ", and I restarted.

  This is one part of the log, but it seems to repeat itself, I have
  attached a file with a longer log.

  -- Logs begin at Tue 2019-02-19 00:29:40 CET. --
  ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no 
properties

_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13

vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
  ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no 
properties

_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13

vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 14:51:01 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (190 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1867133] Re: Ubuntu logo vanishes and fades back in (with a slightly different size) on gdm start

To complicate matters, the fix for comment #3 has now landed in upstream
gnome-shell 3.36.1. So if we want we can say "Won't Fix" to the now
redundant Plymouth fix in comment #7. Or land both because it's more
robust to have two fixes (both would have to regress before you noticed
a regression).

This bug still needs a second gnome-shell fix though, the main fix which
is comment #13.

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

Title:
  Ubuntu logo vanishes and fades back in (with a slightly different
  size) on gdm start

Status in gnome-shell package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  In Progress

Bug description:
  spinner theme flickers Ubuntu logo on gdm transition

  At the end of boot, spinner disappears and Ubuntu logo remains 100%
  opacity white on screen.

  Then GDM starts, and performs a fade-in animation of background
  gradient, and fade-ins Ubuntu logo.

  This results in visual flicker, where Ubuntu logo temporarily
  dissappears and instantly fades back in.

  This should be more smooth. For example, gdm could paint ubuntu logo
  at 100% opacity white without animation, whilst everything else fades-
  in. Or we could fade out ubuntu-logo in the spinner plymouth theme,
  such that on boot it is a tasteful pulsating logo that fades out, and
  back in.

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

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

[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

Please also remember to keep all extensions uninstalled while
investigating leaks. We don't want to spend time finding leaks in
extensions unless they happen to be the default Ubuntu ones.

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Many times after logging in gnome-shell uses 600-800MB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200MB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 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/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions

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

[Desktop-packages] [Bug 1868532] Re: firefox

Please open a Terminal window and type:

  firefox

What do you see?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  firefox

Status in Ubuntu:
  Incomplete

Bug description:
  can not launch

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Mar 23 08:26:09 2020
  DistUpgraded: 2019-12-31 11:19:56,768 DEBUG /openCache(), new cache size 62521
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.34, 4.15.0-89-generic, i686: installed
   virtualbox, 5.2.34, 4.15.0-91-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7420G] [103c:1849]
  InstallationDate: Installed on 2018-02-06 (775 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=118a31ba-5396-4a6e-9870-e70737b32393 ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-12-31 (82 days ago)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd09/18/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088011305D1620100:rvnHewlett-Packard:rn1849:rvr57.2E:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 088011305D1620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Dec 27 08:18:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes

To #4 
the newest chrash file is 4 day old! So it can't be a crash which cause the 
problem because yesterday I documented every thing I known about the error.

To #3 I start working on it. Came back soon.

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

Title:
  gnome mouse (trackpad ) and keyboard freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad ist working since years without this problem. Since last
  Friday, after a reboot, I got mouse and keyboard freezed. I reboot
  multiple time to analyse the problem. Google as a friend shows me that
  some problems are reported and I learned a lot but no solution for me.

  I find out that the problem occurs after 3 to 10 minutes of mouse and 
keyboard inactivity the mouse and keyboard freezes. If I always working with 
the mouse or the keyboard no freeze, still for hours. The problem is still 
reproducible by mouse and keyboard inactivity. This I figured out:
  - Strg+Alt+Del helps but all work are lost
  - klicking application (multiple points) entering some character an klicking 
application again helps some time
  - closing the lid and opening it after about 30 seconds helps, but requires 
password.

  I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and
  reboot. Login and wait till freeze, wait, close lid, and open lid.

  I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found 
that every freeze time there is an error:
  Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for 
signal: StatusChanged: Error: value is out of range for Argument 'interval' 
(type guint32)

timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13

  
  Result of uname -a
  Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Result of gnome-shell --version
  GNOME Shell 3.28.4

  apt-cache policy gnome* is in the attached file

  Any thing else I can deliver to solve the problem

  Thanks and regards Rainer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 16:25:39 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  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/1868480/+subscriptions

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

[Desktop-packages] [Bug 1868529] Re: Stretched picture or pdf preview icon on desktop

2020-03-23 Thread Igor Zubarev

** Description changed:

  After upgrade to 20.04 desktop previews of pictures and documents became
- stretched. See attach pic
+ stretched. The regular previews in Nautilus have normal sizes. See
+ attach pic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After upgrade to 20.04 desktop previews of pictures and documents became
  stretched. The regular previews in Nautilus have normal sizes. See
- attach pic
+ attached pic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Stretched picture or pdf preview icon on desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  After upgrade to 20.04 desktop previews of pictures and documents
  became stretched. The regular previews in Nautilus have normal sizes.
  See attached pic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

It would be hard to prove that's a bug at all, or just the natural
resident set size that the gnome-shell process settles at until the next
garbage collection. And you can't predict or know when that will happen.

Generally speaking for gnome-shell I would say anything under 500MB
might not be a leak. It might just be "normal" JavaScript garbage
accumulation. Or it might be an asymptotic leak. Either way, not yet a
priority.

While we'd all like gnome-shell to always use less memory, whether this
is a bug yet particularly in 20.04 where the memory usage is lower, is
unclear. If you are able to repeat some steps many times and get 20.04
past 500MB and then 1000MB then I would consider it a leak worth
investigating.


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

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Many times after logging in gnome-shell uses 600-800MB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200MB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 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/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions

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

[Desktop-packages] [Bug 1868532] [NEW] firefox

2020-03-23 Thread adrianbianchi

Public bug reported:

can not launch

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Mar 23 08:26:09 2020
DistUpgraded: 2019-12-31 11:19:56,768 DEBUG /openCache(), new cache size 62521
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.34, 4.15.0-89-generic, i686: installed
 virtualbox, 5.2.34, 4.15.0-91-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7420G] [103c:1849]
InstallationDate: Installed on 2018-02-06 (775 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=118a31ba-5396-4a6e-9870-e70737b32393 ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-12-31 (82 days ago)
dmi.bios.date: 09/18/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1849
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.2E
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd09/18/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088011305D1620100:rvnHewlett-Packard:rn1849:rvr57.2E:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 088011305D1620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Dec 27 08:18:32 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: apport-bug bionic i386 third-party-packages ubuntu

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

Title:
  firefox

Status in xorg package in Ubuntu:
  New

Bug description:
  can not launch

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Mar 23 08:26:09 2020
  DistUpgraded: 2019-12-31 11:19:56,768 DEBUG /openCache(), new cache size 62521
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.34, 4.15.0-89-generic, i686: installed
   virtualbox, 5.2.34, 4.15.0-91-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7420G] [103c:1849]
  InstallationDate: Installed on 2018-02-06 (775 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=118a31ba-5396-4a6e-9870-e70737b32393 ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-12-31 (82 days ago)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard

[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen