[Desktop-packages] [Bug 2061242] Re: gnome-shell crashes randomly

[Roman]

Hi Brian, my report once again got "invalid core dump" message.
Strangely, now it took 2 weeks instead of 1 hour.

We've previously talked in
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2058693,
you said to attach a .crash file and make report private, which I did.
Can you access the report now? If not, how can I add you to it?

** Information type changed from Private to Public

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

Title:
  gnome-shell crashes randomly

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Don't yet understand what triggers it, maybe monitor
  connect/disconnect.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu4
  Uname: Linux 6.9.0-rc2 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 20:29:01 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2024-02-14 (60 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  ProcAttrCurrent: Error: [Errno 22] Invalid argument
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu6
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin ollama plugdev sudo users

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


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

[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Temporary bypass:
wget 
http://mirrors.kernel.org/ubuntu/pool/main/n/network-manager/network-manager_1.45.90-1ubuntu1_amd64.deb
dpkg --force-all -i network-manager_1.45.90-1ubuntu1_amd64.deb

dpkg output on my system:
Preparing to unpack network-manager_1.45.90-1ubuntu1_amd64.deb ...
Unpacking network-manager (1.45.90-1ubuntu1) over (1.45.90-1ubuntu1) ...
dpkg: network-manager: dependency problems, but configuring anyway as you 
requested:
 network-manager depends on libnm0 (= 1.45.90-1ubuntu1); however:
  Version of libnm0:amd64 on system is 1.45.90-1ubuntu3.
Setting up network-manager (1.45.90-1ubuntu1) ...
...

After that everything works fine.

Did the same with network-manager-openvpn and network-manager-openvpn-
gnome to bring back VPN, also works.

Btw, after full-upgrade I have a ton (114) of "not gonna be installed"
packages in apt output because some libs are missing from repos, seems
something went wrong when uploading new packages.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


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

[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Yeah, I guess making a full-upgrade instead of upgrade was a bad idea :)

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


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

[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Guess it uninstalls network-manager to install new version but new
version can't be installed because it depends on libnetplan1 which is
missing from repos.

https://packages.ubuntu.com/noble/network-manager currently shows
[depends on] libnetplan1 (>= 0.106)
Package not available 

You can't simply install previous version 1.45.90-1ubuntu1, which still
shows in `apt show network-manager`, because its dependency libnm0 of
the same version is already missing from repos.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


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

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

[Roman]

** Changed in: cups-browsed (Ubuntu)
   Status: Invalid => New

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

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

Status in cups-browsed package in Ubuntu:
  New

Bug description:
  Triggered after `apt upgrade`, don't know why, I don't even have any
  printers installed

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: cups-browsed 2.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [18/Mar/2024:16:28:04 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Kyocera_ECOSYS_M5526cdn-Gray..\' already exists
   W [18/Mar/2024:16:28:04 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Kyocera_ECOSYS_M5526cdn-DeviceN..\' already exists
  Date: Mon Mar 18 16:28:09 2024
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2024-02-14 (34 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  JournalErrors:
   Mar 18 16:28:12 hostname systemd[1]: cups-browsed.service: Main process 
exited, code=dumped, status=11/SEGV
   Mar 18 16:28:12 hostname systemd[1]: cups-browsed.service: Failed with 
result 'core-dump'.
   Mar 18 16:28:12 hostname system-crash-no[445844]: 
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 
'GDK_IS_WAYLAND_WINDOW (window)' failed
  Lpstat:
   device for Kyocera_ECOSYS_M5521cdn: implicitclass://Kyocera_ECOSYS_M5521cdn/
   device for Kyocera_ECOSYS_M5526cdn: implicitclass://Kyocera_ECOSYS_M5526cdn/
   device for RICOH_IM_C3010_5838798EBA01: 
implicitclass://RICOH_IM_C3010_5838798EBA01/
  MachineType: Micro-Star International Co., Ltd. Prestige 16 AI Evo B1MG
  Papersize: a4
  PpdFiles:
   Kyocera_ECOSYS_M5521cdn: ECOSYS M5521cdn, driverless, 2.0.0
   RICOH_IM_C3010_5838798EBA01: RICOH IM C3010 PS3, driverless, 2.0.0
   Kyocera_ECOSYS_M5526cdn: ECOSYS M5526cdn, driverless, 2.0.0
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash mitigations=off 
transparent_hugepage=always iommu=pt intel_iommu=on vt.handoff=7
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'Error:'
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: cups-browsed
  StacktraceTop:
   httpAddrFamily () from /lib/x86_64-linux-gnu/libcups.so.2
   httpAddrConnect2 () from /lib/x86_64-linux-gnu/libcups.so.2
   httpReconnect2 () from /lib/x86_64-linux-gnu/libcups.so.2
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   cupsSendRequest () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cups-browsed crashed with SIGSEGV in httpAddrFamily()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 11/03/2023
  dmi.bios.release: 1.6
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E15A1IMS.106
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-15A1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15A1IMS.106:bd11/03/2023:br1.6:svnMicro-StarInternationalCo.,Ltd.:pnPrestige16AIEvoB1MG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15A1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku15A1.1:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 16 AI Evo B1MG
  dmi.product.sku: 15A1.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  separator:

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


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

[Desktop-packages] [Bug 2058693] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Roman]

All reports from my machine are getting this "core dump is invalid"
messages, why? It is frustrating when you try to properly report bugs
just to get them automatically closed as invalid.

Also seems that this robot automatically removes dumps so you can't even
see them afterwards?

I tried to contact Brian via email without respond, let's try ping him
here somehow - not sure how this is done properly.

** Information type changed from Private to Public

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

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  Uname: Linux 6.8.1 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 20 23:12:46 2024
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2024-02-14 (37 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcAttrCurrent: Error: [Errno 22] Invalid argument
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  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: 
2024-02-18T15:43:08.117195
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

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


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

[Desktop-packages] [Bug 2058120] Re: file-roller crashed with SIGSEGV in gtk_widget_get_screen()

[Roman]

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

looks like the same bug

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1428619
   file-roller crashed with SIGSEGV in gdk_window_is_destroyed()

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

Title:
  file-roller crashed with SIGSEGV in gtk_widget_get_screen()

Status in file-roller package in Ubuntu:
  Invalid

Bug description:
  I saw https://bugs.launchpad.net/bugs/1428619, created a new bug to
  not lose my bug info and because that bug was last updated 8 years
  ago.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: file-roller 43.1-1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 22:21:41 2024
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2024-02-14 (32 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  ProcAttrCurrent: firefox (unconfined)
  ProcCmdline: /usr/bin/file-roller /home/username/Downloads/handout.tar.zst
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x75b8b4f5fcef:mov0xd0(%rax),%rbx
   PC (0x75b8b4f5fcef) ok
   source "0xd0(%rax)" (0x75b800d1) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: file-roller
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_widget_get_screen () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_widget_get_settings () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: file-roller crashed with SIGSEGV in gtk_widget_get_screen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sudo users
  separator:

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


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

[Desktop-packages] [Bug 1428619] Re: file-roller crashed with SIGSEGV in gdk_window_is_destroyed()

[Roman]

Got this triggered today, see
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2058120

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

Title:
  file-roller crashed with SIGSEGV in gdk_window_is_destroyed()

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: file-roller 3.14.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Thu Mar  5 08:47:07 2015
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2014-10-24 (131 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: file-roller /home/phoenix/Descargas/134823-radio\ tray\ 
mono.tar.gz
  SegvAnalysis:
   Segfault happened at: 0x7f1171eb7490 :  movzbl 
0x92(%rdi),%eax
   PC (0x7f1171eb7490) ok
   source "0x92(%rdi)" (0x0093) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   gdk_window_is_destroyed () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gtk_get_event_widget () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
  Title: file-roller crashed with SIGSEGV in gdk_window_is_destroyed()
  UpgradeStatus: Upgraded to vivid on 2015-01-05 (58 days ago)
  UserGroups:

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


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

[Desktop-packages] [Bug 2056506] Re: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)]

[Roman]

You are right, sorry. I rebooted the machine because gnome got stuck,
got a "do you want to send crash info", and thought that another crash
occurred after reboot, but actually it was before reboot.

While checking logs of current boot I saw a line that I don't understand:
Mar 14 19:19:16 gnome-shell[2140]: Extension ubuntu-d...@ubuntu.com already 
installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded

Is it expected? The same is written about all other system plugins.

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

Title:
  ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right
  clicking on the dock [clutter_actor_dispose: assertion failed:
  (priv->parent == NULL)]

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

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

[Roman]

Still present on 24.04 with gnome-shell=45.3-1ubuntu1 and ibus=1.5.29-1

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

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

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2056506] Re: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)]

[Roman]

Got this crash on latest 89ubuntu2

gnome-shell[3256]: 
Clutter:ERROR:../clutter/clutter/clutter-actor.c:5476:clutter_actor_dispose: 
assertion failed: (priv->parent == NULL)
gnome-shell[3256]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-actor.c:5476:clutter_actor_dispose: 
assertion failed: (priv->parent == NULL)
gnome-shell[3256]: GNOME Shell crashed with signal 6
gnome-shell[3256]: == Stack trace for context 0x61a7a1b23340 ==
gnome-shell[3256]: #0   61a7a1bea1a8 i   
file:///usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:642
 (20591ca0b560 @ 12)
gnome-shell[3256]: #1   7ffce5e4aab0 b   
resource:///org/gnome/shell/ui/environment.js:86 (1a4deca3240 @ 98)
gnome-shell[3256]: #2   7ffce5e4ab90 b   
resource:///org/gnome/shell/ui/environment.js:175 (1a4decca790 @ 891)
gnome-shell[3256]: #3   7ffce5e4ac60 b   
resource:///org/gnome/shell/ui/environment.js:297 (35fac36a9470 @ 19)
gnome-shell[3256]: #4   61a7a1bea118 i   
file:///usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:637
 (20591ca0b510 @ 124)
gnome-shell[3256]: #5   61a7a1bea098 i   
file:///usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:486
 (20591ca06f10 @ 45)
gnome-shell[3256]: #6   61a7a1bea008 i   
resource:///org/gnome/shell/ui/init.js:21 (2d08e5470bf0 @ 48)

$ apt show gnome-shell-extension-ubuntu-dock 
Package: gnome-shell-extension-ubuntu-dock
Version: 89ubuntu2

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

Title:
  ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right
  clicking on the dock [clutter_actor_dispose: assertion failed:
  (priv->parent == NULL)]

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

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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

[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy

[Roman Shipovskij]

After several days of usage everything looks good.
Also mutter and gnome-shell upgraded from -proposed.

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

Title:
  SRU gjs 1.72.4 to jammy

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  That's the GNOME 42 stable update, including some fixes:
  https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4

  [ Test case ]

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

  The test plan that will be used is documented at
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  [ Regression potential ]

  Gjs is fundamental part of the ubuntu desktop, so any failure of it
  may cause the desktop not even to boot (because it's being used by gdm
  too).

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


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

[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

[Roman Shipovskij]

What about 22.04 LTS? This bug fixed for 23.04 but not for 22.04.

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Triaged
Status in gjs source package in Kinetic:
  Triaged
Status in gjs source package in Lunar:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7

  Description: Ubuntu 22.04 LTS
  Release: 22.04

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  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/gjs/+bug/1974293/+subscriptions


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

[Desktop-packages] [Bug 2012978] Re: Memory leak

[Roman Shipovskij]

What about 22.04 LTS? This bug fixed for 23.04 but not for 22.04.

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

Title:
  Memory leak

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Triaged

Bug description:
  High Memory Usage 3.1gb in 2h after reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  Uname: Linux 6.2.8-060208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 22:46:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-25 (366 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)

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


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

[Desktop-packages] [Bug 1873398] Re: gnome-disks won't do SMART on NVME drive

[Roman Martin]

The bug is still present.

OS: Ubuntu 22.04.2
Kernel: 6.1.9
gnome-42-2204

Does the issue come from snap?

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

Title:
  gnome-disks won't do SMART on NVME drive

Status in GNOME Disks:
  New
Status in gnome-disk-utility package in Ubuntu:
  Triaged

Bug description:
  I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO.

  I opened Disks (gnome-disks) and it sees all my drives, but it won't
  show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB).
  The SMART menu item is greyed out.  It works fine on other drives.

  The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for 
example.  (Though smartctl is not in this live ISO, I have apt-get installed it 
at another time and tried it; and
  it works fine in the Ubuntu 18.04 that is installed on this machine.)

  I've attached a screencast showing the failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-disk-utility 3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 07:32:43 2020
  ExecutablePath: /usr/bin/gnome-disks
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1873398/+subscriptions


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

[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.5

[Roman Shipovskij]

There is a new bugfix release 42.6 in the stable 42 series.

https://gitlab.gnome.org/GNOME/mutter/-/blob/42.6/NEWS

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

Title:
  Update Mutter to 42.5

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 1993809] Re: Update gnome-shell to 42.5

[Roman Shipovskij]

There is a new bugfix release 42.6 in the stable 42 series.

https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.6/NEWS

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

Title:
  Update gnome-shell to 42.5

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS

  The version currently in Ubuntu 22.04.1 LTS is 42.4

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  I also cherry-picked a fix from kinetic:
  gsettings org.gnome.settings-daemon.peripherals.mouse
  no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop 
trying to report customizations for that gsettings schema.

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


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

[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Roman Strakhov]

Same here.
Ubuntu 22.04.1 LTS x86_64
Kernel: 5.18.16-xanmod1
WM: i3

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Roman Shipovskij]

Yes, this bug is still present in 22.04, the reason and workaround
described here https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/1154#note_1065418

** Patch added: "keyboard-layout-switching-delay-workaround.patch"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+attachment/5602294/+files/keyboard-layout-switching-delay-workaround.patch

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

Title:
  layout switch is delayed

Status in GNOME Shell:
  Unknown
Status in console-setup package in Ubuntu:
  Incomplete
Status in gconf package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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


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

[Desktop-packages] [Bug 1962718] Re: Firefox snap crashes on every upgrade

[Roman Shipovskij]

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

** Tags added: snapd

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

Title:
  Firefox snap crashes on every upgrade

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Firefox snap package crashes every time on upgrade which cause data
  loss, it disappear from the panel but still running on unknown
  workspace

  All this is very annoying to the average user and gives a negative
  impression of using Ubuntu

  I think Firefox snap is not ready for using in LTS release by default
  without an alternative to install .deb package

  Steps to reproduce:
  1) Run Firefox snap
  2) Upgrade from candidate channel: sudo snap refresh firefox --candidate
  3) Try to open a new tab or click on Firefox icon on panel

  Current behaviour:
  Firefox crashes or closes

  Expected behaviour:
  Firefox should notify user that restart is required, as in .deb case

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


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

