[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS

[francesco]

Thanks Lukas!

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

Title:
  if-up.d files do not have effect on ubuntu 24.04 LTS

Status in ifupdown package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Some time ago I wrote a detailed answer to fix an error for lowering
  MTU size for a cisco-compatible VPN
  (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
  into-remote-machine-but-able-to-ping-vpnc/768758#768758)

  After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to
  lower the MTU size.

  In particular, if I run the following command from the terminal

  sudo ifconfig your_tunnel_name mtu 1370 up

  it seems to lower the MTU size.

  However, the script under /etc/network/if-up.d is not automatically
  triggered.

  Does something change with the newer Ubuntu version?

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


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

[Desktop-packages] [Bug 2064093] [NEW] if-up.d files do not have effect on ubuntu 24.04 LTS

[francesco]

Public bug reported:

Some time ago I wrote a detailed answer to fix an error for lowering MTU
size for a cisco-compatible VPN
(here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
into-remote-machine-but-able-to-ping-vpnc/768758#768758)

After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to
lower the MTU size.

In particular, if I run the following command from the terminal

sudo ifconfig your_tunnel_name mtu 1370 up

it seems to lower the MTU size.

However, the script under /etc/network/if-up.d is not automatically
triggered.

Does something change with the newer Ubuntu version?

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


** Tags: 24.04

** Package changed: ubuntu => network-manager (Ubuntu)

** Summary changed:

- if-up.d files does not have effect on ubuntu 24.04 LTS
+ if-up.d files do not have effect on ubuntu 24.04 LTS

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

Title:
  if-up.d files do not have effect on ubuntu 24.04 LTS

Status in network-manager package in Ubuntu:
  New

Bug description:
  Some time ago I wrote a detailed answer to fix an error for lowering
  MTU size for a cisco-compatible VPN
  (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
  into-remote-machine-but-able-to-ping-vpnc/768758#768758)

  After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to
  lower the MTU size.

  In particular, if I run the following command from the terminal

  sudo ifconfig your_tunnel_name mtu 1370 up

  it seems to lower the MTU size.

  However, the script under /etc/network/if-up.d is not automatically
  triggered.

  Does something change with the newer Ubuntu version?

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


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

[Desktop-packages] [Bug 2048398] Re: Unable to change audio volume for the speakers

[francesco]

Found a solution here (https://askubuntu.com/a/1487587/920914), which I
report for self-containment:

Current workaround is by configuring ["api.alsa.soft-mixer"] = true in
/usr/share/wireplumber/main.lua.d/50-alsa-config.lua

then, systemctl --user restart wireplumber.service

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

Title:
  Unable to change audio volume  for the speakers

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi everyone,
  from a fresh install of Ubuntu 23.04, I cannot change the audio volume for 
the speakers. Formally, the audio is either at minimum (lowest part of the 
volume control bar) or at maximum (every other part of the audio control bar). 
I can mute the speakers.

  However, audio works perfectly for headphones. The Bluetooth pairing
  is instant, and I can change the volume.

  
  HW information for the audio device is the following:
  Audio:
Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl
  bus-ID: 00:1f.3
Sound API: ALSA v: k6.2.0-39-generic running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.65 running: yes

  Other info:
  System:
Kernel: 6.2.0-39-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
  v: 44.3 Distro: Ubuntu 23.04 (Lunar Lobster)
  Machine:
Type: Laptop System: LENOVO product: 82Y7 v: Yoga Pro 7 14IRH8

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


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

[Desktop-packages] [Bug 2048398] Re: Unable to change audio volume for the speakers

[francesco]

I have the same problem in a clean install of Ubuntu 24.04 LTS

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

Title:
  Unable to change audio volume  for the speakers

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi everyone,
  from a fresh install of Ubuntu 23.04, I cannot change the audio volume for 
the speakers. Formally, the audio is either at minimum (lowest part of the 
volume control bar) or at maximum (every other part of the audio control bar). 
I can mute the speakers.

  However, audio works perfectly for headphones. The Bluetooth pairing
  is instant, and I can change the volume.

  
  HW information for the audio device is the following:
  Audio:
Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl
  bus-ID: 00:1f.3
Sound API: ALSA v: k6.2.0-39-generic running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.65 running: yes

  Other info:
  System:
Kernel: 6.2.0-39-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
  v: 44.3 Distro: Ubuntu 23.04 (Lunar Lobster)
  Machine:
Type: Laptop System: LENOVO product: 82Y7 v: Yoga Pro 7 14IRH8

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


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

[Desktop-packages] [Bug 2048398] Re: Unable to change audio volume for the speakers

[francesco]

Hi @guiverc, I confirm this issue also on 23.10.

Strangely, I can change the volume through other apps, like youtube and
Spotify.

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

Title:
  Unable to change audio volume  for the speakers

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi everyone,
  from a fresh install of Ubuntu 23.04, I cannot change the audio volume for 
the speakers. Formally, the audio is either at minimum (lowest part of the 
volume control bar) or at maximum (every other part of the audio control bar). 
I can mute the speakers.

  However, audio works perfectly for headphones. The Bluetooth pairing
  is instant, and I can change the volume.

  
  HW information for the audio device is the following:
  Audio:
Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl
  bus-ID: 00:1f.3
Sound API: ALSA v: k6.2.0-39-generic running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.65 running: yes

  Other info:
  System:
Kernel: 6.2.0-39-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
  v: 44.3 Distro: Ubuntu 23.04 (Lunar Lobster)
  Machine:
Type: Laptop System: LENOVO product: 82Y7 v: Yoga Pro 7 14IRH8

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


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

[Desktop-packages] [Bug 2048398] Re: Unable to change audio volume for the speakers

[francesco]

Hi @guiverc for your suggestion.

I think this is indeed a bug since I searched extensively on the
internet and I found several people with the same problem, but I haven't
found any solution so far. Actually, some time ago I opened a question
on askubuntu (link: https://askubuntu.com/questions/1485233/lenovo-
yoga-7i-intel-i7-13700h-cannot-change-volume-on-the-speakers,
https://askubuntu.com/questions/1466286/lenovo-yoga-slim-7-pro-volume-
cannot-be-changed, ...)


I've been using this PC since November, so it's not a fresh install. However, I 
encountered the problem since the first usage bet report here only now, so 
yeah, this "bug" is from a fresh installation of 23.04

The package in question is pulseaudio, I've updated the bug description.

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

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

Title:
  Unable to change audio volume  for the speakers

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi everyone,
  from a fresh install of Ubuntu 23.04, I cannot change the audio volume for 
the speakers. Formally, the audio is either at minimum (lowest part of the 
volume control bar) or at maximum (every other part of the audio control bar). 
I can mute the speakers.

  However, audio works perfectly for headphones. The Bluetooth pairing
  is instant, and I can change the volume.

  
  HW information for the audio device is the following:
  Audio:
Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl
  bus-ID: 00:1f.3
Sound API: ALSA v: k6.2.0-39-generic running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.65 running: yes

  Other info:
  System:
Kernel: 6.2.0-39-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
  v: 44.3 Distro: Ubuntu 23.04 (Lunar Lobster)
  Machine:
Type: Laptop System: LENOVO product: 82Y7 v: Yoga Pro 7 14IRH8

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


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

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[francesco]

re-opened due to some recent activity

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

** Information type changed from Private to Private Security

** Information type changed from Private Security to Public

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+attachment/5638914/+files/Dependencies.txt

** Attachment removed: "monitors.xml.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+attachment/5638919/+files/monitors.xml.txt

** Attachment removed: "ShellJournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+attachment/5638918/+files/ShellJournal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+attachment/5638917/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+attachment/5638916/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+attachment/5638915/+files/GsettingsChanges.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/1982560

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] monitors.xml.txt

[francesco]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1982560/+attachment/5638919/+files/monitors.xml.txt

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] ShellJournal.txt

[francesco]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1982560/+attachment/5638918/+files/ShellJournal.txt

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] ProcEnviron.txt

[francesco]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1982560/+attachment/5638917/+files/ProcEnviron.txt

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] ProcCpuinfoMinimal.txt

[francesco]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1982560/+attachment/5638916/+files/ProcCpuinfoMinimal.txt

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] GsettingsChanges.txt