[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap

[Roman Shipovskij]

Separate bug report about Firefox snap crash
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962718

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

Title:
  Make the deb package install the firefox snap

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Canonical and Mozilla are working together to make the firefox snap
  the only supported package in Ubuntu, thus deprecating the deb package
  in the archive.

  This bug tracks the transformation of the firefox package in the
  archive into a transitional package that installs the snap, much like
  was done for chromium-browser in Ubuntu 19.10.

  There are a number of known problems and regressions with the snap
  compared to the deb (see
  https://bugzilla.mozilla.org/show_bug.cgi?id=snap and
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap),
  those are actively being worked on and will be addressed in due time,
  please refrain from using this bug to point them out. Instead, file
  separate bugs in the upstream bug tracker
  (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify
  this is about the snap package.

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


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

[Desktop-packages] [Bug 1962718] [NEW] Firefox snap crashes on every upgrade

[Roman Shipovskij]

Public bug reported:

Firefox snap package crashes every time on upgrade which cause data
loss, it disappear from the panel but still running on unknown workspace

All this is very annoying to the average user and gives a negative
impression of using Ubuntu

I think Firefox snap is not ready for using in LTS release by default
without an alternative to install .deb package

Steps to reproduce:
1) Run Firefox snap
2) Upgrade from candidate channel: sudo snap refresh firefox --candidate
3) Try to open a new tab or click on Firefox icon on panel

Current behaviour:
Firefox crashes or closes

Expected behaviour:
Firefox should notify user that restart is required, as in .deb case

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


** Tags: impish jammy snap

** Attachment added: "Screencast 2022-03-02 10:31:02.mp4"
   
https://bugs.launchpad.net/bugs/1962718/+attachment/5564948/+files/Screencast%202022-03-02%2010%3A31%3A02.mp4

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

Title:
  Firefox snap crashes on every upgrade

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap package crashes every time on upgrade which cause data
  loss, it disappear from the panel but still running on unknown
  workspace

  All this is very annoying to the average user and gives a negative
  impression of using Ubuntu

  I think Firefox snap is not ready for using in LTS release by default
  without an alternative to install .deb package

  Steps to reproduce:
  1) Run Firefox snap
  2) Upgrade from candidate channel: sudo snap refresh firefox --candidate
  3) Try to open a new tab or click on Firefox icon on panel

  Current behaviour:
  Firefox crashes or closes

  Expected behaviour:
  Firefox should notify user that restart is required, as in .deb case

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


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

[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap

[Roman Shipovskij]

Firefox Snap package still does not work properly. It crashes every time
on upgrade which cause data loss, it disappear from the panel but still
running on unknown workspace...

All this is very annoying to the average user and gives a negative
impression of using Ubuntu.

I think Firefox Snap is not ready for using in LTS release by default.

The same situation with Chromium Snap package, I had to switch to Google
Chrome .deb package because I tired from Chromium Snap problems.

P.S. All Snap packages which I tried to use have the same issues, I'm
tired of riding on square wheels when everyone is riding on round ones.

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

Title:
  Make the deb package install the firefox snap

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Canonical and Mozilla are working together to make the firefox snap
  the only supported package in Ubuntu, thus deprecating the deb package
  in the archive.

  This bug tracks the transformation of the firefox package in the
  archive into a transitional package that installs the snap, much like
  was done for chromium-browser in Ubuntu 19.10.

  There are a number of known problems and regressions with the snap
  compared to the deb (see
  https://bugzilla.mozilla.org/show_bug.cgi?id=snap and
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap),
  those are actively being worked on and will be addressed in due time,
  please refrain from using this bug to point them out. Instead, file
  separate bugs in the upstream bug tracker
  (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify
  this is about the snap package.

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


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

[Desktop-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

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

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

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


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

[Desktop-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

Changing this to d-conf because its downgrade helps to eliminate the
issue

** Package changed: pulseeffects (Ubuntu) => d-conf (Ubuntu)

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

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


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

[Desktop-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work

[Roman]

Exact package causing the issue is not obvious, but I add bluez.

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

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (20.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
 serial:  
 Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
 rev: e2f 
 Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept 
 service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

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


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

[Desktop-packages] [Bug 1863801] Re: [snap] After deleting the cache, chromium crashes when file picker is called to upload files or folders

[Roman Valov]

I have encountered a similar issue on downgrade of snap package and workaround 
does work.
Previously had chromium 94 installed. Due to issues with top-bar rendering 
downgraded chromium to version 93. Got issues with any attempt to 
upload/download file. Running:

rm ~/snap/chromium/current/.last_revision

fixed the issue

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

Title:
  [snap] After deleting the cache, chromium crashes when file picker is
  called to upload files or folders

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  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: GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
   modes: 1920x1080
  Date: Tue Feb 18 20:49:46 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext473G   17G   53G  24% /home
   tmpfs  tmpfs  3.9G   22M  3.9G   1% /dev/shm
   /dev/sda2  ext473G   17G   53G  24% /home
  InstallationDate: Installed on 2019-05-17 (277 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (101 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

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


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

[Desktop-packages] [Bug 1941795] [NEW] Only half of MST display is visible after boot or sleep

[Roman Novikov]

Public bug reported:

Only left half of a 4K display in MST mode visible after sleep. The same
problem often appears after boot as well. Changing mode to any arbitrary
resolution and reverting back resolves the problem.

Display Asus PQ321qe

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 26 21:47:12 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 lttng-modules, 2.12.5, 5.11.0-25-generic, x86_64: installed
 lttng-modules, 2.12.5, 5.11.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop 9 Series) 
[1458:d000]
 Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c0) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RX Vega64 [1002:0b36]
InstallationDate: Installed on 2021-05-27 (90 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=a46531ab-2bd9-4b9c-a1c1-f3a83760a66c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/19/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12k
dmi.board.asset.tag: Default string
dmi.board.name: Z390 AORUS PRO WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12k:bd01/19/2021:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z390 AORUS PRO WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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+git20200226-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 ubuntu

** Attachment added: "IMG_6386.jpg"
   
https://bugs.launchpad.net/bugs/1941795/+attachment/5520959/+files/IMG_6386.jpg

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

Title:
  Only half of MST display is visible after boot or sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  Only left half of a 4K display in MST mode visible after sleep. The
  same problem often appears after boot as well. Changing mode to any
  arbitrary resolution and reverting back resolves the problem.

  Display Asus PQ321qe

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 26 21:47:12 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   lttng-modules, 2.12.5, 5.11.0-25-generic, x86_64: installed
   lttng-modules, 2.12.5, 5.11.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop 9 Series) 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c0) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RX Vega64 [1002:0b36]
  InstallationDate: Installed on 2021-05-27 (90 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI
  ProcKernelCmdLine: BOOT_IMAGE=

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Roman]

> * Logging into 'Ubuntu on Wayland' (select it on the login screen).

I've tried this before commenting last time and it had way worse
performance with the desktop itself. For example the dash would take a
minute or so to load all the icons. Also applications like OBS, Discord
and Teams have issues with recording and/or streaming, so I have to stay
on X.

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Roman]

Yes, it is still the same configuration.

I also get another issue all the time, maybe it is somewhat connected to
this one: When switching between users, either Gnome or X crashes. The
OS asks me each time to send a report and I did it a few times. Or maybe
this is worth a separate bug report?

** Attachment added: "newjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5501256/+files/newjournal.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/1872802

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Roman]

Well. My installation of Ubuntu 20.04 is one week old + all the updates
and it is still happening occasionally. I just did what I did a year ago
and I can reproduce the bug again and again. See attachment for a
screenshot I did a few minutes ago.

** Attachment added: "Screenshot from 2021-05-28 17-57-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5500920/+files/Screenshot%20from%202021-05-28%2017-57-22.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/1872802

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Roman]

Using the GTK greeter and also tried Slick greeter, both show nothing -
a blank screen - and I would have to ctrl alt f1, get to a terminal
screen, put in a username and password there and then "startx" but the
f7 or wherever the lightdm goes, that does not work when switching to
it.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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

[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Roman]

Not only is this bug still present on 20.0 with a Pi 3B+ but switching
to Slick greeter doesn't help at all. XDM works fine, etc. but Slick
Greeter is still based on LightDM which is where the issue appears to
be, not just with the particular GTK greeter.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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

[Desktop-packages] [Bug 1906394] [NEW] Displays blinking after Ubuntu 20.10 upgrade

[Roman]

Public bug reported:

Hi!

MY Displays are blinking after Ubuntu 20.10 upgrade. Please see the log.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Dec  1 14:02:04 2020
DistUpgraded: 2020-11-26 14:18:08,201 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-osp1-20171027-1
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0818]
InstallationDate: Installed on 2019-01-24 (677 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
MachineType: Dell Inc. Latitude 5491
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=33b5750d-e24c-406f-924e-050b03935415 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to groovy on 2020-11-26 (4 days ago)
dmi.bios.date: 02/25/2020
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 0R8P2H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:br1.12:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0R8P2H:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5491
dmi.product.sku: 0818
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Jul 28 12:22:12 2020
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2.2

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


** Tags: amd64 apport-bug groovy 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/1906394

Title:
  Displays blinking after Ubuntu 20.10 upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi!

  MY Displays are blinking after Ubuntu 20.10 upgrade. Please see the
  log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec  1 14:02:04 2020
  DistUpgraded: 2020-11-26 14:18:08,201 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0818]
  InstallationDate: Installed on 2019-01-24 (677 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  MachineType: Dell Inc. Latitude 5491
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=33b5750d-e24c-406f-924e-050b03935415 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Roman Gralevsky]

Affecting me as well

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Roman Gralevsky]

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

Affecting me as well on Sennheiser Momentum True Wireless 2

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Roman Gralevsky]

Sennheiser Momentum True Wireless 2

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

[Roman]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5403355/+files/journal.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/1872802

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

[Roman]

I just recently switched to PopOS and it has the same issue in gnome, if
that helps.

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

[Roman]

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5403356/+files/lspcik.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/1872802

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues

[Roman Odaisky]

This way each application has to be specifically modified to use
$SNAP_USER_COMMON instead of $HOME? Why not let the applications keep
using $HOME but add an option to snapcraft.yaml that would specify what
exactly to set $HOME to, with options like “real home”, “versioned snap
directory”, “common snap directory”? (So none of the REALHOME=$(getent
passwd $(id -u) | cut -d ':' -f 6) nonsense.)

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

Title:
  snap refresh while command is running may cause issues

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  In testing a desktop snap that saves state in $HOME on close, I
  noticed that if I snap refresh the snap while the command is running
  that it will try to save its state to the previous snap version's data
  directory. For the snap I was testing (a browser), this resulted in a
  very poor user experience (the browser on restart complained about an
  improper shutdown).

  What is happening is that:
  1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something 