[francesco]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1982560/+attachment/5638915/+files/GsettingsChanges.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/1982560

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[francesco]

apport information

** Tags added: apport-collected

** Description changed:

  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.
  
- Specifically, frequent mouse lag when I turn on the pc, when I unlock
- the pc or when heavy operations are done on it.
+ Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-11-13 (50 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: gnome-shell 42.5-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
+ RelatedPackageVersions: mutter-common 42.5-0ubuntu1
+ Tags:  jammy wayland-session
+ Uname: Linux 5.15.0-56-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1982560/+attachment/5638914/+files/Dependencies.txt

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[francesco]

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

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

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

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock
  the pc or when heavy operations are done on it.

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


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

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[francesco]

Hi Daniel, after few days of testing I can say that with these options
the problem is much less evident, but still present.

Indeed, I have fewer lag and stutter (the system now is usable also with
wayland session, before that option it was not) but it is not as fluid
as Xorg. When I unlock the pc, a few frame missed are always present.
Overall this is a progress, but in my opinion not a general solution.

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock
  the pc or when heavy operations are done on it.

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


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

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[francesco]

Hi Daniel, thanks! Currently testing these options. It would be helpful
if others would do the same.

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock
  the pc or when heavy operations are done on it.

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


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

[Desktop-packages] [Bug 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on

[francesco]

Also have this issue again in 22.04.1 LTS version.

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

Title:
  Wi-Fi becomes unusally slow all of a sudden and forces me to turn off
  Wi-Fi and then turn it back on

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden
  and I will then be forced to turn the Wi-Fi off and then back on
  again, which is annoying. And even then, the Wi-Fi becomes unusually
  slow afterwards.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  network-manager:
    Installed: 1.10.6-2ubuntu1.2
    Candidate: 1.10.6-2ubuntu1.2
    Version table:
   *** 1.10.6-2ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.10.6-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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


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

[Desktop-packages] [Bug 1936966] Re: Libreoffice 7.x uses wrong desktop/panel/window icons for Template wizards

[Francesco Aloisio]

It still happens in version 7.3.5.2 flatpak too

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

Title:
  Libreoffice 7.x uses wrong desktop/panel/window icons for Template
  wizards

Status in LibreOffice:
  New
Status in bamf package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with Unity and MATE desktops
  2. Add LO PPA, install full LO by

     sudo add-apt-repository ppa:libreoffice/ppa
     sudo apt-get update
     sudo apt-get install libreoffice

  3a. Launch Libreoffice Impress, wait the Select a Template window to appear 
on task bar/window list
  3b. Launch Libreoffice Writer, click on File → Templates → Manage templates, 
wait Templates window to appear on task bar/window list
  3c. Launch Libreoffice Calc, click on File → Templates → Manage templates, 
wait Templates window to appear on task bar/window list
  3d. Launch Libreoffice Draw, click on File → Templates → Manage templates, 
wait Templates window to appear on task bar/window list

  Expected results:
  * all Template windows use correct desktop/panel/window icons on task 
bar/window list

  Actual results:
  * all Template windows use wrong  desktop/panel/window icons on task 
bar/window list

  Details:

   libreoffice1:7.1.4~rc2-0ubuntu0.18.04.1~lo1

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


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

[Desktop-packages] [Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

[Francesco Abeni]

I currently have the bug with Firefox 103.0b9 and mutter 42.2-0ubuntu1.
It went away for a while then it came back; I was not able to determine
the exact version which determined the (possible) regression. I am
available for tests and any additional information if it can help. Thank
you in advance for your time.

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

Title:
  Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

Status in Mozilla Firefox:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

  A similar behavior can also be observed in gedit, nautilus and other
  GNOME applications whether they are confined or not (while snapped
  ones seems to underline the issue more)

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


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

[Desktop-packages] [Bug 1979143] [NEW] Segmentation fault after UI elements misplaced

[Francesco Castellana]

Public bug reported:

Not sure how it started and what causes it, but now every time I open the 
properties window of a torrent, some UI labels would be misplaced (i.e. text 
appears in the wrong places in the UI).
After a few minutes of these UI issues, transmission crashes with Segmentation 
fault.

Running it from the terminal shows a lot of GTK error messages, e.g.:

Gtk-CRITICAL **: 00:22:03.053: gtk_label_set_text: assertion
'GTK_IS_LABEL (label)' failed

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: transmission-gtk 3.00-2ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
Uname: Linux 5.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 20 00:46:02 2022
InstallationDate: Installed on 2021-03-10 (466 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: transmission
UpgradeStatus: Upgraded to jammy on 2022-04-28 (51 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Segmentation fault after UI elements misplaced

Status in transmission package in Ubuntu:
  New

Bug description:
  Not sure how it started and what causes it, but now every time I open the 
properties window of a torrent, some UI labels would be misplaced (i.e. text 
appears in the wrong places in the UI).
  After a few minutes of these UI issues, transmission crashes with 
Segmentation fault.

  Running it from the terminal shows a lot of GTK error messages, e.g.:

  Gtk-CRITICAL **: 00:22:03.053: gtk_label_set_text: assertion
  'GTK_IS_LABEL (label)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 00:46:02 2022
  InstallationDate: Installed on 2021-03-10 (466 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (51 days ago)

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


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

[Desktop-packages] [Bug 1901381] Re: libsane regression error in Ubuntu 20.10: scanner not found

[Francesco V]

Hi, Houni,
really thanks for your help, I workaround to this issue.

Specifying USB in plustek.conf does not fix the issue, suggestion of
Pascal Dormeau works for me (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=971584#57).

$ cat /etc/tmpfiles.d/my-sane-lock.conf 
d   /var/lock/sane  0775root  scanner -   -

I confirm you that this issue is still present, none of this work was
requested in 20.04 version.

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

Title:
  libsane regression error in Ubuntu 20.10: scanner not found

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I recently update my Kubuntu from 20.04 to

  Description:Ubuntu 20.10
  Release:20.10

  After the upgrade, it is no longer possible to scan documents using CanoScan 
N1240U.
  lsusb and sane-find-scanner detected the scanner while scanimage, skanlite 
and xsane cannot found it.
  I checked permission, I ran these tools as root, I configured plustek.conf 
manually but nothing worked.

  Finally I rollback libsane, libsane1 and libsane-common from 1.0.31-2
  to 1.0.29-0ubuntu5.2 and the scanner is detected out-of-the-box.

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

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

[Desktop-packages] [Bug 1901381] [NEW] libsane regression error in Ubuntu 20.10: scanner not found

[Francesco V]

Public bug reported:

I recently update my Kubuntu from 20.04 to

Description:Ubuntu 20.10
Release:20.10

After the upgrade, it is no longer possible to scan documents using CanoScan 
N1240U.
lsusb and sane-find-scanner detected the scanner while scanimage, skanlite and 
xsane cannot found it.
I checked permission, I ran these tools as root, I configured plustek.conf 
manually but nothing worked.

Finally I rollback libsane, libsane1 and libsane-common from 1.0.31-2 to
1.0.29-0ubuntu5.2 and the scanner is detected out-of-the-box.

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libsane regression error in Ubuntu 20.10: scanner not found

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I recently update my Kubuntu from 20.04 to

  Description:Ubuntu 20.10
  Release:20.10

  After the upgrade, it is no longer possible to scan documents using CanoScan 
N1240U.
  lsusb and sane-find-scanner detected the scanner while scanimage, skanlite 
and xsane cannot found it.
  I checked permission, I ran these tools as root, I configured plustek.conf 
manually but nothing worked.

  Finally I rollback libsane, libsane1 and libsane-common from 1.0.31-2
  to 1.0.29-0ubuntu5.2 and the scanner is detected out-of-the-box.

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

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

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Francesco Guarneri]

> sudo update-initramfs -u

This is what I was missing. Thank you so much!

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Francesco Guarneri]

Hi! Managed to reproduce the steps described in #211 (using the updated
archive provided in #217) and #212. The touchpad seems to be working
after running

$ sudo rmmod i2c-hid
$ sudo insmod full-path/i2c-hid.ko polling_mode=1

I need to provide the full path to the i2c-hid.ko module, otherwise the system 
returns "could not load module "i2c-hid.ko: No such file or directory"; not 
sure if this is already an issue.
However, I am not sure how to add the boot parameter to GRUB. I followed this 
(https://wiki.ubuntu.com/Kernel/KernelBootParameters) and tried adding either 
one of these three options:

i2c-hid.polling_mode=1
full-path/i2c-hid.polling_mode=1
full-path/i2c-hid.ko.polling_mode=1

but neither seems to be working. Am i doing something wrong? Using
Ubuntu 20.04.1 with kernel 5.8.16. Also, total noob and first time
writing here, so hopefully not causing issues.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Francesco Grieco]

I think this issue is covering different devices.

I have a Lenovo Ideapad 14ARE05 with the following touchpad:

MSFT0004:00 06CB:CD98

(synaptic? similar to the Legion, I suppose)

And I have the same problem of others, the touchpad sometime works,
sometime not.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 

[Desktop-packages] [Bug 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on

[francesco]

This bug affects me as well but in ubuntu 20.04. It's very annoying.

I've open a question ->
https://answers.launchpad.net/ubuntu/+question/692509

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

Title:
  Wi-Fi becomes unusally slow all of a sudden and forces me to turn off
  Wi-Fi and then turn it back on

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden
  and I will then be forced to turn the Wi-Fi off and then back on
  again, which is annoying. And even then, the Wi-Fi becomes unusually
  slow afterwards.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  network-manager:
Installed: 1.10.6-2ubuntu1.2
Candidate: 1.10.6-2ubuntu1.2
Version table:
   *** 1.10.6-2ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.10.6-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 20:35:53 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  wifi  
1575941718  Mon 09 Dec 2019 08:35:18 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  28634e82-4c1c-3a61-b152-3bd92aaa6992  ethernet  
1575939877  Mon 09 Dec 2019 08:04:37 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp4s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1543 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Atheros 

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

[Francesco Salvi]

To add on my previous comment: after moving to 19.10 (which I think also
comes with its pre-bundled nvidia driver, in any case I'm on 430 now),
the issue seems to be greatly mitigated compared with what I was having
on ubuntu 19.04... like I'm getting it once a day at most (no consistent
repro case though)

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

[Francesco Salvi]

After upgrading to ubuntu 19.10 (and mutter 3.34.1), I cannot
consistently reproduce it as I used to before (vscode tab drag or chrome
bookmark drag) but I still managed to get it randomly while upgrading
some gnome extension

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1846371]

[Francesco-lodolo]

(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #10)
> Can you revert that change in L10nRegistry.jsm and see if you can still 
> reproduce? I doubt that this is the culprit because this change doesn't 
> really affect anything except of protecting against race between sync/async.

Artifact build from current mozilla-central tip

1) Build and run
2) Create a new profile
3) In `about:config` set `intl.multilingual.enabled` to true
4) Install French language pack from the latest mozilla-central-l10n available, 
luckily there might not be new DTD strings loaded on startup…. In my case this 
worked
http://archive.mozilla.org/pub/firefox/nightly/2019/10/2019-10-04-09-46-56-mozilla-central-l10n/linux-x86_64/xpi/
5) Open preferences, switch the language to French and restart. At this point, 
the browser should reopen on Preferences in French, but they're in English, 
even after reloading the page.

I tried undoing the changes to L10nRegistry.jsm, but it didn't solve the issue. 
But removing `data-l10n-sync="true"` from `browser/base/content/browser.xhtml` 
seems to do it.
https://hg.mozilla.org/integration/autoland/rev/1f622156e9eab1d2c58d5d77bb5908fcc83db253#l4.13

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

Title:
  firefox 70.0 beta 11 isn't fully translated

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

Bug description:
  (this was initially spotted by ricotz)

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

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

  Partially translated:
   - about:addons

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

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

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

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

[Desktop-packages] [Bug 1846371]

[Francesco-lodolo]

Even starting with `-purgecaches` doesn't help.

Requested locales is correct `["fr","it"]`, but even about:support stays
in the language of the build (Italian in my case).

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

Title:
  firefox 70.0 beta 11 isn't fully translated

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

Bug description:
  (this was initially spotted by ricotz)

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

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

  Partially translated:
   - about:addons

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

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

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

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

[Desktop-packages] [Bug 1846371]

[Francesco-lodolo]

Disabling and re-enabling the language packs seems to trigger something,
and things start to get localized as expected.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

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

Bug description:
  (this was initially spotted by ricotz)

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

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

  Partially translated:
   - about:addons

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

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

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

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

[Desktop-packages] [Bug 1846371]

[Francesco-lodolo]

[Tracking Requested - why for this release]: It's very late, but we're
providing users with language packs a very poor experience.

I'm trying to run mozregression to identify the bug causing this, but
it's the most painful process imaginable.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

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

Bug description:
  (this was initially spotted by ricotz)

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

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

  Partially translated:
   - about:addons

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

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

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

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

[Desktop-packages] [Bug 1846371]

[Francesco-lodolo]

I can't narrow down further, because all language packs on FTP for that
day cause a YSOD.

@zibi
The only relevant bug seems to be the one migrating menubar to Fluent (it does 
touch L10nRegistry.jsm, no clue if that could be the cause of this)
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e78733e0ffcfe52903aba0a02952cd800b89ca8d=ff0125384d06fefae3ca60435b85a9be0fd9744e

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

Title:
  firefox 70.0 beta 11 isn't fully translated

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

Bug description:
  (this was initially spotted by ricotz)

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

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

  Partially translated:
   - about:addons

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

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

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

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

[Desktop-packages] [Bug 1846371]

[Francesco-lodolo]

Thanks for the detailed report, I can confirm the behavior on 70.0b11
(64 bit).

@zibi
Did anything change in the caching system? That's all Fluent elements, which 
should even change without a restart.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

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

Bug description:
  (this was initially spotted by ricotz)

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

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

  Partially translated:
   - about:addons

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

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

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

[Desktop-packages] [Bug 1827727]

[Francesco-lodolo]

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

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

Title:
  All plugins disabled due to expired cert

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

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to expiration of an intermediate cert, all plugins were disabled.
  Firefox pushed a fix via 'Studies' option, but this seems to be disabled by 
default in Ubuntu builds?

  When this is disabled, no update is getting pushed!

  Think we need to get a fix into repositories asap :)

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

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