like /home/user/snap/foo/x1. The security policy correctly allows writes to 
SNAP_USER_DATA
  2. on snap refresh to 'x2', the security policy for the snap is updated for 
the running process such that /home/user/snap/foo/x1 is readonly and 
/home/user/snap/foo/x2 is read/write
  3. the command in '1's environment is not changed and HOME (as well as 
SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path
  4. the command tries to shutdown gracefully and save state to the 'x1' HOME 
and security policy blocks it

  Snappy's design for rollbacks relies on the previous SNAP_DATA and
  SNAP_USER_DATA directories not being writable and IMHO we should not
  change the policy to make other snap version's data dirs writable.

  The design of the snappy state engine ensures (among other things)
  that there is only ever one security policy in place for the snap. In
  snappy 15.04 this problem was (intentionally) avoided because we used
  snap security policy that was versioned such that the new policy would
  not apply until the next app invocation.

  Gustavo and Zygmunt, you both advocated strongly for only one version
  of the policy on disk and loaded in the kernel and I recall bringing
  up this type of bug as a counter-argument, and if IIRC for daemons we
  said that snapd could simply restart them (makes perfect sense). Have
  you thought of the mechanism for restarting non-daemons?

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

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

[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap

[Roman Odaisky]

So in general it is not possible to connect an interface which the snap
didn’t request? If not, sounds like a powerful feature to add. Forcing a
custom interface on a snap can be used to affect its filesystem in the
desired way.

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

Title:
  /usr/share/alsa missing within snap

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ ls /snap/chromium/current/usr/share/alsa
  alsa.conf  alsa.conf.d  cards  pcm  pulse-alsa.conf  smixer.conf  
sndo-mixer.alisp  topology  ucm

  $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
  ls: cannot access '/usr/share/alsa': No such file or directory

  For this reason there’s no sound. How to make sure that
  /usr/share/alsa which is present in the snap does not somehow go
  missing when the snap runs?

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

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

[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap

[Roman Odaisky]

`snap connect chromium:alsa` and variations thereof fail with “error:
snap "chromium" has no plug named "alsa"”. How to connect?

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

Title:
  /usr/share/alsa missing within snap

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ ls /snap/chromium/current/usr/share/alsa
  alsa.conf  alsa.conf.d  cards  pcm  pulse-alsa.conf  smixer.conf  
sndo-mixer.alisp  topology  ucm

  $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
  ls: cannot access '/usr/share/alsa': No such file or directory

  For this reason there’s no sound. How to make sure that
  /usr/share/alsa which is present in the snap does not somehow go
  missing when the snap runs?

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

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

[Desktop-packages] [Bug 1877629] Re: An excessive number of AppArmor denials

[Roman Odaisky]

Ubuntu 20.04, snap version 81.0.4044.138.

I don’t think the mention of the three domain names docs.google.com,
youtube.com and lpcdn.lpsnmedia.net is anything special. Most likely
these are simply the domains that caused the highest number of
filesystem access requests that are for some reason denied. Further down
the list (when not truncated at 1000 entries) twitter.com, app.slack.com
and other high-profile domains make their appearances.

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

Title:
  An excessive number of AppArmor denials

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  On advice given in another bug, I ran `journalctl | fgrep DEN`. This
  produced as much as a gigabyte of output which certainly sounds
  excessive for one week that it represents. I replaced numbers with
  placeholders so I could `uniq -c` it ( stands for N hex
  characters), the top offenders are below. Is something misconfigured?

  1152937 audit[]: AVC apparmor="DENIED" operation="truncate" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/Favicons-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
   455154 audit[]: AVC apparmor="DENIED" operation="truncate" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/History-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
   196028 audit[]: AVC apparmor="DENIED" operation="rename_src" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOG"
 pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" 
fsuid=1000 ouid=1000
   195406 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
   195406 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=1000 ouid=1000
   164056 kernel: audit: type=1400 audit(:): apparmor="DENIED" 
operation="truncate" profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/Favicons-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
   130756 audit[]: AVC apparmor="DENIED" operation="unlink" 
profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" 
requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
   111779 audit[]: AVC apparmor="DENIED" operation="rename_src" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOG"
 pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" 
fsuid=1000 ouid=1000
   111480 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
   111480 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=1000 ouid=1000
96203 kernel: audit: type=1400 audit(:): apparmor="DENIED" 
operation="truncate" profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/History-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
62594 audit[]: AVC apparmor="DENIED" operation="rename_src" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOG"
 pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" 
fsuid=1000 ouid=1000
62340 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
62340 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolF

[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap

[Roman Odaisky]

I’m not running any other snaps, which one would you recommend to test
this?

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

Title:
  /usr/share/alsa missing within snap

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ ls /snap/chromium/current/usr/share/alsa
  alsa.conf  alsa.conf.d  cards  pcm  pulse-alsa.conf  smixer.conf  
sndo-mixer.alisp  topology  ucm

  $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
  ls: cannot access '/usr/share/alsa': No such file or directory

  For this reason there’s no sound. How to make sure that
  /usr/share/alsa which is present in the snap does not somehow go
  missing when the snap runs?

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

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

[Desktop-packages] [Bug 1877629] [NEW] An excessive number of AppArmor denials

[Roman Odaisky]

Public bug reported:

On advice given in another bug, I ran `journalctl | fgrep DEN`. This
produced as much as a gigabyte of output which certainly sounds
excessive for one week that it represents. I replaced numbers with
placeholders so I could `uniq -c` it ( stands for N hex
characters), the top offenders are below. Is something misconfigured?

1152937 audit[]: AVC apparmor="DENIED" operation="truncate" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/Favicons-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
 455154 audit[]: AVC apparmor="DENIED" operation="truncate" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/History-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
 196028 audit[]: AVC apparmor="DENIED" operation="rename_src" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOG"
 pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" 
fsuid=1000 ouid=1000
 195406 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
 195406 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=1000 ouid=1000
 164056 kernel: audit: type=1400 audit(:): apparmor="DENIED" 
operation="truncate" profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/Favicons-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
 130756 audit[]: AVC apparmor="DENIED" operation="unlink" 
profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" 
requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
 111779 audit[]: AVC apparmor="DENIED" operation="rename_src" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOG"
 pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" 
fsuid=1000 ouid=1000
 111480 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
 111480 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=1000 ouid=1000
  96203 kernel: audit: type=1400 audit(:): apparmor="DENIED" 
operation="truncate" profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/History-journal" 
pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  62594 audit[]: AVC apparmor="DENIED" operation="rename_src" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOG"
 pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" 
fsuid=1000 ouid=1000
  62340 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  62340 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOCK"
 pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=1000 ouid=1000
  49838 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" 
requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000
  44399 audit[]: AVC apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/home/roma/snap/chromium/1135/.config/chromium/Default/Cookies-journal" 
pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" 
fsuid=1000 ouid=1000
  42368 audit[]: AVC apparmor="DENIED" operation="unlink" 
profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" 
requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
  41786 audit[]: AVC apparmor="DENIED" operation="unlink" 
profile="sna

[Desktop-packages] [Bug 1877597] Re: Does not see ~/.XCompose

[Roman Odaisky]

Ah, I think the true source of the problem was that my .XCompose was a
symlink into a subdirectory of .config, so that’s what was actually
denied. This is at least understandable, even if it still makes no sense
(~/.config/my-dotfiles-git-repository is off limits but ~/Documents
/financial-report-top-secret.pdf is not).

Sorry for the misleading bug description.

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

Title:
  Does not see ~/.XCompose

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Unless I manually edit ~/.chromium-browser.init to include “export
  XCOMPOSEFILE=” and take
  care to put a copy of XCompose at such a path, Chromium does not see
  the XCompose file and so can’t make use of user-defined Compose
  sequences.

  Chromium needs to be able to see ~/.XCompose, possibly other X11 files
  of similar nature.

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

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

[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap

[Roman Odaisky]

I am not. This is certainly not the place to discuss advantages and
drawbacks of pulseaudio, of which it has both, but seeing as both
Chromium and snapd itself support ALSA, the chromium snap should also
support it.

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

Title:
  /usr/share/alsa missing within snap

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ ls /snap/chromium/current/usr/share/alsa
  alsa.conf  alsa.conf.d  cards  pcm  pulse-alsa.conf  smixer.conf  
sndo-mixer.alisp  topology  ucm

  $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
  ls: cannot access '/usr/share/alsa': No such file or directory

  For this reason there’s no sound. How to make sure that
  /usr/share/alsa which is present in the snap does not somehow go
  missing when the snap runs?

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

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

[Desktop-packages] [Bug 1877601] [NEW] /usr/share/alsa missing within snap

[Roman Odaisky]

Public bug reported:

$ ls /snap/chromium/current/usr/share/alsa
alsa.conf  alsa.conf.d  cards  pcm  pulse-alsa.conf  smixer.conf  
sndo-mixer.alisp  topology  ucm

$ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
ls: cannot access '/usr/share/alsa': No such file or directory

For this reason there’s no sound. How to make sure that /usr/share/alsa
which is present in the snap does not somehow go missing when the snap
runs?

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

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

Title:
  /usr/share/alsa missing within snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  $ ls /snap/chromium/current/usr/share/alsa
  alsa.conf  alsa.conf.d  cards  pcm  pulse-alsa.conf  smixer.conf  
sndo-mixer.alisp  topology  ucm

  $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
  ls: cannot access '/usr/share/alsa': No such file or directory

  For this reason there’s no sound. How to make sure that
  /usr/share/alsa which is present in the snap does not somehow go
  missing when the snap runs?

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

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

[Desktop-packages] [Bug 1877597] [NEW] Does not see ~/.XCompose

[Roman Odaisky]

Public bug reported:

Unless I manually edit ~/.chromium-browser.init to include “export
XCOMPOSEFILE=” and take care
to put a copy of XCompose at such a path, Chromium does not see the
XCompose file and so can’t make use of user-defined Compose sequences.

Chromium needs to be able to see ~/.XCompose, possibly other X11 files
of similar nature.

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

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

Title:
  Does not see ~/.XCompose

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Unless I manually edit ~/.chromium-browser.init to include “export
  XCOMPOSEFILE=” and take
  care to put a copy of XCompose at such a path, Chromium does not see
  the XCompose file and so can’t make use of user-defined Compose
  sequences.

  Chromium needs to be able to see ~/.XCompose, possibly other X11 files
  of similar nature.

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

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

[Desktop-packages] [Bug 1877593] [NEW] Needlessly cats ~/.chromium-browser.init

[Roman Odaisky]

Public bug reported:

$ fgrep -w cat -C4 /snap/chromium/current/bin/chromium.launcher

# Source ~/.chromium-browser.init for compatibility with the chromium-browser
# deb package (https://launchpad.net/bugs/1837746)
if [ -f $REALHOME/.chromium-browser.init ]; then
  cat $REALHOME/.chromium-browser.init 2>/dev/null
  if [ "$?" -eq "0" ]; then
. $REALHOME/.chromium-browser.init
  fi
fi

This `cat` needlessly clutters the output when using things like `xdg-
open`. If the intent is to check whether policies permit reading the
file (so `test -f` wouldn’t work), then the stdout should be redirected
to /dev/null as well.

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

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

Title:
  Needlessly cats ~/.chromium-browser.init

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  $ fgrep -w cat -C4 /snap/chromium/current/bin/chromium.launcher

  # Source ~/.chromium-browser.init for compatibility with the chromium-browser
  # deb package (https://launchpad.net/bugs/1837746)
  if [ -f $REALHOME/.chromium-browser.init ]; then
cat $REALHOME/.chromium-browser.init 2>/dev/null
if [ "$?" -eq "0" ]; then
  . $REALHOME/.chromium-browser.init
fi
  fi

  This `cat` needlessly clutters the output when using things like `xdg-
  open`. If the intent is to check whether policies permit reading the
  file (so `test -f` wouldn’t work), then the stdout should be
  redirected to /dev/null as well.

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

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

[Roman Odaisky]

This issue causes `ubuntu-bug chromium-browser` to hang.

Additionally, isn’t this an issue that’s best solved within snapd
itself?

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

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Hi,

I tested the package contained in the proposed repo (v13.99.1).
I plugged and unplugged the jack several times. It worked well. Worked fine 
also after reboot.

I am now again a happy user of my headset :D

Thanks,
Roman

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Hi Kai-Heng,

Your repo works!
I didn't expect my problem will be addressed that fast.
Thanks a lot for a super quick response and fix - that is great!

Cheers,
Roman

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Forgot to add my system details:

Dell Lattitude E5570.

Sound card:
  product: 100 Series/C230 Series Chipset Family HD Audio Controller
  vendor: Intel Corporation

System: Ubuntu Budgie 20.04 with pulseaudio version 13.99.1.

Linux 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1876065] [NEW] After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Public bug reported:

After startup with headset plugged in they play sound nicely - no issue.
When they are unplugged, the sound is switched to the speaker (laptop) -
all good. However, when I plug the headset back there is no sound. I see
the app on pavucontrol, the volume is fine - everything looks fine
except there is no sound. I dumped output of "pactl list" command on
startup (headset plugged), after unplugging the headset, and when it is
plugged back. From the comparison of these outputs, it looks like the
source has got muted after the headset is plugged.

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

Attached three outputs:
headset-in.txt - after startup with headset plugged - all fine.
headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
headset-back.txt - after plugged headset back - no sound.

Any help greatly appreciated.

Regards,
Roman

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

** Attachment added: "pa-issue.tar.gz"
   
https://bugs.launchpad.net/bugs/1876065/+attachment/5363918/+files/pa-issue.tar.gz

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in glitchy appearance for a fraction of a second

[Roman]

** Description changed:

  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.
+ 
+ No such issues were experienced with previously installed Ubuntu Mate or
+ Windows 10.
+ 
+ Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
+ i5-7200U CPU @ 2.50GHz × 4
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  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 in Ubuntu.
https://bugs.launchpad.net/bugs/1872802

Title:
  Resizing any window will randomly result in glitchy appearance for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1872802] [NEW] Resizing any window will randomly result in glitchy appearance for a fraction of a second

[Roman]

Public bug reported:

When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
This glitchy appearance is restored immediately.
The issue seems to be seen less often when the CPU is utilized more heavily, as 
when I recorded the screen with OBS to grab the screenshot.
The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

No such issues were experienced with previously installed Ubuntu Mate or
Windows 10.

Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
i5-7200U CPU @ 2.50GHz × 4

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 14 20:45:47 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-14 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal

** Attachment added: "gnome-system-monitor"
   https://bugs.launchpad.net/bugs/1872802/+attachment/5354098/+files/bad.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/1872802

Title:
  Resizing any window will randomly result in glitchy appearance for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872802/+subscriptions

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

[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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated from bionic-proposed and everything is fine, as I
see the problem was fixed since kernel 4.15.0-62, so the patch for mesa
can be safely dropped.

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

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

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Desktop-packages] [Bug 1766495] Re: "your libfreerdp does not support h264"

[Roman Cardenas]

la solucion esta aqui,

https://theoscaargomes.wordpress.com/2018/05/04/solucionando-erro-
remmina-linux-ubuntu-18-04/

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

Title:
  "your libfreerdp does not support h264"

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect via RDP, Remmina gives this error:

  "You requested an h264 GFX mode for server , but your
  libfreerdp does not support h264. Please check color depth settings."

  However, (1) I don't see any color depth settings in Remmina GUI, and
  (2) ubuntu-restricted-extras is installed. I have libx264-152 version
  2:0.152.2854+gite9a5903-2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 24 09:29:44 2018
  InstallationDate: Installed on 2018-03-23 (31 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated mesa from bionic-proposed and now everything is fine
on i386 Ubuntu 18.04:

~# apt-cache policy libgl1-mesa-glx 
libgl1-mesa-glx:
  Встановлено: 19.0.2-1ubuntu1.1~18.04.2
  Кандидат:19.0.2-1ubuntu1.1~18.04.2
  Таблиця версій:
 *** 19.0.2-1ubuntu1.1~18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages
100 /var/lib/dpkg/status

I have also tried different kernels with bad mesa
19.0.2-1ubuntu1.1~18.04.1 from bionic-updates:

linux-generic (4.15.0-54-generic) - problem exists
linux-generic-hwe-18.04 (4.18.0-25-generic) - problem exists
linux-generic-hwe-18.04-edge (5.0.0-20-generic) - everything is fine

With mesa 19.0.2-1ubuntu1.1~18.04.1 from bionic-proposed everything is
fine on all these kernels

** Tags removed: verification-needed
** Tags added: verification-done-bionic

** Tags removed: verification-needed-bionic

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

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

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location

[Roman Grytskiv]

I am also experiencing this on Ubuntu 18.10

Could you please give an update on this issue?

Thanks!

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in cinnamon-desktop-environment package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Mint 17.3 Cinnamon 64bit.

  Steps to reproduce:
   * Do a fresh install.
   * Run mintupdate and update all packages.
   * Run firefox. 
   * Start right clicking on the page to open the context menu. Resize the 
window and perhaps move it around the screen a couple of times. Right click 
some more. 
   * Observer that, eventually, the context menu will start to appear in 
incorrect locations on the screen. The same also happens with the search bar, 
text fields and any other dropdown box.

  In the worst embodiment of the bug, the menu opens underneath the
  pointer and treats the release of the mouse button as a click, and so
  does things the user does not want to do.

  I believe the root cause is the following bug in GTK+ 3.10.8. Firefox
  switched over to using GTK+3 in version 46 which is when this bug
  appeared and has been there ever since.

  https://bugzilla.gnome.org/show_bug.cgi?id=758609
  https://bugzilla.mozilla.org/show_bug.cgi?id=1022241

  Mozilla aren't going to fix it because it's a GTK bug. GTK have
  already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not
  have the patch.

  Please roll out the patch for us 17.3 users who cannot upgrade. I can
  confirm that the problem is solved in Mint 18.

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

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

[Desktop-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated from ppa:ubuntu-x-swat/updates, now everything is
fine on i386 Ubuntu 18.04

~# apt-cache policy libgl1-mesa-glx
libgl1-mesa-glx:
  Installed: 19.0.8-0ubuntu0~18.04.1
  Candidate: 19.0.8-0ubuntu0~18.04.1
  Version table:
 *** 19.0.8-0ubuntu0~18.04.1 500
500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu bionic/main 
i386 Packages
100 /var/lib/dpkg/status

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

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

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Desktop-packages] [Bug 1836721] [NEW] Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

Public bug reported:

Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04.

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

~# uname -a
Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

~# lspci -nn -k -d ::0300
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

mesa: 19.0.2-1ubuntu1.1~18.04.1

X crashes with message:
 i965: Failed to submit batchbuffer: Invalid argument

The same issue was after updating mesa from 18.0 to 18.2:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

I have tried the same fix and it works for me:
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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


** Tags: bionic i386 regression-update

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

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

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Desktop-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

[Roman]

Confirming x1 5th gen. Any updates?

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

Title:
  Internal mic stops working when plugging in headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1791654] [NEW] package postgresql 10+190 failed to install/upgrade: проблеми з залежностями - залишається неналаштованим

[Roman Denysiuk]

Public bug reported:

Automatic error report

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: postgresql 10+190
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 firefox-locale-uk:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Sep 10 06:56:38 2018
ErrorMessage: проблеми з залежностями - залишається неналаштованим
InstallationDate: Installed on 2018-07-12 (59 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: postgresql-common
Title: package postgresql 10+190 failed to install/upgrade: проблеми з 
залежностями - залишається неналаштованим
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: postgresql-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package postgresql 10+190 failed to install/upgrade: проблеми з
  залежностями - залишається неналаштованим

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  Automatic error report

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: postgresql 10+190
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   firefox-locale-uk:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep 10 06:56:38 2018
  ErrorMessage: проблеми з залежностями - залишається неналаштованим
  InstallationDate: Installed on 2018-07-12 (59 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: postgresql-common
  Title: package postgresql 10+190 failed to install/upgrade: проблеми з 
залежностями - залишається неналаштованим
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1476574] Re: Unable to print pages with long title

[Roman Shipovskij]

On 18.04 bug not present, I think it fixed in GTK.

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

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

Title:
  Unable to print pages with long title

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

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

  Unable to print pages with title (or URI if no title) more than 255
  characters

  CUPS error: Print-Job client-error-attributes-or-values-not-supported

  https://tools.ietf.org/html/rfc2911
  4.1.2 'name'

 This syntax type is used for user-friendly strings, such as a Printer
 name, that, for humans, are more meaningful than identifiers.  Names
 are never translated from one natural language to another.  The
 'name' attribute syntax is essentially the same as 'text', including
 the REQUIRED support of UTF-8 except that the sequence of characters
 is limited so that its encoded form MUST NOT exceed 255 (MAX) octets.

 Also like 'text', 'name' is really an abbreviated notation for either
 'nameWithoutLanguage' or 'nameWithLanguage'.  That is, all IPP
 objects and clients MUST support both the 'nameWithoutLanguage' and
 'nameWithLanguage' attribute syntaxes.  However, in actual usage and

  to reproduce just try to print attached html file

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

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

[Desktop-packages] [Bug 1476574] Re: Unable to print pages with long title

[Roman Shipovskij]

As I see bug is fixed for GTK versions older than 3.18.2, but on 16.04
GTK version is 3.18.9

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

Title:
  Unable to print pages with long title

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

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

  Unable to print pages with title (or URI if no title) more than 255
  characters

  CUPS error: Print-Job client-error-attributes-or-values-not-supported

  https://tools.ietf.org/html/rfc2911
  4.1.2 'name'

 This syntax type is used for user-friendly strings, such as a Printer
 name, that, for humans, are more meaningful than identifiers.  Names
 are never translated from one natural language to another.  The
 'name' attribute syntax is essentially the same as 'text', including
 the REQUIRED support of UTF-8 except that the sequence of characters
 is limited so that its encoded form MUST NOT exceed 255 (MAX) octets.

 Also like 'text', 'name' is really an abbreviated notation for either
 'nameWithoutLanguage' or 'nameWithLanguage'.  That is, all IPP
 objects and clients MUST support both the 'nameWithoutLanguage' and
 'nameWithLanguage' attribute syntaxes.  However, in actual usage and

  to reproduce just try to print attached html file

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

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

[Desktop-packages] [Bug 1476574] Re: Unable to print pages with long title

[Roman Shipovskij]

Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:   xenial

Firefox 61.0.1, bug still here

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

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

Title:
  Unable to print pages with long title

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

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

  Unable to print pages with title (or URI if no title) more than 255
  characters

  CUPS error: Print-Job client-error-attributes-or-values-not-supported

  https://tools.ietf.org/html/rfc2911
  4.1.2 'name'

 This syntax type is used for user-friendly strings, such as a Printer
 name, that, for humans, are more meaningful than identifiers.  Names
 are never translated from one natural language to another.  The
 'name' attribute syntax is essentially the same as 'text', including
 the REQUIRED support of UTF-8 except that the sequence of characters
 is limited so that its encoded form MUST NOT exceed 255 (MAX) octets.

 Also like 'text', 'name' is really an abbreviated notation for either
 'nameWithoutLanguage' or 'nameWithLanguage'.  That is, all IPP
 objects and clients MUST support both the 'nameWithoutLanguage' and
 'nameWithLanguage' attribute syntaxes.  However, in actual usage and

  to reproduce just try to print attached html file

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

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

[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Roman]

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

I've experienced this bug in a clean install of 18.04 via the server
edition first then adding a GUI. In the past editing
/etc/NetworkManager/NetworkManager.conf and setting managed=true was the
solution, that doesn't work anymore. Instead, first I needed to create a
file under /usr/lib/NetworkManager/conf.d/10-globally-managed-
devices.conf and put the following text in it:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan

then copy that file to /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf

and then edit the file /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf and change the line to say unmanaged-devices=none

that is finally, at long last what solved it for me.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Desktop-packages] [Bug 1417534]

[Roman Shipovskij]

>From http://downloadarchive.documentfoundation.org/libreoffice/old/

Version 3.6.7.2 (Build ID: e183d5b) - last version without bug
Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) - first 
version with bug

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

Title:
  Calc doesn't merge cells when pasting merged content from HTML

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

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

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:5.0.2-0ubuntu1
Candidate: 1:5.0.2-0ubuntu1
Version table:
   *** 1:5.0.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens the following URL via Firefox 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1417534/+attachment/438/+files/table_with_merged_cells_in_first_row.html
 > highlights all content in the top row > paste into Calc then A1 contains:
  Cell1

  and B1 and C1 are merged together containing:
  Cell2 + 3

  as it does in Excel 2013.

  4) What happens instead is that while cell A1 contains Cell1, B1 and
  C1 are not merged, and B1 contains Cell2 + 3.

  Originally reported on LO 4.2, and reported to not exist in LO 3.5.

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

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

[Desktop-packages] [Bug 1417534]

[Roman Shipovskij]

The bug is still present on:

Ubuntu 16.04, LibreOffice 5.2.5.1 from
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2

Ubuntu 16.04, LibreOffice 5.3.0.3 from
https://launchpad.net/~libreoffice/+archive/ubuntu/ppa

Windows 10, LibreOffice 5.2.5.1

Windows 10, LibreOffice 5.3.0.3

The bug does not present on LibreOffice 3.5 and lower, it's a regression

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

Title:
  Calc doesn't merge cells when pasting merged content from HTML

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

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

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:5.0.2-0ubuntu1
Candidate: 1:5.0.2-0ubuntu1
Version table:
   *** 1:5.0.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens the following URL via Firefox 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1417534/+attachment/438/+files/table_with_merged_cells_in_first_row.html
 > highlights all content in the top row > paste into Calc then A1 contains:
  Cell1

  and B1 and C1 are merged together containing:
  Cell2 + 3

  as it does in Excel 2013.

  4) What happens instead is that while cell A1 contains Cell1, B1 and
  C1 are not merged, and B1 contains Cell2 + 3.

  Originally reported on LO 4.2, and reported to not exist in LO 3.5.

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

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

[Desktop-packages] [Bug 1778824] Re: Terminal starts maximized when using custom font

[Roman Kvitkov]

170x43 terminal with same font starts in normal window. Terminal of size
170x44 is maximized.

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

Title:
  Terminal starts maximized when using custom font

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu Mono Regular 15pt with 170x45 terminal size which
  fits in 1920x1080 display. I expect normal state window when starting
  Terminal. Instead, Terminal starts maximized.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 05:16:34 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-06-24 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1778824] [NEW] Terminal starts maximized when using custom font

[Roman Kvitkov]

Public bug reported:

I'm using Ubuntu Mono Regular 15pt with 170x45 terminal size which fits
in 1920x1080 display. I expect normal state window when starting
Terminal. Instead, Terminal starts maximized.


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 27 05:16:34 2018
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2018-06-24 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

- Description:  Ubuntu 18.04 LTS
- Release:  18.04
- gnome-terminal:
-   Installed: 3.28.2-1ubuntu1~18.04.1
-   Candidate: 3.28.2-1ubuntu1~18.04.1
-   Version table:
-  *** 3.28.2-1ubuntu1~18.04.1 500
- 500 http://mirror.yandex.ru/ubuntu bionic-updates/main amd64 Packages
- 100 /var/lib/dpkg/status
-  3.28.1-1ubuntu1 500
- 500 http://mirror.yandex.ru/ubuntu bionic/main amd64 Packages
- 
  I'm using Ubuntu Mono Regular 15pt with 170x45 terminal size which fits
  in 1920x1080 display. I expect normal state window when starting
  Terminal. Instead, Terminal starts maximized.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 05:16:34 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-06-24 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1778824