Re: [Desktop-packages] [Bug 1278052] Re: Mounted partitons use the same launcher icon as the home folder

[Francesco Tarantini]

Dear Sebastian,
I am afraid I have no access on Ubuntu anymore to test.

Best wishes,
Francesco

On Mon, 28 Jan 2019 at 16:35, Sebastien Bacher 
wrote:

> Do you still have that issue in newer Ubuntu versions?
>
> ** Changed in: nautilus (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: nautilus (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1278052
>
> Title:
>   Mounted partitons use the same launcher icon as the home folder
>
> Status in nautilus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Ubuntu 13.10. On my launcher I have an icon for my data partition and
> the default icon for my home folder. When I click on the partition icon, a
> nautilus window opens, showing the content of that partition (let's call it
> 'window A').
>   The problem is that 'window A' uses the home icon insted of the
> partition icon (i.e. the home icon is highlighted), so after you minimize
> 'window A' you'd have to click on the home icon to bring it up again, but
> of course this opens your home folder instead. Clicking on the partition
> icon does nothing, not even open a new partition window.
>   The only way to bring 'window A' up again is using the scrollwheel,
> which is normally used to switch between different windows of the same
> application.
>   I think that windows for partitions should use their own icons, so it
> would be easier to manage them and understand whether you have your home
> folder or your partition opened.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1278052/+subscriptions
>

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

Title:
  Mounted partitons use the same launcher icon as the home folder

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10. On my launcher I have an icon for my data partition and the 
default icon for my home folder. When I click on the partition icon, a nautilus 
window opens, showing the content of that partition (let's call it 'window A').
  The problem is that 'window A' uses the home icon insted of the partition 
icon (i.e. the home icon is highlighted), so after you minimize 'window A' 
you'd have to click on the home icon to bring it up again, but of course this 
opens your home folder instead. Clicking on the partition icon does nothing, 
not even open a new partition window.
  The only way to bring 'window A' up again is using the scrollwheel, which is 
normally used to switch between different windows of the same application.
  I think that windows for partitions should use their own icons, so it would 
be easier to manage them and understand whether you have your home folder or 
your partition opened.

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

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

[Desktop-packages] [Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time

[Francesco Pretto]

I think what reported by Lorens may be totally unrelated to the use of
Chrome. The use of VirtualBox, latest version 5.2.18, with a Ubuntu
18.04 64bit guest with 3D acceleration **enabled** and maximum VRAM
configured (128MB) is completely unusable because of extremely high
memory usage of gnome-shell, independently of the application launched:
you can launch nothing or launch firefox, for example, and the session
will become unusable pretty soon. It may be worth some more
investigation of VirtualBox+3D acceleration use case. My host is
actually Windows 10 64bit.

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

Title:
  gnome-shell + chrome doing nothing consumes high CPU all the time

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  This is somewhat similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1696305

  After a few cycles of suspend, working with external monitor, running
  Chrome with 10+ opened tabs causes gnome-shell and chrome to use 60%
  of CPU just idling. When I do some more active work - it consumes even
  more. My laptop is hot all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 10:34:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-01-31 (474 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/1772365/+subscriptions

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

[Desktop-packages] [Bug 545044] Re: Xdg-open should use kde-open instead of kfmclient

[Francesco Belladonna]

If you need a temporary fix to this issue to get xdg-open to work (lot
of tools depend on it), I recommend exporting the environment variable
KDE_SESSION_VERSION=5 (or 4 or 6 or whatever is your KDE version). Fixes
the problem (this environment variable is entirely missing in my
installation)

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

Title:
  Xdg-open should use kde-open instead of kfmclient

Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xdg-utils

  In /usr/bin/xdg-open, open_kde attempts to use the kfmclient binary to
  open the provided URI. Kfmclient is according to Ubuntu package
  database
  
(http://packages.ubuntu.com/search?searchon=contents=kfmclient=exactfilename=lucid=any),
  only available in the konqueror package, and in the kdebase-dbg (only
  in PATH from the Konqueror package).

  Neither of these two packages is a natural requirement for basic xdg-
  open functionality under a KDE-environment. Currently, unless the user
  has Konqueror installed, xdg-open falls back to open_generic
  sidestepping any KDE-configs.

  However, KDE does have a similar utility, kde-open, which does the
  same thing as xdg-open, and should be used instead of kfmclient.

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

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

[Desktop-packages] [Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

[Francesco De Caro]

With proposed the issue is solved.

Before:

dpkg: error processing archive 
/var/cache/apt/archives/libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb 
(--unpack):
 libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
Errors were encountered while processing:
 /var/cache/apt/archives/libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

After:

Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 
libp11-kit-gnome-keyring amd64 3.28.0.2-1ubuntu1.18.04.1 [3.228 B]
Fetched 3.228 B in 0s (23,8 kB/s)   
(Reading database ... 548794 files and directories currently installed.)
Preparing to unpack 
.../libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1.18.04.1_amd64.deb ...
Unpacking libp11-kit-gnome-keyring:amd64 (3.28.0.2-1ubuntu1.18.04.1) over 
(3.20.1-1ubuntu1) ...
Setting up libp11-kit-gnome-keyring:amd64 (3.28.0.2-1ubuntu1.18.04.1) ...


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

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Bionic:
  Fix Committed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1754199] Re: Mounted Volume ICON not displayed on desktop

[Francesco Fumanti]

I am experiencing the same problem on bionic.

My system is an upgrade from artful.

The NFS shares are mounted at: 
/media/sharename 

I don't know whether it is relevant, but I am still using the Unity 7
desktop on bionic.

The shortcuts of the NFS mounts were visible in nautilus on artful,
where I was also using the Unity 7 desktop.

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

Title:
  Mounted Volume ICON not displayed on desktop

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Have several NFS volumes that I mount and unmount.  Have always seen
  the volume ICON show up on the desktop and the nautilus shortcut panel
  but this is no longer occurring in 18.04.  The mount is available.
  Have verified that the tweaks-ui setting is ON for mounted volumes.
  Believe this was ok in earlier daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 19:17:45 2018
  InstallationDate: Installed on 2018-03-05 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1762577] [NEW] package texlive-latex-base-doc 2013.20140215-1ubuntu0.1 failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/texlive-doc/latex/url/url.tex.gz" pr

[Francesco]

Public bug reported:

i was trying to update some latex packages, but I got some problems during 
intallation.
then i try to recover and reset the installed packages to restore old version 
of dblatex and other connected packages.
now i cannot proceed in both solution: try to purge or try to reinstall.

the "E: Sub-process /usr/bin/dpkg returned an error code (1)" is the error when 
i try to remove/purge/reinstall/install these packages:
- context
- dblatex
- lilypond-data


thks

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: texlive-latex-base-doc 2013.20140215-1ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-145.194-generic 3.13.11-ckt39
Uname: Linux 3.13.0-145-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Mon Apr  9 22:30:37 2018
DuplicateSignature: 
package:texlive-latex-base-doc:2013.20140215-1ubuntu0.1:tentata sovrascrittura 
di "/usr/share/doc/texlive-doc/latex/url/url.tex.gz" presente anche nel 
pacchetto texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
ErrorMessage: tentata sovrascrittura di 
"/usr/share/doc/texlive-doc/latex/url/url.tex.gz" presente anche nel pacchetto 
texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
InstallationDate: Installed on 2014-01-26 (1534 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.17
SourcePackage: texlive-base
Title: package texlive-latex-base-doc 2013.20140215-1ubuntu0.1 failed to 
install/upgrade: tentata sovrascrittura di 
"/usr/share/doc/texlive-doc/latex/url/url.tex.gz" presente anche nel pacchetto 
texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
UpgradeStatus: Upgraded to trusty on 2016-02-15 (784 days ago)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package texlive-latex-base-doc 2013.20140215-1ubuntu0.1 failed to
  install/upgrade: tentata sovrascrittura di "/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz" presente anche nel pacchetto texlive-latex-
  recommended-doc 2013.20140215-1ubuntu0.1

Status in texlive-base package in Ubuntu:
  New

Bug description:
  i was trying to update some latex packages, but I got some problems during 
intallation.
  then i try to recover and reset the installed packages to restore old version 
of dblatex and other connected packages.
  now i cannot proceed in both solution: try to purge or try to reinstall.

  the "E: Sub-process /usr/bin/dpkg returned an error code (1)" is the error 
when i try to remove/purge/reinstall/install these packages:
  - context
  - dblatex
  - lilypond-data

  
  thks

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-latex-base-doc 2013.20140215-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-145.194-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-145-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Mon Apr  9 22:30:37 2018
  DuplicateSignature: 
package:texlive-latex-base-doc:2013.20140215-1ubuntu0.1:tentata sovrascrittura 
di "/usr/share/doc/texlive-doc/latex/url/url.tex.gz" presente anche nel 
pacchetto texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  ErrorMessage: tentata sovrascrittura di 
"/usr/share/doc/texlive-doc/latex/url/url.tex.gz" presente anche nel pacchetto 
texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  InstallationDate: Installed on 2014-01-26 (1534 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc 2013.20140215-1ubuntu0.1 failed to 
install/upgrade: tentata sovrascrittura di 
"/usr/share/doc/texlive-doc/latex/url/url.tex.gz" presente anche nel pacchetto 
texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  UpgradeStatus: Upgraded to trusty on 2016-02-15 (784 days ago)

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

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

[Desktop-packages] [Bug 1756013] Re: 2 instances of onboard onscreen keyboard running and settings only applying to one

[Francesco Fumanti]

The main problem is that Onboard was not designed to work with GNOME3,
that has restrictions, that Onboard can hardly bypass. (Onboard is also
incompatible to Wayland, which is an additional issue.) There is a gnome
extension for Onboard that slightly improves the situation, but a proper
compatibility with GNOME 3 requires Onboard to be rewritten, having the
restrictions of GNOME 3 in mind. A rewrite of Onboard started some time
ago under the name of OnboardOSK; but I don't know what state OnboardOSK
is in.

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

Title:
  2 instances of onboard onscreen keyboard running and settings only
  applying to one

Status in onboard package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04 Bionic Beaver development branch
  Onboard 1.4.1-2ubuntu1

  An onscreen keyboard comes installed by default, but it's not very usable
  * Lack of buttons 
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1755987
  * Pipe doesn't work 
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1755985
  * Uppercase is broken 
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1755983

  I tried changing the settings for the onscreen keyboard, selecting the "Full" 
layout (instead of "Compact"), but found the settings did not take effect even 
after a reboot.
  https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1755988

  Then I ran onboard from the launcher, and the full keyboard appeared at the 
bottom of the screen *constantly* and resized the rest of my screen smaller.
  With the full layout, uppercase works, and so far it seems fine.

  However now whenever I click on any window that has a text input, the
  buggy compact onscreen keyboard appears over the working full layout
  onscreen keyboard.

  I actually like the behavior of the buggy compact onscreen keyboard's
  ability to show/hide as needed vs the full "onboard" keyboard
  displaying constantly.

  So right now it's a bit of a mess, sorry if I should have reported
  each issue as part of a single bug report.

  Desired outcome:
  1. The automatically displayed keyboard should respect the settings (eg: the 
layout) set by onboard-settings.
  2. If I run onboard manually, meaning it stays at the bottom of the screen 
constantly, another instance should not automatically pop up over it.

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

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

[Desktop-packages] [Bug 1723253] [NEW] package gnome-keyring 3.20.0-3ubuntu2 failed to install/upgrade: tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so" presente an

[francesco]

Public bug reported:

 I don't know

ProblemType: Package
DistroRelease: Kali 2017.2
Package: gnome-keyring 3.20.0-3ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Thu Oct 12 21:09:30 2017
ErrorMessage: tentata sovrascrittura di 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so" presente anche nel 
pacchetto libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
InstallationDate: Installed on 2017-09-06 (36 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.24kali2
 apt  1.4.6~17.04.1
SourcePackage: gnome-keyring
Title: package gnome-keyring 3.20.0-3ubuntu2 failed to install/upgrade: tentata 
sovrascrittura di "/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so" 
presente anche nel pacchetto libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package gnome-keyring 3.20.0-3ubuntu2 failed to install/upgrade:
  tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/pkcs11/gnome-
  keyring-pkcs11.so" presente anche nel pacchetto libp11-kit-gnome-
  keyring:amd64 3.20.0-3ubuntu2

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Kali 2017.2
  Package: gnome-keyring 3.20.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Thu Oct 12 21:09:30 2017
  ErrorMessage: tentata sovrascrittura di 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so" presente anche nel 
pacchetto libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
  InstallationDate: Installed on 2017-09-06 (36 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.24kali2
   apt  1.4.6~17.04.1
  SourcePackage: gnome-keyring
  Title: package gnome-keyring 3.20.0-3ubuntu2 failed to install/upgrade: 
tentata sovrascrittura di 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so" presente anche nel 
pacchetto libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719152] [NEW] package texlive-latex-recommended-doc 2016.20170123-5 failed to install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato di errore 2

[Francesco Uboldi]

Public bug reported:

package texlive-latex-recommended-doc 2016.20170123-5 failed to
install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito
lo stato di errore 2

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: texlive-latex-recommended-doc 2016.20170123-5
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Sat Sep 23 21:07:22 2017
ErrorMessage: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato 
di errore 2
InstallationDate: Installed on 2017-09-23 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: texlive-base
Title: package texlive-latex-recommended-doc 2016.20170123-5 failed to 
install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo 
stato di errore 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package texlive-latex-recommended-doc 2016.20170123-5 failed to
  install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha
  restituito lo stato di errore 2

Status in texlive-base package in Ubuntu:
  New

Bug description:
  package texlive-latex-recommended-doc 2016.20170123-5 failed to
  install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha
  restituito lo stato di errore 2

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: texlive-latex-recommended-doc 2016.20170123-5
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sat Sep 23 21:07:22 2017
  ErrorMessage: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo stato 
di errore 2
  InstallationDate: Installed on 2017-09-23 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: texlive-base
  Title: package texlive-latex-recommended-doc 2016.20170123-5 failed to 
install/upgrade: il sottoprocesso dpkg-deb --fsys-tarfile ha restituito lo 
stato di errore 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1704397] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Francesco Milano]

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

Public bug reported:

generated by the system

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
Date: Sat Jul  8 09:18:57 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-26 (17 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  generated by the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sat Jul  8 09:18:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-26 (17 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1672465] Re: Onboard doesn't work in Wayland

[Francesco Fumanti]

Hi Sebastien,

First of all, thanks for you appreciating our team and we also hope to
continue the cooperation with you.

As Onboard has more features than Caribou, there already has been some demand 
for its integration into GNOME and people have also done some work on it; for 
example: 
https://stackoverflow.com/questions/33065735/replacing-gnomes-virtual-keyboard-with-onboard-hide-show-via-dbus-doesnt-wor

In the meantime, Onboard is shipping an own extension for its integration into 
GNOME shell. 
https://launchpad.net/ubuntu/xenial/amd64/gnome-shell-extension-onboard
https://bugs.launchpad.net/onboard/+bug/1538627

The release for zesty does not fully support GNOME shell yet, but since
Ubuntu has decided to switch to GNOME Shell and Wayland, these two items
have become high priority for us and marmuta is currently actively
working on the port. He told me that he made some progress, but he is
better placed than me to give you details on it, so I leave it up to
him.

As far as I know, Lightdm is also being replaced by GDM, which will also
be relevant for Onboard...

Thanks again for contacting us.

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

Title:
  Onboard doesn't work in Wayland

Status in Onboard:
  In Progress
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Onboard 1.4.1 on Ubuntu GNOME 17.04

  Onboard at least shows the keyboard now in GNOME on Wayland. But it
  doesn't send key presses to gedit or other native Wayland apps.

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

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

[Desktop-packages] [Bug 1699844] Re: Onboard settings and scanning problem

[Francesco Fumanti]

You did probably install Onboard from our Stable PPA, which does not include 
the fix yet. Could you please try the Onboard version from our Snapshots PPA, 
which includes the fixes marmuta cited above? 
https://launchpad.net/~onboard/+archive/ubuntu/snapshots

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

Title:
  Onboard settings and scanning problem

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  I´ve configured scanning option on onboard.
  In Version 0.97 there was a bug that doesn´t open keyboard with such 
configuration
  In this version (1.4.1) i´m trying to open onboard-settings and it gives me 
the error:

  Traceback (most recent call last):
File "", line 2, in 
File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 311, in 
__init__
  builder = LoadUI("settings")
File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 71, in 
LoadUI
  builder.add_from_file(os.path.join(config.install_dir, filebase+".ui"))
File "/usr/lib/python3/dist-packages/gi/types.py", line 43, in function
  return info.invoke(*args, **kwargs)
  gi._glib.GError: /usr/share/onboard/settings.ui:2126:1  requires 
attribute "id"

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

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

[Desktop-packages] [Bug 1672465] Re: Onboard doesn't work in Wayland

[Francesco Fumanti]

** Changed in: onboard
   Status: Confirmed => In Progress

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

Title:
  Onboard doesn't work in Wayland

Status in Onboard:
  In Progress
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Onboard 1.4.1 on Ubuntu GNOME 17.04

  Onboard at least shows the keyboard now in GNOME on Wayland. But it
  doesn't send key presses to gedit or other native Wayland apps.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

oard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

ositioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

s warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

  * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

ple
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

nable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

ple
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

 Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

oard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

citely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

xit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

djustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

oard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

oard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

oard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

ple
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

oard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

  PS: This is a bit of topic, but in my opinion nevertheless worth
  mentioning here:

  Marmuta and I are experiencing crashes to login when Onboard is
  running and menus, especially the appindicator menus are used. On my
  system, the crashes seem to happen especially, when also mozilla
  applications (firefox or thunderbird) are running.

  I have been told that the problem should probably be fixed in libatk
  or unity-panel-service.

  As the crashes also occur with the Onboard version currently in the
  main repository, I assume that it should not be crucial for this
  sponsorship review.

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

n:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.
  
  Thanks in advance for your help.
  
  Have a good day.
  
  Francesco
+ 
+ PS: This is a bit of topic, but in my opinion nevertheless worth
+ mentioning here:
+ 
+ Marmuta and I are experiencing crashes to login when Onboard is running
+ and menus, especially the appindicator menus are used. On my system, the
+ crashes seem to happen especially, when also mozilla applications
+ (firefox or thunderbird) are running.
+ 
+ I have been told that the problem should probably be fixed in libatk or
+ unity-panel-service.
+ 
+ As the crashes also occur with the Onboard version currently in the main
+ repository, I assume that it should not be crucial for this sponsorship
+ review.

** Attachment added: "onboard_1.4.0-1ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1664746/+attachment/4819221/+files/onboard_1.4.0-1ubuntu1.dsc

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  New

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

ple
    * Update build instructions in README for Arch and Mageia
    * Improve uninstall instructions in README

  The source code has been tested against Unity and several other DEs.

  The debianisation builds successfully in pbuilder and I am currently
  running the resulting debian packages.

  Could anybody please review the package for inclusion into the main
  zesty repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

.patch:
+ - Update system-theme-associations example key
+ - Add DEP3 tag
+ - Refresh
+   * debian/source.lintian-overrides:
+ - Create file
+ - Override 2 missing-license-paragraph-in-dep5-copyright entries
+   * Tablet-mode: (LP: #1366421)
+ - Add detection based on acpid reporting the SW_TABLET_MODE switch
+ - Add detection based on hotkey events from XInput
+ - Add detection by reading tablet-mode state from a few known sysfs paths
+ - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
+ - Only run GlobalKeyListener when necessary
+ - Add tablet-mode settings to Preferences->Auto-show->Convertibles
+   * GNOME Shell:
+ - Add edge-drag gesture to show the keyboard in GNOME Shell
+ - Add option to gnome-shell-extension-prefs to disable edge-drag
+ - Enable auto-show only on first start (LP: #1650810)
+ - Fix setup.py to have distutils-extra not open extension dir as a file
+ - Stop the legacy icon panel from sliding in and out all the time
+ - Add license and copyright header to gschema.xml
+ - Fix broken string in prefs.js
+ - Fix copyright information in prefs.js
+ - Clean up prefs.js
+ - Remove debug output
+   * Auto-show:
+ - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
+ - Improve reliability in Unity Dash by reacting only to crucial events
+ - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
+ - Allow to block auto-show while external keyboards are connected
+ - Don't auto-hide while keys are still pressed.
+   * External keyboard detection:
+ - Detect keyboards with udev
+ - Add new preference subpage Preferences->Auto-show->External Keyboards
+ - Allow devices to be ignored; e.g. always connected keyboard
+   * onboard-autostart.desktop: (LP #1656779)
+ - Rename it to onboard-autostart.desktop.in
+ - Add _GenericName, _Comment and Icon keys
+ - Make it translatable
+   * Move listening for global key presses to new GlobalKeyListener.py file
+   * Have separate resize protection preference for floating icon and keyboard
+   * Add scale for label popup size to Preferences->Keyboard
+   * Switch position of "play sound" and "label popups" in Preferences-Keyboard
+   * Add MATE'S ContrastHighInverse to the map of known accessibility themes
+   * Replace deprecated GdkScreen.get_monitor_workarea()
+   * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
+   * Indicate in log when Onboard has been started from the project directory
+   * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
+   * Reorganize AtspiStateTracker for saner handling of multiple accessibles
+   * Update licensing tool for gnome shell extension
+   * Explicitely clean up Applndicator status icon on exit
+   * Improve error handling when opening layouts files
+   * Work around firefox 50 urlbar losing focus and giving wrong caret position
+   * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
+   * Work around byobu not reporting trailing spaces
+   * Fix -Wstrict-prototypes warning when building C++ extension lm
+   * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
+   * Fix geometry hints for minimum size calculation error on startup
+   * Fix startup failure on Arch Linux when libdbus-glib isn't installed
+   * Fix signed/unsigned comparison warnings when building in Arch Linux
+   * Make sure to hide label popups when the keyboard is hidden
+   * Ease adjustment of aspect ratio with more handles when docked and expanded
+   * Keep more distance when auto-positioning to the Dash search entry
+   * Enable docking by default in onboard-defaults.conf.example
+   * Update build instructions in README for Arch and Mageia
+   * Improve uninstall instructions in README
  
+ The source code has been tested against Unity and several other DEs.
+ 
+ The debianisation builds successfully in pbuilder and I am currently
+ running the resulting debian packages.
  
  Could anybody please review the package for inclusion into the main
  zesty repository.
  
  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.
  
  Thanks in advance for your help.
  
  Have a good day.
  
  Francesco

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  New

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of 

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

** Description changed:

- Info to be added soon...
+ Version 1.4.0 of Onboard has been released upstream several hours ago. I
+ am proposing here a debianisation of the new version, based on onboard
+ version currently shipping in the Ubuntu main repository. These are the
+ main changes of the new Onboard version, copied from the relevant part
+ of the debian/changelog:
+ 
+   * Request for sponsorship for new upstream release (LP: #1664746)
+   * debian/control:
+ - Add libudev-dev to Build-Depends
+   * debian/copyright.in:
+ - Replaced by a more accurate, manually adjusted copyright file
+   * debian/onboard.install:
+ - Remove settings_auto_show_dialog.ui entry
+   * debian/patches/add_defaults_for_ubuntu.patch:
+ - Update system-theme-associations example key
+ - Add DEP3 tag
+ - Refresh
+   * debian/source.lintian-overrides:
+ - Create file
+ - Override 2 missing-license-paragraph-in-dep5-copyright entries
+   * Tablet-mode: (LP: #1366421)
+ - Add detection based on acpid reporting the SW_TABLET_MODE switch
+ - Add detection based on hotkey events from XInput
+ - Add detection by reading tablet-mode state from a few known sysfs paths
+ - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
+ - Only run GlobalKeyListener when necessary
+ - Add tablet-mode settings to Preferences->Auto-show->Convertibles
+   * GNOME Shell:
+ - Add edge-drag gesture to show the keyboard in GNOME Shell
+ - Add option to gnome-shell-extension-prefs to disable edge-drag
+ - Enable auto-show only on first start (LP: #1650810)
+ - Fix setup.py to have distutils-extra not open extension dir as a file
+ - Stop the legacy icon panel from sliding in and out all the time
+ - Add license and copyright header to gschema.xml
+ - Fix broken string in prefs.js
+ - Fix copyright information in prefs.js
+ - Clean up prefs.js
+ - Remove debug output
+   * Auto-show:
+ - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
+ - Improve reliability in Unity Dash by reacting only to crucial events
+ - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
+ - Allow to block auto-show while external keyboards are connected
+ - Don't auto-hide while keys are still pressed.
+   * External keyboard detection:
+ - Detect keyboards with udev
+ - Add new preference subpage Preferences->Auto-show->External Keyboards
+ - Allow devices to be ignored; e.g. always connected keyboard
+   * onboard-autostart.desktop: (LP #1656779)
+ - Rename it to onboard-autostart.desktop.in
+ - Add _GenericName, _Comment and Icon keys
+ - Make it translatable
+   * Move listening for global key presses to new GlobalKeyListener.py file
+   * Have separate resize protection preference for floating icon and keyboard
+   * Add scale for label popup size to Preferences->Keyboard
+   * Switch position of "play sound" and "label popups" in Preferences-Keyboard
+   * Add MATE'S ContrastHighInverse to the map of known accessibility themes
+   * Replace deprecated GdkScreen.get_monitor_workarea()
+   * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
+   * Indicate in log when Onboard has been started from the project directory
+   * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
+   * Reorganize AtspiStateTracker for saner handling of multiple accessibles
+   * Update licensing tool for gnome shell extension
+   * Explicitely clean up Applndicator status icon on exit
+   * Improve error handling when opening layouts files
+   * Work around firefox 50 urlbar losing focus and giving wrong caret position
+   * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
+   * Work around byobu not reporting trailing spaces
+   * Fix -Wstrict-prototypes warning when building C++ extension lm
+   * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
+   * Fix geometry hints for minimum size calculation error on startup
+   * Fix startup failure on Arch Linux when libdbus-glib isn't installed
+   * Fix signed/unsigned comparison warnings when building in Arch Linux
+   * Make sure to hide label popups when the keyboard is hidden
+   * Ease adjustment of aspect ratio with more handles when docked and expanded
+   * Keep more distance when auto-positioning to the Dash search entry
+   * Enable docking by default in onboard-defaults.conf.example
+   * Update build instructions in README for Arch and Mageia
+   * Improve uninstall instructions in README
+ 
+ 
+ Could anybody please review the package for inclusion into the main
+ zesty repository.
+ 
+ Don't hesitate to contact us if you need further information:
+ https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.
+ 
+ Thanks in advance for your help.
+ 
+ Have a good day.
+ 
+ F

[Desktop-packages] [Bug 1664746] [NEW] Request for sponsorship for new upstream release (zesty deb provided)

[Francesco Fumanti]

Public bug reported:

Info to be added soon...

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

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  New

Bug description:
  Info to be added soon...

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

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

[Desktop-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

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

Thanks Sebastien for your input. You were probably right, as the unity-
settings-daemon startted under lightdm was also running in the desktop
session and version 1.20.0-0ubuntu3 that I just installed fixed the
issue.

** This bug has been marked a duplicate of bug 1637758
   lightdm greeter session not properly shut down at login

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.

  Here is the terminal output after entering the desktop session:

  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse

  As you can see, the mousetweaks process started under lightdm is still
  running. The second mousetweaks process in the terminal output was
  started by settings in the desktop session.

  This behaviour is new in zesty; in previous Ubuntu versions there was
  no mousetweaks process left running under lightdm after entering the
  desktop session.

  As Onboard has not been responsible until now for killing the
  mousetweaks process it started under lightdm, I am filing this bug
  against lightdm.

  On the other hand, one could argue that since it is Onboard that
  starts mousetweaks under lightdm, it is also Onboard's job to kill it
  when exiting lightdm. This is what we from the Onboard development
  team are wondering now.

  @ lightdm developers or maintainers

  Please let us know, what you think about Onboard being responsible to
  kill mousetweaks when switching when entering the desktop session.

  I don't know how difficult it will be to implement it, as Onboard
  cannot simply stop the hover click when it gets killed. In fact, in
  the desktop session, the hover click can be started independently from
  Onboard in the Pointing and Clicking tab from the Universal Access
  control panel in the System Settings.

  I am also subscribing the other members of the Onboard development
  team to this bug thread.

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

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

[Desktop-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

** Description changed:

  This problem occurs on the current development version of zesty; it does
  not occur on any other Ubuntu version that is currently supported.
  
  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.
  
  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the pointer
  stops moving. It is an accessibility feature for example for people that
  are not able to click with an hardware device, like mouse buttons.
  
  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.
  
  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.
  
  Here is the terminal output after entering the desktop session:
  
  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse
  
  As you can see, the mousetweaks process started under lightdm is still
- running and there is also a second mousetweaks process that was started
- because the desktop session is configured to automatically start the on-
- screen keyboard Onboard and Onboard is configured to start the hover
- click.
+ running. The second mousetweaks process in the terminal output was
+ started by settings in the desktop session.
  
  This behaviour is new in zesty; in previous Ubuntu versions there was no
  mousetweaks process left running under lightdm after entering the
  desktop session.
  
  As Onboard has not been responsible until now for killing the
  mousetweaks process it started under lightdm, I am filing this bug
  against lightdm.
  
  On the other hand, one could argue that since it is Onboard that starts
- mousetweaks, it is also Onboard's job to kill it when exiting lightdm.
- This is what we from the Onboard development team are wandering now.
+ mousetweaks under lightdm, it is also Onboard's job to kill it when
+ exiting lightdm. This is what we from the Onboard development team are
+ wondering now.
  
  @ lightdm developers or maintainers
  
+ Please let us know, what you think about Onboard being responsible to
+ kill mousetweaks when switching when entering the desktop session.
  
- Please let us know, what you think about it. 
+ I don't know how difficult it will be to implement it, as Onboard cannot
+ simply stop the hover click when it gets killed. In fact, in the desktop
+ session, the hover click can be started independently from Onboard in
+ the Pointing and Clicking tab from the Universal Access control panel in
+ the System Settings.
  
- I am also subscribing marmuta, the main Onboard developer who knows
- about me filing this bug, to this bug thread.
+ I am also subscribing the other members of the Onboard development team
+ to this bug thread.

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it 

[Desktop-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

** Description changed:

  This problem occurs on the current development version of zesty; it does
  not occur on any other Ubuntu version that is currently supported.
  
  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.
  
  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the pointer
  stops moving. It is an accessibility feature for example for people that
  are not able to click with an hardware device, like mouse buttons.
  
  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.
  
  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.
  
  Here is the terminal output after entering the desktop session:
  
  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse
  
  As you can see, the mousetweaks process started under lightdm is still
  running and there is also a second mousetweaks process that was started
  because the desktop session is configured to automatically start the on-
  screen keyboard Onboard and Onboard is configured to start the hover
  click.
  
  This behaviour is new in zesty; in previous Ubuntu versions there was no
  mousetweaks process left running under lightdm after entering the
- desktop session. Thus, I am filing this as a bug.
+ desktop session.
+ 
+ As Onboard has not been responsible until now for killing the
+ mousetweaks process it started under lightdm, I am filing this bug
+ against lightdm.
+ 
+ On the other hand, one could argue that since it is Onboard that starts
+ mousetweaks, it is also Onboard's job to kill it when exiting lightdm.
+ This is what we from the Onboard development team are wandering now.
+ 
+ @ lightdm developers or maintainers
+ 
+ 
+ Please let us know, what you think about it. 
+ 
+ I am also subscribing marmuta, the main Onboard developer who knows
+ about me filing this bug, to this bug thread.

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.

  Here is the terminal output after entering the desktop session:

  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse

  As you can see, the mousetweaks process started under lightdm is still
  running and there is also a second mousetweaks process that was
  started because the desktop session is configured to automatically
  start the on-screen keyboard Onboard and Onboard is configured to
  start the hover 

[Desktop-packages] [Bug 1643700] Re: mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

** Description changed:

  This problem occurs on the current development version of zesty; it does
  not occur on any other Ubuntu version that is currently supported.
  
  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.
  
  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the pointer
  stops moving. It is an accessibility feature for example for people that
  are not able to click with an hardware device, like mouse buttons.
  
- Here is how to start the hover click in lightdm: 
- - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right. 
- - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click. 
- - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature. 
+ Here is how to start the hover click in lightdm:
+ - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
+ - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
+ - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.
  
  The problem now is that the mousetweaks process started by Onboard in
- lightdm is still running after entering the desktop session. This was
- not the case in previous Ubuntu versions.
+ lightdm is still running after entering the desktop session.
+ 
+ Here is the terminal output after entering the desktop session:
+ 
+ $ ps -ef | grep mouse
+ lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
+ frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
+ frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse
+ 
+ As you can see, the mousetweaks process started under lightdm is still
+ running and there is also a second mousetweaks process that was started
+ because the desktop session is configured to automatically start the on-
+ screen keyboard Onboard and Onboard is configured to start the hover
+ click.
+ 
+ This behaviour is new in zesty; in previous Ubuntu versions there was no
+ mousetweaks process left running under lightdm after entering the
+ desktop session. Thus, I am filing this as a bug.

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm:
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right.
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click.
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature.

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session.

  Here is the terminal output after entering the desktop session:

  $ ps -ef | grep mouse
  lightdm   1784 1  0 22:30 ?00:00:00 mousetweaks
  frafu 3584  3546  1 22:31 ?00:00:00 mousetweaks
  frafu 4324  3105  0 22:31 pts/500:00:00 grep mouse

  As you can see, the mousetweaks process started under lightdm is still
  running and there is also a second mousetweaks process that was
  started because the desktop session is configured to automatically
  start 

[Desktop-packages] [Bug 1643700] [NEW] mousetweaks process does not get killed when entering desktop

[Francesco Fumanti]

Public bug reported:

This problem occurs on the current development version of zesty; it does
not occur on any other Ubuntu version that is currently supported.

Lightdm offers the possibility to start the default on-screen keyboard
Onboard. Further, Onboard offers the possibility to start the hover
click, which is provided by a process called mousetweaks.

The hover click consists in having the system automatically perform a
left click (and optionally other click types) shortly after the pointer
stops moving. It is an accessibility feature for example for people that
are not able to click with an hardware device, like mouse buttons.

Here is how to start the hover click in lightdm: 
- Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right. 
- Click on the key on the at the right of the Onboard layout that has a pointer 
as label; an additional column with keys will appear; these are the keys to 
control the hover click. 
- Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature. 

The problem now is that the mousetweaks process started by Onboard in
lightdm is still running after entering the desktop session. This was
not the case in previous Ubuntu versions.

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

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

Title:
  mousetweaks process does not get killed when entering desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem occurs on the current development version of zesty; it
  does not occur on any other Ubuntu version that is currently
  supported.

  Lightdm offers the possibility to start the default on-screen keyboard
  Onboard. Further, Onboard offers the possibility to start the hover
  click, which is provided by a process called mousetweaks.

  The hover click consists in having the system automatically perform a
  left click (and optionally other click types) shortly after the
  pointer stops moving. It is an accessibility feature for example for
  people that are not able to click with an hardware device, like mouse
  buttons.

  Here is how to start the hover click in lightdm: 
  - Start the on-screen keyboard Onboard by using the accessibility menu at the 
top right. 
  - Click on the key on the at the right of the Onboard layout that has a 
pointer as label; an additional column with keys will appear; these are the 
keys to control the hover click. 
  - Click on the key at the bottom of the column that just appeared and that 
shows a pointer with a little clock. This is the key to start the hover click. 
In fact, it starts the mousetweaks process, that provides the hover click 
feature. 

  The problem now is that the mousetweaks process started by Onboard in
  lightdm is still running after entering the desktop session. This was
  not the case in previous Ubuntu versions.

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

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

[Desktop-packages] [Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"

[Francesco Strappini]

Same here with Xubuntu 16.04 on RPi 3

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

Title:
  Chromium-browser armhf crashes with "InitializeSandbox() called with
  multiple threads in process gpu-process"

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  crashes on startup with

  [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() 
called with multiple threads in process gpu-process
  Segmentation fault

  System ODROID XU3 armhf

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

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

[Desktop-packages] [Bug 1619380] Re: onboard 1.3.0 Preferences dialog won't open

[Francesco Fumanti]

Thanks Jeremy for the piece of information and updating the bug status
accordingly.

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

Title:
  onboard 1.3.0 Preferences dialog won't open

Status in Onboard:
  Invalid
Status in onboard package in Ubuntu:
  Invalid

Bug description:
  onboard 1.3.0-0ubuntu1 on Ubuntu GNOME 16.10 Beta.

  1. Make sure onboard is not running.
  2. Open a terminal, then run onboard
  3. Click the menu button, then click the Preferences button.
  4. The Preferences dialog does not open. This is printed in the terminal:

  $ onboard

  (onboard:1301): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 
'window->update_and_descendants_freeze_count > 0' failed
  Traceback (most recent call last):
File "", line 1, in 
File "/home/jeremy/devel/temp/onboard/onboard-1.3.0/Onboard/settings.py", 
line 43, in 
  from Onboard.LayoutLoaderSVG import LayoutLoaderSVG
File 
"/home/jeremy/devel/temp/onboard/onboard-1.3.0/Onboard/LayoutLoaderSVG.py", 
line 46, in 
  from Onboard.WordSuggestions import WordListPanel
File 
"/home/jeremy/devel/temp/onboard/onboard-1.3.0/Onboard/WordSuggestions.py", 
line 35, in 
  import Onboard.pypredict as pypredict
File 
"/home/jeremy/devel/temp/onboard/onboard-1.3.0/Onboard/pypredict/__init__.py", 
line 25, in 
  from pypredict.lm_wrapper import *
File 
"/home/jeremy/devel/temp/onboard/onboard-1.3.0/Onboard/pypredict/__init__.py", 
line 25, in 
  from pypredict.lm_wrapper import *
File 
"/home/jeremy/devel/temp/onboard/onboard-1.3.0/Onboard/pypredict/lm_wrapper.py",
 line 28, in 
  from pypredict.lm import overlay, linint, loglinint  # exported symbols
  ImportError: cannot import name 'overlay'

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

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

[Desktop-packages] [Bug 1541900] Re: Latin

[Francesco Fumanti]

** Also affects: onboard
   Importance: Undecided
   Status: New

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

Title:
  Latin

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  There's no Non-Latin scripts Support. Ex: (Chinese(Bopomo, Cangjie),
  Japanese(あいうえお), Korean, etc.)

  Bopomo(ㄅㄆㄇ) keyboard:
  
http://a.bbkz.net/forum/attachment.php?attachmentid=163476=1=1=1263888015

  Cangjie (倉頡) keyboard http://www.linqi.org/cangjie/keybd.gif

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

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

[Desktop-packages] [Bug 1470611] Re: Onboard not fully registering initial touch events

[Francesco Fumanti]

** Also affects: onboard
   Importance: Undecided
   Status: New

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

Title:
  Onboard not fully registering initial touch events

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  With touch, onboard needs the first touch to get focus, then will give
  keypresses on subsequent touch events.

  Bug posted after response from Question:
  https://answers.launchpad.net/ubuntu/+source/onboard/+question/268716

  System Info:

  lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  uname -a
  Linux providius-voyager 3.16.7-ckt11-providius20150624 #1 SMP Wed Jun 24 
11:05:56 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
  * I am running the Debian kernel release as the Synaptics touchscreen doesn't 
work with any recent Ubuntu release.

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

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

[Desktop-packages] [Bug 1547417] Re: reset position of keyboard and icon

[Francesco Fumanti]

** Also affects: onboard
   Importance: Undecided
   Status: New

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

Title:
  reset position of keyboard and icon

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  Hello,

  I have connected external monitor as second display above primary.
  Primary monitor has touch screen. There are onboard keybord and icon
  on primary display. After unplugging second monitor onboard keyboard
  and icon doesn't show on primary display.

  Linux Mint XFCE 17.3 Rosa
  Onboard 1.0.1-0ubuntu1

  thanks
  Tomas

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

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

[Desktop-packages] [Bug 1546646] Re: Disable Auto Show when bluethooth keyboard is connected.

[Francesco Fumanti]

** Also affects: onboard
   Importance: Undecided
   Status: New

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

Title:
  Disable Auto Show when bluethooth keyboard is connected.

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  Hi,

  I like the auto show feature, but it wont get disabled when a
  bluetooth keyboard is connected to the device.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: onboard 1.1.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 17 17:56:00 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-13 (522 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1580666] Re: Failed keyboard configuration on reboot

[Francesco Fumanti]

** Also affects: onboard
   Importance: Undecided
   Status: New

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

Title:
  Failed keyboard configuration on reboot

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  I have a laptop ACER Aspire E15 E5-571G-337K with French keyboard

  After each reboot, i have to run the following command to have
  corrects specials characters :

  sudo dpkg-reconfigure keyboard-configuration

  then the keyboard is correct for all the sessions but unfortunately
  after a reboot I have the old broken keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: onboard 1.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 11 17:41:53 2016
  InstallationDate: Installed on 2015-08-27 (257 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: onboard
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (0 days ago)

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

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