Title:
  Terminal starts maximized when using custom font

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu Mono Regular 15pt with 170x45 terminal size which
  fits in 1920x1080 display. I expect normal state window when starting
  Terminal. Instead, Terminal starts maximized.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 05:16:34 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-06-24 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU

[Roman Dinga]

Same here, Asus N550JK with Nvidia 850M. After switch to Intel by
Nvidia-prime and restart, I can see huge consumption, around 22W. When I
disable nouveau completely, by disabling the Nvidia fallback service and
then turning off the GPU using old bbswitch, I get 11W which is normal
for this laptop with turned off GPU. So bbswitch still works, but
vgaswitcheroo doesn't. Pity that bumblebee doesn't work anymore...

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

Title:
  nvidia-prime can't switch off the discrete GPU

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a
  change in the nvidia packaging, and a change of behaviour in logind,
  broke this feature.

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

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

[Desktop-packages] [Bug 1773820] [NEW] package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kern

[Roman Shevelev]

Public bug reported:

romanshevelev@HOME-PC2:~$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

romanshevelev@HOME-PC2:~$ apt-cache policy nvidia-340
nvidia-340:
  Установлен: 340.106-0ubuntu3
  Кандидат:   340.106-0ubuntu3
  Таблица версий:
 *** 340.106-0ubuntu3 500
500 http://ru.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 340.106-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sun May 27 21:30:51 2018
ErrorMessage: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который 
уже имеется в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка 
перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете 
nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка
  перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется
  в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1

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

Bug description:
  romanshevelev@HOME-PC2:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  romanshevelev@HOME-PC2:~$ apt-cache policy nvidia-340
  nvidia-340:
Установлен: 340.106-0ubuntu3
Кандидат:   340.106-0ubuntu3
Таблица версий:
   *** 340.106-0ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/restricted amd64 
Packages
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 21:30:51 2018
  ErrorMessage: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», 
который уже имеется в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка 
перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете 
nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't display

[roman dovhan]

Here is how settings is "displayed", when control panel is in bottom of
the display.


** Attachment added: "printscreen"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1721637/+attachment/5139256/+files/Screenshot%20from%202018-05-14%2017-27-49.png

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't display

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't display

[roman dovhan]

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => roman dovhan (dovhanrg)

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't display

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

[Roman]

$ sudo systemctl restart NetworkManager
also fixed pushed routes from server. Thanks author of comment #14

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

Title:
  NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Relevant information that may or may not have been included by ubuntu-
  bug:

  Ubuntu release 16.04
  Package network-manager 1.2.0-0ubuntu0.16.04.2
  Package network-manager-openvpn 1.1.93-1ubuntu1

  NetworkManager ignores pushed openvpn routes when "Use this connection
  only for resources on its network" is checked.  This is a behavior
  change since 14.04.

  To repeat:

  1) Use an OpenVpn server that pushes routes.  I suggest using a server
  that pushes several routes since this makes their absence obvious.
  Set up a NetworkManager VPN of type OpenVpn to this server.  Select
  "Use this connection only for resources on its network" in the
  "Routes" section of the IPV4 options.

  2) Set up a raw OpenVpn connection to the same server.

  3) Connect to the server using the raw OpenVpn connection.  The pushed
  routes are all there.

  4) Connect to the server using NetworkManager.  The only route added
  is a n interface level route to the tunnel device network.

  Using the same setup on 14.04, all pushed routes are added.

  
  The missing routes are also "Resources on the VPN network", and should be 
added in the absence of further direction.  Ignoring pushed routes should be 
controlled by the "Ignore automatically obtained routes" checkbox.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jul 15 23:12:55 2016
  InstallationDate: Installed on 2016-05-04 (72 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

[Roman Shchekin]

@nrbrtx I love you, dude, thanks for your fix!

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

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

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

[Desktop-packages] [Bug 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

[Roman Shchekin]

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

This is very old and annoying bug. Can someone fix it, please???

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

[Sadoyan Roman]

Thank you Norbert for good job, hotkeys with yours patch works good! But there 
is one moment, keyboard layout still switch on key RELEASE and when I'am using 
CTRL+SHIFT+T my keyboard layout is changed to another and it is not good, 
because I doesn't expect for keyboard layout switching when I use hotkeys.
Is there any change to make keyboard layout switching on key release, not key 
down?

P.S.: Developers would be grateful to you.

Ubuntu 18.04.

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Roman Dinga]

Ok I see that there already is a bug for this 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Roman Dinga]

Is there an open bug for discrete GPU switch not working? Or should I
open a new one?

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1579160] Re: second nautilus spawns errors

[Roman Shipovskij]

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

** This bug has been marked a duplicate of bug 1569970
   Nautilus does not start on 16.04

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

Title:
  second nautilus spawns errors

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS
  nautilus:
   1:3.18.4.is.3.14.3-0ubuntu4

  
  Steps to reproduce:
  killall nautilus
  nautilus /home &
  nautilus /tmp

  (nautilus:17416): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: 
assertion 'interface_->priv->connections != NULL' failed
  (nautilus:17416): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: 
assertion 'interface_->priv->connections != NULL' failed
  (nautilus:17416): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 
'GDK_IS_SCREEN (screen)' failed
  (nautilus:17416): GLib-GObject-WARNING **: invalid (NULL) pointer instance
  (nautilus:17416): GLib-GObject-CRITICAL **: g_signal_connect_object: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

  Same errors (but with different line numbers) are polluting also at least: 
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1576252
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1571431
  https://ask.fedoraproject.org/en/question/72155/nautilus-critical-error/

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

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

[Desktop-packages] [Bug 1751788] Re: No power off option for power off button in gnome control center

[Roman Zabaluev]

And how do I update it? Just ran apt-get update/upgrade before filing a
bug report.

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

Title:
  No power off option for power off button in gnome control center

Status in gnome-control-center:
  Fix Released
Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  There's no such an option to power off the machine on power button
  press.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 26 16:50:14 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-12-05 (83 days ago)

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

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

[Desktop-packages] [Bug 1751788] Re: No power off option for power off button in gnome control center

[Roman Zabaluev]

** Attachment added: "gnome settings"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1751788/+attachment/5063533/+files/photo_2018-02-26_18-09-08.jpg

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

Title:
  No power off option for power off button in gnome control center

Status in gnome-control-center:
  Fix Released
Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  There's no such an option to power off the machine on power button
  press.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 26 16:50:14 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-12-05 (83 days ago)

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

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

[Desktop-packages] [Bug 1751788] Re: No power off option for power off button in gnome control center

[Roman Zabaluev]

The first one means "suspend", the last one means "do nothing".

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

Title:
  No power off option for power off button in gnome control center

Status in gnome-control-center:
  Fix Released
Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  There's no such an option to power off the machine on power button
  press.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 26 16:50:14 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-12-05 (83 days ago)

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

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

[Desktop-packages] [Bug 1751788] Re: No power off option for power off button in gnome control center

[Roman Zabaluev]

Unfortunately, I can not provide a screenshot of available options since
neither gnome screenshot tool nor printscreen button can't capture the
screen with pop-up dialog.

** Bug watch added: GNOME Bug Tracker #781108
   https://bugzilla.gnome.org/show_bug.cgi?id=781108

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=781108
   Importance: Unknown
   Status: Unknown

** Also affects: gnome-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=781108
   Importance: Unknown
   Status: Unknown

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

Title:
  No power off option for power off button in gnome control center

Status in gnome-control-center:
  Unknown
Status in GNOME Settings Daemon:
  Unknown
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  There's no such an option to power off the machine on power button
  press.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 26 16:50:14 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-12-05 (83 days ago)

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

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

[Desktop-packages] [Bug 1751788] [NEW] No power off option for power off button in gnome control center

[Roman Zabaluev]

Public bug reported:

There's no such an option to power off the machine on power button
press.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 26 16:50:14 2018
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-12-05 (83 days ago)

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


** Tags: amd64 apport-bug artful third-party-packages

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

Title:
  No power off option for power off button in gnome control center

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

Bug description:
  There's no such an option to power off the machine on power button
  press.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 26 16:50:14 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-12-05 (83 days ago)

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

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

[Roman Shchekin]

Any news on this? It can be fixed with custom xorg, but resets after
every software updates and it is very annoying. Please, apply the patch.

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742856] [NEW] Silently stops receiving mail (agent not ready)

[Roman Odaisky]

Public bug reported:

Every couple weeks, some of my accounts silently stop receiving email as
though I’m not being sent any. I think this happens with my GMail
accounts and not with my own IMAP server, but I’m not sure. When I go to
akonadiconsole, the affected agent has nothing where other agents have
“Ready”. If I restart the agent, mail starts being received.

This is unfortunately yet another Akonadi Does Not Work problem. Please
fix.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: akonadi-server 4:17.04.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jan 12 05:53:12 2018
InstallationDate: Installed on 2015-12-17 (756 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: akonadi
UpgradeStatus: Upgraded to artful on 2017-10-16 (87 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Silently stops receiving mail (agent not ready)

Status in akonadi package in Ubuntu:
  New

Bug description:
  Every couple weeks, some of my accounts silently stop receiving email
  as though I’m not being sent any. I think this happens with my GMail
  accounts and not with my own IMAP server, but I’m not sure. When I go
  to akonadiconsole, the affected agent has nothing where other agents
  have “Ready”. If I restart the agent, mail starts being received.

  This is unfortunately yet another Akonadi Does Not Work problem.
  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: akonadi-server 4:17.04.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jan 12 05:53:12 2018
  InstallationDate: Installed on 2015-12-17 (756 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: akonadi
  UpgradeStatus: Upgraded to artful on 2017-10-16 (87 days ago)

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Roman Vrublevskiy]

As a workaround, I commented out dns=dnsmasq in 
/etc/NetworkManager/NetworkManager.conf.
Now network manager adds VPN DNS servers to /etc/resolv.conf and everything 
works as expected.

As an additional benefit, it also adds and uses additional search domains but 
only with "Use this connection only for resources on its network" unchecked, so 
all traffic is routed to the tunnel.
With working DNS I can live with it for now.

I'm on Mint 18.3 Cinnamon.

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

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

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

[Roman Shchekin]

Any news on this? It affects not only layout switching, but also a lot of 
famous and well used hotkeys, for example:
  - ctrl+shift+T in Chrome (reopen closed tab)
  - ctrl+shift+arrow in text edit
It is bloody unusable at the moment.

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731622] [NEW] package postgresql-common 173ubuntu0.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Roman Novikow]

Public bug reported:

I started my system and got: "package postgresql-common 173ubuntu0.1
failed to install/upgrade: подпроцесс установлен сценарий post-
installation возвратил код ошибки 1" but I had not been installing or
upgrading postgres last I used the computer.  It's been installed a
month ago as minim. And it works fine - I've just checked...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: postgresql-common 173ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Nov 10 13:13:38 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2017-09-19 (52 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: postgresql-common
Title: package postgresql-common 173ubuntu0.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: postgresql-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package postgresql-common 173ubuntu0.1 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  I started my system and got: "package postgresql-common 173ubuntu0.1
  failed to install/upgrade: подпроцесс установлен сценарий post-
  installation возвратил код ошибки 1" but I had not been installing or
  upgrading postgres last I used the computer.  It's been installed a
  month ago as minim. And it works fine - I've just checked...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: postgresql-common 173ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov 10 13:13:38 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-09-19 (52 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: postgresql-common
  Title: package postgresql-common 173ubuntu0.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

[Roman Brodylo]

Right after logging in. Notebook is upgraded from ubuntu-gnome 17.04 to
ubuntu 17.10, Gnome X session. Nothing special - usb flash drive is
attached, and a usb transmitter for a trackball.

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1502476] Re: Totem menubar is displayed in fullscreen mode during gnome-flaskback session

[Roman Zabaluev]

I don't think they even care about this 2yo bug. I guess switching to
VLC is the best option, guys.

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

Title:
  Totem menubar is displayed in fullscreen mode during gnome-flaskback
  session

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

Bug description:
  The menubar of Totem video player doesn't hide in fullscreen mode when
  I use gnome-flashback session.

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

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

[Desktop-packages] [Bug 1720908] Re: Firefox cannot load Flash because of libxul broken dependency

[Roman Shipovskij]

Flash works again but still crashes on context menu

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

Title:
  Firefox cannot load Flash because of libxul broken dependency

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  When I start Firefox version 56 in my console and then go to a page
  using Adobe Flash, I get the following errors:

  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
  [18352] WARNING: pipe error (114): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
  [18352] WARNING: pipe error (94): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
  [18352] WARNING: pipe error (41): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353

  Each time the problem is the same: gdk_screen_get_monitor_workarea is
  undefined. Gnome marked that function as deprecated, but Firefox
  version 55 worked just fine, whereas Firefox 56 fails with Flash.

  https://developer.gnome.org/gdk3/stable/GdkScreen.html#gdk-screen-get-
  monitor-workarea

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexis24733 F pulseaudio
   /dev/snd/controlC0:  alexis24733 F pulseaudio
  BuildID: 20170928135459
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Oct  2 17:05:32 2017
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2010-12-27 (2471 days ago)
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-33216e86-e3b0-440b-a25a-2754b1171002
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20170928135459 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2016-05-20 (500 days ago)
  dmi.bios.date: 09/16/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P55A-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1720908] Re: Firefox cannot load Flash because of libxul broken dependency

[Roman Shipovskij]

** Tags added: i386 trusty

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

Title:
  Firefox cannot load Flash because of libxul broken dependency

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  When I start Firefox version 56 in my console and then go to a page
  using Adobe Flash, I get the following errors:

  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
  [18352] WARNING: pipe error (114): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
  [18352] WARNING: pipe error (94): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
  [18352] WARNING: pipe error (41): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353

  Each time the problem is the same: gdk_screen_get_monitor_workarea is
  undefined. Gnome marked that function as deprecated, but Firefox
  version 55 worked just fine, whereas Firefox 56 fails with Flash.

  https://developer.gnome.org/gdk3/stable/GdkScreen.html#gdk-screen-get-
  monitor-workarea

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexis24733 F pulseaudio
   /dev/snd/controlC0:  alexis24733 F pulseaudio
  BuildID: 20170928135459
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Oct  2 17:05:32 2017
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2010-12-27 (2471 days ago)
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-33216e86-e3b0-440b-a25a-2754b1171002
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20170928135459 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2016-05-20 (500 days ago)
  dmi.bios.date: 09/16/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P55A-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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