date:20200828

[Expired for evolution-data-server (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: evolution-data-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  evolution public certificate lookups in ldap fail

Status in evolution-data-server package in Ubuntu:
  Expired

Bug description:
  Looking up user's public certificates in AD/LDAP fail while looking up
  with regular ldapsearch works without any issues.

  ldapsearch -LLL -b DC=company,DC=com -H ldap://ADDC.company.com -Q -N 
'(cn=username)' userCertificate -z 10 -o ldif-wrap=no
  dn: CN=username,OU=CA,OU=User,OU=OU1,OU=ID,OU=OU2,DC=company,DC=com
  userCertificate:: MII...truncated

  Evolution can't look up these certificates and evolution's address
  book processes hang even crash evolution.

  The same configuration work both with ldapsearch and in thunderbird,
  but thunderbird is not an alternative in this case.

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

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

[Desktop-packages] [Bug 1882023] Re: Notifications are pointlessly truncated even on ultrawide monitors

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

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

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

Title:
  Notifications are pointlessly truncated even on ultrawide monitors

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I tried to use ubuntu-bug -w to identify the component for this bug by
  clicking on a notification, but it failed with "xprop failed to
  determine process ID of the window". Sorry.

  The bug is that notifications of adding/removing icons to Favorites in
  the taskbar, are truncated for no good reason. I have a dual monitor
  setup ridiculous amounts of horizontal space, yet the notification is
  fixed size - which is fine, if it wrapped the text inside it. But it
  doesn't.

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

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

[Desktop-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

This bug was fixed in the package jack-mixer - 13-0ubuntu2

---
jack-mixer (13-0ubuntu2) groovy; urgency=medium

  * d/control: Remove gir1.2-gconf-2.0 dependency (LP: #1771041)

 -- Erich Eickmeyer   Wed, 19 Aug 2020 09:14:49
-0700

** Changed in: jack-mixer (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  Fix Released
Status in jack-mixer package in Ubuntu:
  Fix Released
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Confirmed

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

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

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

[Desktop-packages] [Bug 1881654] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: tex-common (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Expired

Bug description:
  See message sent automatically by system.  I am not a SW developer.I
  try installinbg updates and this non-informative message appears
  saying there is a preoblem - duh.  Typical kids who can't communicate
  specifics.  VEDRY annoying.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic i686
  ApportVersion: 2.20.1-0ubuntu2.23
  AptOrdering:
   ca-certificates: Install
   tex-common: Configure
   ca-certificates: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Mon Jun  1 12:54:56 2020
  DpkgHistoryLog:
   Start-Date: 2020-06-01  12:54:35
   Commandline: aptdaemon role='role-commit-packages' sender=':1.74'
   Upgrade: ca-certificates:i386 (20170717~16.04.2, 20190110~16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-06-07 (2551 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32ubuntu0.1
  SourcePackage: tex-common
  Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2020-04-30 (32 days ago)

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

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

[Desktop-packages] [Bug 1885552] Re: gnome shell crashes if screen is locked

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

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

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

Title:
  gnome shell crashes if screen is locked

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  1) Description:   Ubuntu 18.04.4 LTS
  Release:  18.04

  2) gnome-shell:
Installé : 3.28.4-0ubuntu18.04.3
Candidat : 3.28.4-0ubuntu18.04.3
   Table de version :
   *** 3.28.4-0ubuntu18.04.3 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.3+git20190124-0ubuntu18.04.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) I want to lock the screen (SUPER+L)
  4) Gnome Shell crashes and restart

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 13:25:29 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-08 (752 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/zsh
  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/1885552/+subscriptions

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

[Desktop-packages] [Bug 1892973] Re: gnome-session fails, and fails, and fails yet again

2020-08-28 Thread ebsf

Some additional information:

When the boot sequence is
- GRUB boot to recovery mode
- Drop to root prompt
- Remove a driver and install a driver
- Exit root prompt (Ctrl-D)
- Resume normal boot as per the recovery mode menu

Then the display comes up at a degraded resolution (1024x768) but no
gnome-session hang occurs in response to some of the reliable triggers
(typically, attempting to launch Firefox, Google Chrome, or navigate
gnome-settings).

Booting normally (via restart or hard-reset) brings up the display at
maximum resolution and gnome-session hangs immediately on one of the
reliable triggers.

I noted this previously.

To test whether resolution is the issue, I booted normally.  gnome-settings 
hangs gnome-session, so instead, I ran
```xrandr -s 1024x768```
which was immediately effective.  I then accessed gnome-settings and it 
triggered another gnome-session hang.

The conclusion is that degraded screen resolution itself does not
prevent gnome-session hangs.

Reviewing /var/log/syslog and the systemd journal, as well as
/var/log/Xorg.0.log reveals that gdm3 recognizes the monitor by
manufacturer and model and correctly picks up its configuration
capabilities when the system boots normally.  This does not occur,
however, when one boots first to recovery mode, changes drivers, and
resumes normal boot.

To test whether a recovery mode session alone prevented a gnome-session
hang, I then booted to recovery mode, did NOT change drivers, then
resumed normal boot.  Interestingly, the display came up in high
resolution notwithstanding the prior xrandr reconfiguration.
/var/log/Xorg.0.log reflected that gdm3 did identify the monitor.  And,
most importantly, the reliable triggers immediately caused a gnome-
session hang.

The conclusion, then, is that a recovery mode session alone does not
prevent a gnome-session hang.  One must change the driver during that
recovery mode session, to prevent it (albeit at the cost of degraded
screen resolution).

To test whether simply removing and installing the same driver during a
recovery mode session would be sufficient to avoid a gnome-session hang,
I experimented with that.  On resuming normal boot, the screen came up
at full resolution and the usual triggers produced a gnome-session hang.

The conclusion, then, is that a change of drivers is necessary during a
recovery mode session to prevent a gnome-session hang after resuming
normal boot from recovery mode.  Again, this is at the cost of degraded
screen resolution, and the protection will not persist through a normal
boot.

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

Title:
  gnome-session fails, and fails, and fails yet again

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia-
  driver-440.  Both drivers expressly support the hardware.  All
  varieties of desktop environment (Xorg, Gnome Classic, Ubuntu)

  
  Bug summary

  Screen hangs randomly and iretrievably with the only possibility of recovery 
being a a hard system reset.  Sometimes this is triggered by activity 
(launching or using gnome-settings; resizing a window; using Nautilus), 
sometimes, not.  No session lasts more than five minutes.
  No combination of keystrokes will yield a terminal of any kind.
  The hang also interrupts System Monitor output, so no information regarding 
use of system resources is available.

  
  Steps to reproduce

  1.  Install gnome-session.
  2.  Reboot.
  3.  Use graphical applications.

  
  What happened]

  The screen froze irretrievably.

  Screen hangs randomly and iretrievably with the only possibility of
  recovery being a a hard system reset.  Sometimes this is triggered by
  activity (launching or using gnome-settings; resizing a window; using
  Nautilus), sometimes, not.  No session lasts more than five minutes.

  No combination of keystrokes will yield a terminal of any kind.

  The hang also interrupts System Monitor output, so no information
  regarding use of system resources is available.

  A hard system reset and consequent reboot yields a variety of
  outcomes.  Sometimes, a normal gdm login.  Sometimes, a black screen
  with an inverted-black mouse cursor/pointer/arrow that moves.
  Sometimes an entirely black screen.  Sometimes, not even a hard system
  reset is sufficient and the system has to be booted into recovery
  mode, the existing driver removed, and another installed, before
  rebooting again.

  With nvidia-driver-440, fewer hangs but the monitor resolution can't be set 
to its capacity.
  I don't get it.  GNOME hangs have been extensively documented for ten years.  
The drivers expressly support the hardware.  This package is part of an Ubuntu 
LTS release.  Is gnome-session intended to be serious, functional, production 
software subjected to rigorous and competent

[Desktop-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-08-28 Thread Chris Guiver

Ubuntu groovy daily (2020-08-28) QA-test on initial reporting box

dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

It booted to no wallpaper

On changing wallpaper, the images are corrupted, block-low-signal tv
type blocky/corrupted images.

On occasion the selection of an image will be drawn as background
perfectly, but select another (corrupted), return to the one that was
perfect before and now it'll be corrupted. Corruption isn't consistent,
at times it's minor, other times the images is unrecognizable.

The images in the background window (where you select another image) are
drawn perfectly...


** Tags added: groovy

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor

2020-08-28 Thread Rocko

@Daniel: That current mode is from the xrandr.txt when the working
2560x1440 resolution is set. Lionel and I got the 23.98 Hz figure from
monitors.xml that I generated after the 1920x1080 change is applied and
the monitor has no signal. With the monitor receiving no signal in
1920x1080, the verbose xrandr shows:

  1920x1080 (0xc6) 74.176MHz +HSync +VSync *current
h: width  1920 start 2558 end 2602 total 2750 skew0 clock  26.97KHz
v: height 1080 start 1084 end 1089 total 1125   clock  23.98Hz

So g-c-c is definitely choosing the lowest refresh rate, whereas if I
use xrandr's --mode option to set 1920x1080, it choose the 60 Hz rate,
which works.

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

Title:
  gnome-control-center cannot change resolution of external monitor

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

Bug description:
  g-c-c is unable to change the resolution on my external 2560x1440
  monitor to 1920x1080 - when I try, the monitor turns off.

  However, the command "xrandr --output HDMI-1 --mode 1920x1080" does
  successfully change the resolution.

  xrandr for the monitor shows:

  HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1920x1080i60.0050.0059.94  
 1600x1200 60.00  
 1280x1024 75.0260.02  
 1280x960  60.00  
 1360x768  60.02  
 1280x720  60.0050.0059.94  
 1024x768  75.0370.0760.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x576i  50.00  
 720x480   60.0059.94  
 720x480i  60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  

  I tried changing the resolution to 1600x1200 using g-c-c and this did
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  Uname: Linux 5.8.1-050801-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 11:28:08 2020
  InstallationDate: Installed on 2019-07-01 (415 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago)

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

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

[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound

2020-08-28 Thread Tim Richardson

My sound control panel reports three speech-dispatcher entries in Volume
Levels. I don't know why.

My session is about two days old and I haven't had any instance of
distortion, so the workaround referred to in my previous comment, a
config change, may be a good idea for package maintainers to implement.

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

Title:
  speech-dispatcher distorts all sound

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel

  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use
  the site after a while. When I close down Firefox the problem still
  lingers a bit, but maybe not as long. One thing I did which seemed
  faster was close down everything, then load what I wanted to listen to
  (Skype, Discord), and if it still persisted I would go into "Sound
  Settings" and after a few blinks in that window the sound is normal
  again.

  While the site is open, according to "Sound Settings" (from the
  speaker icon menu) and Pulse Audio Volume Controller (pavu) there are
  4 copies of this package. Muting them did not help the problem, but
  moving one of them, and a very specific one, from the "Built-in Audio
  Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be
  a workaround.

  Just so you know, I do not use the HDMI cable for sound, but instead
  use the "headphones" jack. If you need any more details, I'll try to
  provide them.

  /Edward

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

-- 
Mailing list: https://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 1131664] Re: The default apps should have standard menubars under Unity

2020-08-28 Thread bluedxca93

Xfce and Mate are great Desktops also on ubuntu. If i had the money i would
support both desktops with donations.

As long as xubuntu and ubuntu-mate exists , Canoncial is still producing
usable  fast and stable wonderful gtk based  Systems. Just to mention the
positive side of things.

The focus of the main ubuntu desktop is far away from the traditional
menubar design. Advanced functions are hidden  or are entirely removed.
Based on these facts i see only for most users  the possibility to either
install a different ubuntu flavor or to switch to debian.

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

Title:
  The default apps should have standard menubars under Unity

Status in Ayatana Design:
  Fix Released
Status in File Roller:
  New
Status in gThumb:
  New
Status in Rhythmbox:
  Expired
Status in evince package in Ubuntu:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-mines package in Ubuntu:
  Won't Fix
Status in gnote package in Ubuntu:
  Fix Released
Status in gthumb package in Ubuntu:
  Won't Fix
Status in nautilus package in Ubuntu:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  When fixing this bug, also take a look at bug #1130722 at the same
  time if possible.

  
--

  In Raring, the  'Calculator' app should have the following menu items:

  === Edit ===

  Copy
  Paste
  -
  Undo
  Redo
  -
  Preferences
  -
  Quit

  === Mode ===

  Basic
  Advanced
  Financial
  Programming

  === Help ===

  Contents
  About

  


  In Raring, the  'System Settings' app should have the following menu
  items:

  === Help ===

  Contents
  [Optional link to help doc for the currently selected settings panel]
  -
  Quit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1131664/+subscriptions

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

[Desktop-packages] [Bug 1131664] Re: The default apps should have standard menubars under Unity

2020-08-28 Thread vexorian

And thus Gnome's poor UX design is dragging everyone else with them.

Maybe Gnome developers and Canonical can live in a pretend world where a
Hamburger menu is a remotely-acceptable UX in A DESKTOP OS, but for
those of us who use Ubuntu professionally this design is just not
practical.


I'm retiring my yearly Canonical donation, dropping Unity in favor of Gnome  
should have been a enough of a signal that Canonical no longer have an interest 
in actually improving the Desktop experience. Instead it looks like the 
donations are going towards advertising cloud solution and it looks like 
Canonical devs are too busy defending the WSL in twitter to be able to make 
these sort of improvements.

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

Title:
  The default apps should have standard menubars under Unity

Status in Ayatana Design:
  Fix Released
Status in File Roller:
  New
Status in gThumb:
  New
Status in Rhythmbox:
  Expired
Status in evince package in Ubuntu:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-mines package in Ubuntu:
  Won't Fix
Status in gnote package in Ubuntu:
  Fix Released
Status in gthumb package in Ubuntu:
  Won't Fix
Status in nautilus package in Ubuntu:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  When fixing this bug, also take a look at bug #1130722 at the same
  time if possible.

  
--

  In Raring, the  'Calculator' app should have the following menu items:

  === Edit ===

  Copy
  Paste
  -
  Undo
  Redo
  -
  Preferences
  -
  Quit

  === Mode ===

  Basic
  Advanced
  Financial
  Programming

  === Help ===

  Contents
  About

  


  In Raring, the  'System Settings' app should have the following menu
  items:

  === Help ===

  Contents
  [Optional link to help doc for the currently selected settings panel]
  -
  Quit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1131664/+subscriptions

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

[Desktop-packages] [Bug 1893484] [NEW] Google Chrome 85.0.4183.83 crahses with SIGSEGV

2020-08-28 Thread alex-mobigo

Public bug reported:

After an Update, the new version Google Chrome 85.0.4183.83  crashes
with SIGSEGV.


1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
ii  google-chrome-stable   85.0.4183.83-1   
amd64The web browser from Google

3) What you expected to happen
Load the initial page or load my themes and configurations

4) What happened instead
It show the initial page, ask for Restore pages? when clicked it freezes for a 
moment and then a crash with:
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
+++ killed by SIGSEGV (core dumped) +++


Previous version was working fine.

I de-installed, removed all configurations and themes and tried again.
Same issue.

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

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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

[Desktop-packages] [Bug 1893478] Re: Wireless mouse not working

2020-08-28 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Wireless mouse not working

Status in gdm3 package in Ubuntu:
  New

Bug description:
  This might be link to gdm3
  Running Ubuntu 20.04.1
  Wireless mouse stop working after fresh install of Ubuntu 20.04 and after 
upgrade to 20.04 on another computer.

  The usb dongle is detected according to lsusb
  Bus 001 Device 023: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse

  When booting if I select recovery mode and then choose resume,
  everything works fine for this session, but as soon as I reboot then
  mouse stop working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 15:30:34 2020
  InstallationDate: Installed on 2020-05-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2020-08-28T11:40:26.503109

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

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

[Desktop-packages] [Bug 1893478] [NEW] Wireless mouse not working

You have been subscribed to a public bug:

This might be link to gdm3
Running Ubuntu 20.04.1
Wireless mouse stop working after fresh install of Ubuntu 20.04 and after 
upgrade to 20.04 on another computer.

The usb dongle is detected according to lsusb
Bus 001 Device 023: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse

When booting if I select recovery mode and then choose resume,
everything works fine for this session, but as soon as I reboot then
mouse stop working again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 28 15:30:34 2020
InstallationDate: Installed on 2020-05-15 (105 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2020-08-28T11:40:26.503109

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


** Tags: amd64 apport-bug focal
-- 
Wireless mouse not working
https://bugs.launchpad.net/bugs/1893478
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 in Ubuntu.

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

[Desktop-packages] [Bug 1893065] Re: Gnome applications launching very slow due to gphoto2 services

2020-08-28 Thread Bug Watch Updater

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

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

Title:
  Gnome applications launching very slow due to gphoto2 services

Status in gPhoto2:
  New
Status in libgphoto2 package in Ubuntu:
  New

Bug description:
  Any time, into a fresh session or after any time of work, when I try
  to open any Gnome Application, including Nautilus, the app delay a lot
  of seconds (like 10 or more) to launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 26 12:01:03 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'Humanity'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2020-08-04 (21 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893470] Re: Cheese doesn't show image or video

2020-08-28 Thread Daniel Letzeisen

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

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

Title:
  Cheese doesn't show image or video

Status in cheese package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.7

  My webcam is connected to a USB port. Image/video in Cheese disappears
  within a fraction of a second.

  But GTK UVC works well without changing that port. Changed the USB
  port for Cheese.  Reinstalled and tried.  But in vain.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cheese 3.18.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230
  Uname: Linux 4.4.0-187-generic i686
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Aug 28 23:13:38 2020
  InstallationDate: Installed on 2018-05-07 (844 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   cheese3.18.1-2ubuntu3
   cheese-common 3.18.1-2ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PE94510M.86A.0050.2007.0710.1559
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D945GCPE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD97209-201
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1893468] Re: Cheese doesn't show image or video

2020-08-28 Thread Daniel Letzeisen

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

** This bug has been marked a duplicate of bug 1893470
   Cheese doesn't show image or video

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

Title:
  Cheese doesn't show image or video

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Cheese image/video disappears within a fraction of a second. Ubuntu
  16.04.7. But GTK UVC works well.

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

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

[Desktop-packages] [Bug 1892973] Re: gnome-session fails, and fails, and fails yet again

2020-08-28 Thread ebsf

Thanks for responding.

Some delays in responding because of client demands, then because the
storage configuration of the machine was incomplete and the debug files
couldn't be networked, then because the incessant gnome-session hangs
required a hard-reset at nearly every step along the way.

The delays provided some information, however.

First, I booted to recovery mode, removed nvidia-driver-440, installed
nvidia-driver-450 (the recommended one, per the ubuntu-drivers devices
output), exited recovery, and continued the boot (NOT another hard-
reset). Here, the resolution was 1024x768, not the full resolution of
the monitor, in logging in under all available desktop managers (Xorg,
Classic, and Ubuntu). The machine experienced NO gnome session freezes
over 8-10 hours with occasional interaction in between client calls.
THEN, I did a normal reboot at the end of the day, specified Xorg on
login. The resolution now was back to normal but I immediately right-
clicked to launch display settings and this triggered a gnome-session
freeze. Through a series of hard-resets, the machine continued several
other random freezes.

Today, I had reconfigured storage to, among other things, mount /tmp to
/tmpfs, the consequence of which obviously is to flush /tmp on every
reboot. The machine experienced no gnome-session hangs. I then ran apt
update and apt full-upgrade, which triggered updates of what appeared to
be nvidia-driver-450 and all of its dependencies. The machine then
promptly experienced a gnome-session hang.

Hard-reset, black screen.

Hard-reset, Xorg login, generate the debug files (attached). Run
apport-collect 1892973. Launching Firefox to authorize triggers a
gnome-session hang.

Hard-reset, Xorg login. Launching Firefox triggers a gnome-session
hang.

Hard-reset, Xorg login. Copy debug files to this machine (a functional
Windows laptop) and make this entry.

The requested debug files, to the extent of the machine's ability to generate
them, are attached. I ended up generating several prior-boot journal logs for
all of the foregoing gnome-session hangs, and attach them in a ZIP archive
because the interface will only let me attach one file. The files include:
- prevboot-1 (first prevboot)
- prevboot-2 (the boot preceeding prevboot-1)
- prevboot-1128-* (boots involving Firefox-induced hangs and one preceding)
- prevboot-1135-1 (boot involving a Firefox-induced hang).

Obviously, the machine is incapable of authorizing for apport-collect.
I should add that attempting to launch Google Chrome also triggers a
gnome-session hang.

No files exist in /var/crash.

** Attachment added: "Zip archive of debug files"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+attachment/5405535/+files/documents.zip

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

Title:
gnome-session fails, and fails, and fails yet again

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia-
driver-440. Both drivers expressly support the hardware. All
varieties of desktop environment (Xorg, Gnome Classic, Ubuntu)

Bug summary

Screen hangs randomly and iretrievably with the only possibility of recovery
being a a hard system reset. Sometimes this is triggered by activity
(launching or using gnome-settings; resizing a window; using Nautilus),
sometimes, not. No session lasts more than five minutes.
No combination of keystrokes will yield a terminal of any kind.
The hang also interrupts System Monitor output, so no information regarding
use of system resources is available.

Steps to reproduce

1. Install gnome-session.
2. Reboot.
3. Use graphical applications.

What happened]

The screen froze irretrievably.

No combination of keystrokes will yield a terminal of any kind.

The hang also interrupts System Monitor output, so no information
regarding use of system resources is available.

A hard system reset and consequent reboot yields a variety of
outcomes. Sometimes, a normal gdm login. Sometimes, a black screen
with an inverted-black mouse cursor/pointer/arrow that moves.
Sometimes an entirely black screen. Sometimes, not even a hard system
reset is sufficient and the system has to be booted into recovery
mode, the existing driver removed, and another installed, before
rebooting again.

With nvidia-driver-440, fewer hangs but the monitor resolution can't be set
to its capacity.
I don't get it. GNOME hangs have been extensively documented for ten

[Desktop-packages] [Bug 1893476] [NEW] Broken colors using RDP with Windows 10

2020-08-28 Thread DooMMasteR

Public bug reported:

When I connect to my desktop PC via remmina all colors a broken.
Using MS RD Client on Android gives me no issues at all.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: remmina 1.4.2+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Aug 28 21:00:54 2020
ExecutablePath: /usr/bin/remmina
InstallationDate: Installed on 2018-05-02 (849 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: remmina
UpgradeStatus: Upgraded to focal on 2020-02-24 (185 days ago)

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


** Tags: amd64 apport-bug focal wayland-session

** Attachment added: "screenshot of the issue."
   
https://bugs.launchpad.net/bugs/1893476/+attachment/5405529/+files/Screenshot%20from%202020-08-28%2021-04-26.png

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

Title:
  Broken colors using RDP with Windows 10

Status in remmina package in Ubuntu:
  New

Bug description:
  When I connect to my desktop PC via remmina all colors a broken.
  Using MS RD Client on Android gives me no issues at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.4.2+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Aug 28 21:00:54 2020
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2018-05-02 (849 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: remmina
  UpgradeStatus: Upgraded to focal on 2020-02-24 (185 days ago)

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

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

[Desktop-packages] [Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-28 Thread satmandu

@vorlon it is in the graphic which shows up in the GUI surrounding the checkbox 
to enable -proposed
here: 
https://wiki.ubuntu.com/Testing/EnableProposed?action=AttachFile=get=devoptions_1604.png


Thank you @knox for the clarification. This was largely my fault for doing a 
's/focal/groovy/g' in my sources.list.

I can't speak to whether the GUI source selection interface allows one
to add -proposed to the primary sources.list when the devel series is
running though.

Is there a way to tell apt that packages which have a dependency upon
libffi7 should absolutely not be mixed with packages which depend upon
libffi8 because there is a breaking change? (I imagine there is no
automated way to notice that hey data structures have changed between
library versions.)

And for the benefit of users in the future who accidentally hit this
sort of issue, can anyone recommend a best practices way to downgrade
all packages which are for instance built against libffi8ubuntu1?

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

Title:
  gnome-shell crashing (libffi8ubuntu1 upgrade issue)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libffi package in Ubuntu:
  Incomplete

Bug description:
  Seeing this on groovy installs after an update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.4-1ubuntu2~build1
  Uname: Linux 5.8.3-050803-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Aug 25 15:49:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (311 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2
  ShellJournal:
   -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 
EDT. --
   -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087

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

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

[Desktop-packages] [Bug 1893468] [NEW] Cheese doesn't show image or video

2020-08-28 Thread MadhuSoodanan

Public bug reported:

Cheese image/video disappears within a fraction of a second. Ubuntu
16.04.7. But GTK UVC works well.

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

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

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

Title:
  Cheese doesn't show image or video

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Cheese image/video disappears within a fraction of a second. Ubuntu
  16.04.7. But GTK UVC works well.

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

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

[Desktop-packages] [Bug 1893469] [NEW] Missing pdfnup and other scripts

2020-08-28 Thread Roberto Lionello

Public bug reported:

texlive-extra package is supposed to provide several scripts in
/usr/share/texlive/texmf-dist/scripts/pdfjam/, including pdfnup,
pdfnpun, pdfbook, etc. However, the only script present is pdfjam.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: texlive-extra-utils 2019.202000218-1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Aug 28 10:31:12 2020
InstallationDate: Installed on 2020-08-04 (23 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
PackageArchitecture: all
SourcePackage: texlive-extra
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal uec-images

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

Title:
  Missing pdfnup and other scripts

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  texlive-extra package is supposed to provide several scripts in
  /usr/share/texlive/texmf-dist/scripts/pdfjam/, including pdfnup,
  pdfnpun, pdfbook, etc. However, the only script present is pdfjam.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: texlive-extra-utils 2019.202000218-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Aug 28 10:31:12 2020
  InstallationDate: Installed on 2020-08-04 (23 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  PackageArchitecture: all
  SourcePackage: texlive-extra
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium

Ok, so the issue with the launcher is that your favourite for Chromium
is 'chromium-browser.desktop', whereas it should be
'chromium_chromium.desktop'.

If you have the chromium-browser deb package installed, running /usr/bin
/chromium-browser (just once) should translate the desktop file name. If
not, you can modify its value by hand with this command:

gsettings set org.gnome.shell favorite-apps "['thunderbird.desktop',
'libreoffice-writer.desktop', 'libreoffice-calc.desktop',
'org.gnome.Nautilus.desktop', 'chromium_chromium.desktop',
'org.gnome.Screenshot.desktop', 'org.gnome.Calculator.desktop']"

Please let us know if that fixes the problem for you.

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

Title:
  [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking
  for chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Deleting the ~/snaps folder in ubuntu seems to permanently break gnome
  dash window tracking.

  Steps to reproduce:

  1) Add chromium-browser.desktop to your dash / dock favourites.
  Chromium Windows get attributed to this favourite when created.

  2) Delete the ~/snaps folder, quit all chromium processes and / or
  reboot

  3) The ~/snaps folder gets recreated, but Chromium windows now get
  attributed to a new chromium-browser dash icon, ignoring the favourite
  created in step 1

  I know I know, don't delete the ~/snaps folder then!

  Unfortunately, there are situations when this is beyond my control.
  These desktops are gonna get into the hands of normal users, like my dad and 
my colleagues.
  They will delete the folder by accident or because they don't know and don't 
care about snaps.
  Deleting it shouldn't permanently break window tracking.

  This is on a fully patched 20.04 system.

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)

2020-08-28 Thread Bug Watch Updater

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1661715.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-08-28T14:37:12+00:00 Olivier Tilloy wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/85.0.4183.83 Safari/537.36

Steps to reproduce:

Downstream (Ubuntu) bug report:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893021

With the release of firefox 80.0, loading the flash plugin on Ubuntu
16.04 was failing with the following error:

/usr/lib/firefox/plugin-container: symbol lookup error:
/usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar


Actual results:

In previous releases, loading the flash plugin worked fine.


Expected results:

This regression was caused by two recent revisions:
https://phabricator.services.mozilla.com/D84623 and
https://phabricator.services.mozilla.com/D82804, which added GTK
function stubs (in widget/gtk/mozgtk/mozgtk.c in the wrong section (they
were added to the COMMON_SYMBOLS section but they should be in the
GTK3_SYMBOLS because they are GTK3 only).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893021/comments/3


On 2020-08-28T14:47:39+00:00 Olivier Tilloy wrote:

Created attachment 9172666
Bug 1661715 - Move GTK function stubs to the correct section.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893021/comments/5


On 2020-08-28T15:17:47+00:00 Release-mgmt-account-bot wrote:

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893021/comments/8


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

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

Title:
  Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
  (gtk_window_set_titlebar)

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When testing firefox 80.0+build2 on xenial (from https://launchpad.net
  /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm
  observing that the flash plugin (installed by flashplugin-installer)
  doesn't work. This appears to affect only xenial, flash is working in
  the bionic and focal builds.

  This is what I'm seeing when launching firefox from a terminal:

/usr/lib/firefox/plugin-container: symbol lookup error:
  /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar

  This is most likely caused by this recent upstream change:
  https://phabricator.services.mozilla.com/D84623

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

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

[Desktop-packages] [Bug 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium

> Interestingly, the new Chromium window now displays a "file not found"
> error for file:///snap/chromium/1275/firstrun/snap-en.html when launched.

Oh, good catch, this is an (unrelated) regression, fixed with
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/commit/?id=0959d5f44d9ce6dbcac4b89228e7014e9b07e95f.

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

Title:
  [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking
  for chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Deleting the ~/snaps folder in ubuntu seems to permanently break gnome
  dash window tracking.

  Steps to reproduce:

  1) Add chromium-browser.desktop to your dash / dock favourites.
  Chromium Windows get attributed to this favourite when created.

  2) Delete the ~/snaps folder, quit all chromium processes and / or
  reboot

  3) The ~/snaps folder gets recreated, but Chromium windows now get
  attributed to a new chromium-browser dash icon, ignoring the favourite
  created in step 1

  I know I know, don't delete the ~/snaps folder then!

  Unfortunately, there are situations when this is beyond my control.
  These desktops are gonna get into the hands of normal users, like my dad and 
my colleagues.
  They will delete the folder by accident or because they don't know and don't 
care about snaps.
  Deleting it shouldn't permanently break window tracking.

  This is on a fully patched 20.04 system.

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

-- 
Mailing list: https://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 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-28 Thread Steve Langasek

On Fri, Aug 28, 2020 at 03:01:13PM -, Dimitri John Ledkov wrote:
> I'm not sure how we can update that testing page to be more informative.

I don't find that cited text on this wiki page at all.

I *do* find that the page advises to enable "selective upgrading from
-proposed", which would have avoided this particular problem.

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

Title:
  gnome-shell crashing (libffi8ubuntu1 upgrade issue)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libffi package in Ubuntu:
  Incomplete

Bug description:
  Seeing this on groovy installs after an update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.4-1ubuntu2~build1
  Uname: Linux 5.8.3-050803-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Aug 25 15:49:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (311 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2
  ShellJournal:
   -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 
EDT. --
   -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087

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

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

[Desktop-packages] [Bug 1879742] Re: When using Google Meet on Firefox, delay sending sound from microphone

2020-08-28 Thread Mike Guterl

I am still having this issue on MacOS with Firefox 80. Is there anything
that I can do to help diagnose the issue?

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879742] Re: When using Google Meet on Firefox, delay sending sound from microphone

2020-08-28 Thread Mike Guterl

I am still having this issue on MacOS with Firefox 80. Is there anything
that I can do to help diagnose the issue?

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1893449] [NEW] libbluray-bdj crashes on 20.04

2020-08-28 Thread Sean

Public bug reported:

libluray/libbluray-bdj crashes on 20.04 when playing certain blurays.
Issue does not happen on 18.04.

Description:Ubuntu 20.04.1 LTS
Release:20.04

libbluray-bdj:
  Installed: 1:1.2.0-1
  Candidate: 1:1.2.0-1
  Version table:
 *** 1:1.2.0-1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status


libbluray-bdj_1.0.2-3 from 18.04 plays the blurays correctly.


Jave error in log when using libbluray from 20.04:

Exception in thread "main"
PrintStream.java:java.io.PrintStream.println:823:
java.lang.NoClassDefFoundError: org/objectweb/asm/commons/SimpleRemapper

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.BDJClassFileTransformer.rename(BDJClassFileTransformer.java:64)

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.mmbd.Adapter.(Adapter.java:83)

PrintStream.java:java.io.PrintStream.println:823:   at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

PrintStream.java:java.io.PrintStream.println:823:   at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

PrintStream.java:java.io.PrintStream.println:823:   at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

PrintStream.java:java.io.PrintStream.println:823:   at
java.lang.reflect.Constructor.newInstance(Constructor.java:423)

PrintStream.java:java.io.PrintStream.println:823:   at
java.lang.Class.newInstance(Class.java:442)

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.Libbluray.loadAdapter(Libbluray.java:99)

PrintStream.java:java.io.PrintStream.println:823:   at
org.videolan.Libbluray.init(Libbluray.java:354)

bdj.c:737: Failed to initialize BD-J (uncaught exception)
GUIManager:0: ERROR: getInstance(): no instance !
bluray.c:3202: Can't play BD-J title 1
[7f81ec0062c0] libbluray demux error: bluray: stopping playback after fatal 
error

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

** Attachment added: "VLC error log"
   
https://bugs.launchpad.net/bugs/1893449/+attachment/5405477/+files/libbluray%20error%20log

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

Title:
  libbluray-bdj crashes on 20.04

Status in libbluray package in Ubuntu:
  New

Bug description:
  libluray/libbluray-bdj crashes on 20.04 when playing certain blurays.
  Issue does not happen on 18.04.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  libbluray-bdj:
Installed: 1:1.2.0-1
Candidate: 1:1.2.0-1
Version table:
   *** 1:1.2.0-1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

  
  libbluray-bdj_1.0.2-3 from 18.04 plays the blurays correctly.

  
  Jave error in log when using libbluray from 20.04:

  Exception in thread "main"
  PrintStream.java:java.io.PrintStream.println:823:
  java.lang.NoClassDefFoundError:
  org/objectweb/asm/commons/SimpleRemapper

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.BDJClassFileTransformer.rename(BDJClassFileTransformer.java:64)

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.mmbd.Adapter.(Adapter.java:83)

  PrintStream.java:java.io.PrintStream.println:823:   at
  sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  PrintStream.java:java.io.PrintStream.println:823:   at
  
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

  PrintStream.java:java.io.PrintStream.println:823:   at
  
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  PrintStream.java:java.io.PrintStream.println:823:   at
  java.lang.reflect.Constructor.newInstance(Constructor.java:423)

  PrintStream.java:java.io.PrintStream.println:823:   at
  java.lang.Class.newInstance(Class.java:442)

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.Libbluray.loadAdapter(Libbluray.java:99)

  PrintStream.java:java.io.PrintStream.println:823:   at
  org.videolan.Libbluray.init(Libbluray.java:354)

  bdj.c:737: Failed to initialize BD-J (uncaught exception)
  GUIManager:0: ERROR: getInstance(): no instance !
  bluray.c:3202: Can't play BD-J title 1
  [7f81ec0062c0] libbluray demux error: bluray: stopping playback after 
fatal error

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

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

[Desktop-packages] [Bug 1893439] Re: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect

2020-08-28 Thread Akbarkhon Variskhanov

This behavior can be observed from an Ubuntu Live USB session as well.
Booting up a live Ubuntu 18.04.5 session, installing Unity and trying to
adjust the Pointer speed slider yields the same result, or no result,
shall I say. Hence, I set the status to "Confirmed".

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

Title:
  Adjusting the 'Pointer speed' setting in Bionic running on Unity has
  no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  - What is expected to happen: 
Pointer speed (mouse sensitivity) adjusts according to the slider's 
position.
  - What happens instead:
The setting has no effect on mouse, though the slider can be moved freely.
  - How it happens:
1) Log in into a Unity session;
2) Go to System Settings > Mouse & Touchpad > Try moving the slider to 
either side;
3) The new values are not applied, pointer speed is not updated.

  Whenever the slider's position is moved, the "speed" key in
  "org.gnome.desktop.peripherals.mouse" gsettings schema updates
  accordingly, however the "libinput Accel Speed (290)" property does
  not. It stays at 0. Manually setting a value to this property (xinput
  --set-prop device property value) has an immediate effect.

  This setting works as expected during a GNOME session. Both the
  "speed" key and the "Accel Speed" property update as the slider is
  adjusted.

  Ubuntu 18.04.5 LTS; 
  unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); 
  lightdm 1.26.0 (=1.26.0-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Aug 28 18:34:50 2020
  InstallationDate: Installed on 2016-11-03 (1393 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago)

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

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

[Desktop-packages] [Bug 1893439] Re: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect

2020-08-28 Thread Akbarkhon Variskhanov

** Changed in: unity-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Adjusting the 'Pointer speed' setting in Bionic running on Unity has
  no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  - What is expected to happen: 
Pointer speed (mouse sensitivity) adjusts according to the slider's 
position.
  - What happens instead:
The setting has no effect on mouse, though the slider can be moved freely.
  - How it happens:
1) Log in into a Unity session;
2) Go to System Settings > Mouse & Touchpad > Try moving the slider to 
either side;
3) The new values are not applied, pointer speed is not updated.

  Whenever the slider's position is moved, the "speed" key in
  "org.gnome.desktop.peripherals.mouse" gsettings schema updates
  accordingly, however the "libinput Accel Speed (290)" property does
  not. It stays at 0. Manually setting a value to this property (xinput
  --set-prop device property value) has an immediate effect.

  This setting works as expected during a GNOME session. Both the
  "speed" key and the "Accel Speed" property update as the slider is
  adjusted.

  Ubuntu 18.04.5 LTS; 
  unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); 
  lightdm 1.26.0 (=1.26.0-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Aug 28 18:34:50 2020
  InstallationDate: Installed on 2016-11-03 (1393 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago)

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

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

[Desktop-packages] [Bug 1893415] Re: Hardware GPU Compositing not working, missing libGLESV2.so in snap package

2020-08-28 Thread Simon

Thanks everyone, just updated on my machine and it is now working as
expected.

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

Title:
  Hardware GPU Compositing not working, missing libGLESV2.so in snap
  package

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  chrome://gpu/

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only. Hardware acceleration disabled
  Flash Stage3D: Software only. Hardware acceleration disabled
  Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  Out-of-process Rasterization: Disabled
  OpenGL: Disabled
  Hardware Protected Video Decode: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Skia Renderer: Enabled
  Video Decode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  Problems Detected
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Version Information
  Data exported 2020-08-28T12:43:36.316Z
  Chrome versionChrome/85.0.4183.83
  Operating system  Linux 5.4.0-42-generic
  Software rendering list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
  Driver bug list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
  ANGLE commit id   unknown hash
  2D graphics backend   Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
  Command Line  /snap/chromium/1275/usr/lib/chromium-browser/chrome 
--no-default-browser-check --no-first-run --password-store 
--flag-switches-begin --flag-switches-end 
--origin-trial-disabled-features=MeasureMemory

  [truncated]

  Problems Detected for Hardware GPU
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Log Messages
  [31619:31619:0828/134331.474558:ERROR:gl_implementation.cc(286)] : Failed to 
load /snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: 
/snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: cannot open shared 
object file: No such file or directory
  [31619:31619:0828/134331.475780:ERROR:viz_main_impl.cc(150)] : Exiting GPU 
process due to errors during initialization
  GpuProcessHost: The GPU process exited normally. Everything is okay.
  [31627:31627:0828/134336.157808:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.159639:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.160909:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader

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

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

[Desktop-packages] [Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-28 Thread Dimitri John Ledkov

@satmandu

Thank you for pointing that documentation out.

It is correct that it is helpful to test Proposed, but I think that
information was written when packages in proposed were only published
for stable series, which only contain prospective Stable Release
Updates, and is the way "for testing updates".

That is not true for devel series. In devel series, -proposed is not for
human consumption. Instead simply running devel series, release pocket
is already testing and providing feedback from such config is useful.

I'm not sure how we can update that testing page to be more informative.

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

Title:
  gnome-shell crashing (libffi8ubuntu1 upgrade issue)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libffi package in Ubuntu:
  Incomplete

Bug description:
  Seeing this on groovy installs after an update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.4-1ubuntu2~build1
  Uname: Linux 5.8.3-050803-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Aug 25 15:49:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (311 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2
  ShellJournal:
   -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 
EDT. --
   -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087

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

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

[Desktop-packages] [Bug 1893444] [NEW] Screen locking issue

2020-08-28 Thread praveen

Public bug reported:

screen goes down automatically, while working

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
Uname: Linux 4.15.0-115-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 28 20:15:27 2020
InstallationDate: Installed on 2015-10-17 (1776 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.xdg.autostart.gnome-screensaver.desktop: 
2015-10-18T14:10:39.156974

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


** Tags: amd64 apport-bug bionic

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

Title:
  Screen locking issue

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  screen goes down automatically, while working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 20:15:27 2020
  InstallationDate: Installed on 2015-10-17 (1776 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-screensaver.desktop: 
2015-10-18T14:10:39.156974

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)

Patch submitted upstream:
https://phabricator.services.mozilla.com/D88588

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

Title:
  Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
  (gtk_window_set_titlebar)

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When testing firefox 80.0+build2 on xenial (from https://launchpad.net
  /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm
  observing that the flash plugin (installed by flashplugin-installer)
  doesn't work. This appears to affect only xenial, flash is working in
  the bionic and focal builds.

  This is what I'm seeing when launching firefox from a terminal:

/usr/lib/firefox/plugin-container: symbol lookup error:
  /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar

  This is most likely caused by this recent upstream change:
  https://phabricator.services.mozilla.com/D84623

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)

> How does one apply patch?

Just wait for the update to be available in xenial-security, which
should happen later today.

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

Title:
  Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
  (gtk_window_set_titlebar)

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When testing firefox 80.0+build2 on xenial (from https://launchpad.net
  /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm
  observing that the flash plugin (installed by flashplugin-installer)
  doesn't work. This appears to affect only xenial, flash is working in
  the bionic and focal builds.

  This is what I'm seeing when launching firefox from a terminal:

/usr/lib/firefox/plugin-container: symbol lookup error:
  /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar

  This is most likely caused by this recent upstream change:
  https://phabricator.services.mozilla.com/D84623

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)

Upstream bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1661715

** Bug watch added: Mozilla Bugzilla #1661715
   https://bugzilla.mozilla.org/show_bug.cgi?id=1661715

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1661715
   Importance: Unknown
   Status: Unknown

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

Title:
  Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
  (gtk_window_set_titlebar)

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When testing firefox 80.0+build2 on xenial (from https://launchpad.net
  /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm
  observing that the flash plugin (installed by flashplugin-installer)
  doesn't work. This appears to affect only xenial, flash is working in
  the bionic and focal builds.

  This is what I'm seeing when launching firefox from a terminal:

/usr/lib/firefox/plugin-container: symbol lookup error:
  /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar

  This is most likely caused by this recent upstream change:
  https://phabricator.services.mozilla.com/D84623

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

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

[Desktop-packages] [Bug 1893415] Re: Hardware GPU Compositing not working, missing libGLESV2.so in snap package

And this is fixed in revision 1279 (now in the stable channel).

The corresponding commit is https://git.launchpad.net/~chromium-team
/chromium-browser/+git/snap-from-
source/commit/?h=stable=6f619f7ac589a5e8343dc0cde275a5eec83bdc15.

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

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => High

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

Title:
  Hardware GPU Compositing not working, missing libGLESV2.so in snap
  package

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  chrome://gpu/

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only. Hardware acceleration disabled
  Flash Stage3D: Software only. Hardware acceleration disabled
  Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  Out-of-process Rasterization: Disabled
  OpenGL: Disabled
  Hardware Protected Video Decode: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Skia Renderer: Enabled
  Video Decode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  Problems Detected
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Version Information
  Data exported 2020-08-28T12:43:36.316Z
  Chrome versionChrome/85.0.4183.83
  Operating system  Linux 5.4.0-42-generic
  Software rendering list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
  Driver bug list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
  ANGLE commit id   unknown hash
  2D graphics backend   Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
  Command Line  /snap/chromium/1275/usr/lib/chromium-browser/chrome 
--no-default-browser-check --no-first-run --password-store 
--flag-switches-begin --flag-switches-end 
--origin-trial-disabled-features=MeasureMemory

  [truncated]

  Problems Detected for Hardware GPU
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Log Messages
  [31619:31619:0828/134331.474558:ERROR:gl_implementation.cc(286)] : Failed to 
load /snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: 
/snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: cannot open shared 
object file: No such file or directory
  [31619:31619:0828/134331.475780:ERROR:viz_main_impl.cc(150)] : Exiting GPU 
process due to errors during initialization
  GpuProcessHost: The GPU process exited normally. Everything is okay.
  [31627:31627:0828/134336.157808:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.159639:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.160909:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)

2020-08-28 Thread treloar

How does one apply patch?

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

Title:
  Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
  (gtk_window_set_titlebar)

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When testing firefox 80.0+build2 on xenial (from https://launchpad.net
  /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm
  observing that the flash plugin (installed by flashplugin-installer)
  doesn't work. This appears to affect only xenial, flash is working in
  the bionic and focal builds.

  This is what I'm seeing when launching firefox from a terminal:

/usr/lib/firefox/plugin-container: symbol lookup error:
  /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar

  This is most likely caused by this recent upstream change:
  https://phabricator.services.mozilla.com/D84623

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

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

[Desktop-packages] [Bug 1893439] [NEW] Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect

2020-08-28 Thread Akbarkhon Variskhanov

Public bug reported:

- What is expected to happen: 
  Pointer speed (mouse sensitivity) adjusts according to the slider's position.
- What happens instead:
  The setting has no effect on mouse, though the slider can be moved freely.
- How it happens:
  1) Log in into a Unity session;
  2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either 
side;
  3) The new values are not applied, pointer speed is not updated.

Whenever the slider's position is moved, the "speed" key in
"org.gnome.desktop.peripherals.mouse" gsettings schema updates
accordingly, however the "libinput Accel Speed (290)" property does not.
It stays at 0. Manually setting a value to this property (xinput --set-
prop device property value) has an immediate effect.

This setting works as expected during a GNOME session. Both the "speed"
key and the "Accel Speed" property update as the slider is adjusted.

Ubuntu 18.04.5 LTS; 
unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); 
lightdm 1.26.0 (=1.26.0-0ubuntu1).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Aug 28 18:34:50 2020
InstallationDate: Installed on 2016-11-03 (1393 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago)

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


** Tags: bionic mouse unity-control-center

** Attachment added: "graphical representation"
   https://bugs.launchpad.net/bugs/1893439/+attachment/5405447/+files/mouse.png

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

Title:
  Adjusting the 'Pointer speed' setting in Bionic running on Unity has
  no effect

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

Bug description:
  - What is expected to happen: 
Pointer speed (mouse sensitivity) adjusts according to the slider's 
position.
  - What happens instead:
The setting has no effect on mouse, though the slider can be moved freely.
  - How it happens:
1) Log in into a Unity session;
2) Go to System Settings > Mouse & Touchpad > Try moving the slider to 
either side;
3) The new values are not applied, pointer speed is not updated.

  Whenever the slider's position is moved, the "speed" key in
  "org.gnome.desktop.peripherals.mouse" gsettings schema updates
  accordingly, however the "libinput Accel Speed (290)" property does
  not. It stays at 0. Manually setting a value to this property (xinput
  --set-prop device property value) has an immediate effect.

  This setting works as expected during a GNOME session. Both the
  "speed" key and the "Accel Speed" property update as the slider is
  adjusted.

  Ubuntu 18.04.5 LTS; 
  unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); 
  lightdm 1.26.0 (=1.26.0-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Aug 28 18:34:50 2020
  InstallationDate: Installed on 2016-11-03 (1393 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago)

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

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

[Desktop-packages] [Bug 1893415] Re: Hardware GPU Compositing not working, missing libGLESV2.so in snap package

2020-08-28 Thread Jose Mico

The bug was introduced in rev 1275 (85.0.4183.83).

Previous rev 1269 (84.0.4147.135) was working fine.

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

Title:
  Hardware GPU Compositing not working, missing libGLESV2.so in snap
  package

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chrome://gpu/

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only. Hardware acceleration disabled
  Flash Stage3D: Software only. Hardware acceleration disabled
  Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  Out-of-process Rasterization: Disabled
  OpenGL: Disabled
  Hardware Protected Video Decode: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Skia Renderer: Enabled
  Video Decode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  Problems Detected
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Version Information
  Data exported 2020-08-28T12:43:36.316Z
  Chrome versionChrome/85.0.4183.83
  Operating system  Linux 5.4.0-42-generic
  Software rendering list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
  Driver bug list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
  ANGLE commit id   unknown hash
  2D graphics backend   Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
  Command Line  /snap/chromium/1275/usr/lib/chromium-browser/chrome 
--no-default-browser-check --no-first-run --password-store 
--flag-switches-begin --flag-switches-end 
--origin-trial-disabled-features=MeasureMemory

  [truncated]

  Problems Detected for Hardware GPU
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Log Messages
  [31619:31619:0828/134331.474558:ERROR:gl_implementation.cc(286)] : Failed to 
load /snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: 
/snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: cannot open shared 
object file: No such file or directory
  [31619:31619:0828/134331.475780:ERROR:viz_main_impl.cc(150)] : Exiting GPU 
process due to errors during initialization
  GpuProcessHost: The GPU process exited normally. Everything is okay.
  [31627:31627:0828/134336.157808:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.159639:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.160909:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader

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

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

[Desktop-packages] [Bug 1893415] Re: Hardware GPU Compositing not working, missing libGLESV2.so in snap package

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  Hardware GPU Compositing not working, missing libGLESV2.so in snap
  package

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chrome://gpu/

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only. Hardware acceleration disabled
  Flash Stage3D: Software only. Hardware acceleration disabled
  Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  Out-of-process Rasterization: Disabled
  OpenGL: Disabled
  Hardware Protected Video Decode: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Skia Renderer: Enabled
  Video Decode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  Problems Detected
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Version Information
  Data exported 2020-08-28T12:43:36.316Z
  Chrome versionChrome/85.0.4183.83
  Operating system  Linux 5.4.0-42-generic
  Software rendering list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
  Driver bug list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
  ANGLE commit id   unknown hash
  2D graphics backend   Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
  Command Line  /snap/chromium/1275/usr/lib/chromium-browser/chrome 
--no-default-browser-check --no-first-run --password-store 
--flag-switches-begin --flag-switches-end 
--origin-trial-disabled-features=MeasureMemory

  [truncated]

  Problems Detected for Hardware GPU
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Log Messages
  [31619:31619:0828/134331.474558:ERROR:gl_implementation.cc(286)] : Failed to 
load /snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: 
/snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: cannot open shared 
object file: No such file or directory
  [31619:31619:0828/134331.475780:ERROR:viz_main_impl.cc(150)] : Exiting GPU 
process due to errors during initialization
  GpuProcessHost: The GPU process exited normally. Everything is okay.
  [31627:31627:0828/134336.157808:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.159639:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.160909:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader

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

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

[Desktop-packages] [Bug 1866038] Re: By default install Noto fonts for Unicode ranges not already covered by default

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

** Changed in: fonts-noto (Ubuntu)
   Status: New => Confirmed

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

Title:
  By default install Noto fonts for Unicode ranges not already covered
  by default

Status in fonts-noto package in Ubuntu:
  Confirmed

Bug description:
  There is currently movement towards protecting browser users from font
  fingerprinting. This means refusing, by default, to load user-
  installed fonts, which makes the set of fonts that each OS installs by
  default even more important than before.

  Firefox bug:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1582687

  W3C CSS WG issue:
  https://github.com/w3c/csswg-drafts/issues/4497

  Currently, Windows 10, macOS, Android, Chrome OS, and, to a lesser
  extent, Fedora provide broader installed-by-default Unicode coverage
  than Ubuntu.

  Examples of living scripts that have enough active users to make it to
  the list at
  
https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scripts_by_adoption
  but are not supported by default in Eoan include Javanese, Sundanese,
  Batak, Balinese, Modern Yi, Mongolian, and New Tai Lue.

  Egyptian hieroglyphs is an example of a dead script the Eoan doesn't
  support but Windows 10, macOS, Chrome OS, and Android do support.

  To remedy this with minimal disk space impact, I suggest the same
  approach that Apple took. Apple bundles with macOS those Noto fonts
  that cover scripts that were not already covered by the previous
  installed-by-default set of fonts on macOS. In the macOS case, the on-
  disk footprint of the Noto fonts that were required to take macOS to
  Android/Chrome OS-competitive Unicode coverage was only a couple of
  megabytes. (The fonts are hidden in /Library/Application
  Support/Apple/Fonts/Language Support/.) In the case of Ubuntu, the set
  of Noto fonts required to reach the Chrome OS / Android level of
  script coverage is a bit larger than in the macOS case but should
  still be manageable.

  Please install, by default, those Noto fonts that provide support for
  scripts that are not properly supported by the fonts that Ubuntu
  already installs by default.

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

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

[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows

2020-08-28 Thread Andrzej Dubiel

Whoa! I have experienced something interesting.
The issue disappeared when I tried to debug something with mouse and use `xev`.
After starting it (and also after closing it) - focus issue disappeared.
It would be awesome if this helped to fix it. Not sure if this is related but 
I'm temporary happy (will see for how long it is).

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

Title:
  Focus gets stuck to a window - impossible to select other windows

Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Alright, terribly annoying bug that gets me to reboot several times a
  day, but very hard to understand how to trigger it.

  What happens: after some time of usage, you get "stuck" in a window. Idem 
est, you can not select another window. 
  You can still click, select and drag in the window that has the focus, but 
clicking on other windows, or on the panel, just doesn't work.

  Notes:
  - With window I don't mean "application window". For example it can only be 
the page view in firefox, and  you won't be able to click the buttons or the 
URL field. It can also be the main text window in xchat, and you wont be able 
to click in the user list or to change the chatroom.
  - The click seems to be grabbed by the window having the focus, even if you 
click outside of it. For example, using xchat, if the main text window has 
focus, clicking and dragging in the user list will actually select text in the 
main text window.
  - Using xev, it seems that clics do not get passed to the correct window at 
all (nothing received)
  - I have no idea what triggers this as sometimes it will trigger alone - pc 
works, I leave it for an hour, I come back, the problem is triggered
  - Curious effect now: dragging and dropping to another window gives focus to 
the window, and seems to be the only way to do so. For example if in firefox 
the main page view window has the focus and I cant click the buttons, drag and 
dropping text to the buttons gives the focus to the buttons, and I can't clic 
the page view window anymore. Drag and dropping a button to the page view 
window gives it its focus back

  
  Additional info: 
  * Compiz disabled
  * Intel graphic card
  * Ubuntu jaunty - latest patches
  * Using a laptop, with an USB mouse

  HAL, xserver, I have no idea where to file this bug into. I hope it will be 
fixed before the release, it is really terribly annoying :s 
  Please tell me if there is any other detail I can provide.

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

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

[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2020-08-28 Thread Hauke Wintjen

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

Disabling 'desktop icons' from the extensions app did not work for me, but 
renaming the 
folder /usr/share/gnome-shell/extensions/desktop-icons@csoriano did the trick.

The extension was already disabled. After folder renamed, login works
quick again. Thanks

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

Title:
  Locking and unlocking the screen is slow and stuttery

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

Bug description:
  Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 14 10:10:38 2019
  InstallationDate: Installed on 2019-06-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049

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

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

[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows

2020-08-28 Thread Andrzej Dubiel

@arnfranke
I just experienced it too last week. I'm using Ubuntu since 2015.
Current mouse (trackball) I used from the beginning of 2020. It works with no 
issue with Ubuntu 18.04. Issue occurred just after last Ubuntu update (middle 
of August).
Whats funny when I have my mouse/trackball plugged in I have this issue also 
with touchpad.
When I remove mouse USB - everything works fine again.
Another thing is that when I plug in other mouse or trackball - the issue is 
not present. It is just with single device.

I also tried with another laptop with Ubuntu 18.04 (without update) I
worked on it 2 hours - there were no issues. Then I just updated Ubuntu
and restarted that second laptop and... issue occurred also on the
second machine and again just after Ubuntu update. I'm mad, I love to
work with my trackball but I cannot now.

This behavior is so strange.

Also when I unplug my trackball and plug it agan it works fine for 30-60
seconds and then issue occurred again.

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

Title:
  Focus gets stuck to a window - impossible to select other windows

Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Alright, terribly annoying bug that gets me to reboot several times a
  day, but very hard to understand how to trigger it.

  What happens: after some time of usage, you get "stuck" in a window. Idem 
est, you can not select another window. 
  You can still click, select and drag in the window that has the focus, but 
clicking on other windows, or on the panel, just doesn't work.

  Notes:
  - With window I don't mean "application window". For example it can only be 
the page view in firefox, and  you won't be able to click the buttons or the 
URL field. It can also be the main text window in xchat, and you wont be able 
to click in the user list or to change the chatroom.
  - The click seems to be grabbed by the window having the focus, even if you 
click outside of it. For example, using xchat, if the main text window has 
focus, clicking and dragging in the user list will actually select text in the 
main text window.
  - Using xev, it seems that clics do not get passed to the correct window at 
all (nothing received)
  - I have no idea what triggers this as sometimes it will trigger alone - pc 
works, I leave it for an hour, I come back, the problem is triggered
  - Curious effect now: dragging and dropping to another window gives focus to 
the window, and seems to be the only way to do so. For example if in firefox 
the main page view window has the focus and I cant click the buttons, drag and 
dropping text to the buttons gives the focus to the buttons, and I can't clic 
the page view window anymore. Drag and dropping a button to the page view 
window gives it its focus back

  
  Additional info: 
  * Compiz disabled
  * Intel graphic card
  * Ubuntu jaunty - latest patches
  * Using a laptop, with an USB mouse

  HAL, xserver, I have no idea where to file this bug into. I hope it will be 
fixed before the release, it is really terribly annoying :s 
  Please tell me if there is any other detail I can provide.

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

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

[Desktop-packages] [Bug 1893415] [NEW] Hardware GPU Compositing not working, missing libGLESV2.so in snap package

2020-08-28 Thread Simon

Public bug reported:

chrome://gpu/

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only. Hardware acceleration disabled
Flash Stage3D: Software only. Hardware acceleration disabled
Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Disabled
Hardware Protected Video Decode: Disabled
Rasterization: Software only. Hardware acceleration disabled
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Software only, hardware acceleration unavailable
WebGL2: Software only, hardware acceleration unavailable
Problems Detected
Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
Disabled Features: gpu_compositing

Version Information
Data exported   2020-08-28T12:43:36.316Z
Chrome version  Chrome/85.0.4183.83
Operating systemLinux 5.4.0-42-generic
Software rendering list URL 
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
Driver bug list URL 
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
ANGLE commit id unknown hash
2D graphics backend Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
Command Line/snap/chromium/1275/usr/lib/chromium-browser/chrome 
--no-default-browser-check --no-first-run --password-store 
--flag-switches-begin --flag-switches-end 
--origin-trial-disabled-features=MeasureMemory

[truncated]

Problems Detected for Hardware GPU
Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
Disabled Features: gpu_compositing

Log Messages
[31619:31619:0828/134331.474558:ERROR:gl_implementation.cc(286)] : Failed to 
load /snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: 
/snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: cannot open shared 
object file: No such file or directory
[31619:31619:0828/134331.475780:ERROR:viz_main_impl.cc(150)] : Exiting GPU 
process due to errors during initialization
GpuProcessHost: The GPU process exited normally. Everything is okay.
[31627:31627:0828/134336.157808:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
[31627:31627:0828/134336.159639:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
[31627:31627:0828/134336.160909:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader

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

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

Title:
  Hardware GPU Compositing not working, missing libGLESV2.so in snap
  package

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  chrome://gpu/

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only. Hardware acceleration disabled
  Flash Stage3D: Software only. Hardware acceleration disabled
  Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  Out-of-process Rasterization: Disabled
  OpenGL: Disabled
  Hardware Protected Video Decode: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Skia Renderer: Enabled
  Video Decode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  Problems Detected
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Version Information
  Data exported 2020-08-28T12:43:36.316Z
  Chrome versionChrome/85.0.4183.83
  Operating system  Linux 5.4.0-42-generic
  Software rendering list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
  Driver bug list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
  ANGLE commit id   unknown hash
  2D graphics backend   Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
  Command

[Desktop-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

2020-08-28 Thread Aaron Wagner

Possibly related to this:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405

That bug focuses on the soft lockup but nouveau has come up as a factor.

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

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

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

2020-08-28 Thread Aaron Wagner

Just upgraded to 16.04 LTS and that works as well. To be clear, for both
14.04 and 16.04, the proprietary NVIDIA drivers are available via the
nvidia-304 package, but I'm not using those. The nouveau driver itself
works on 14.04 and 16.04.

FWIW, back when I tried running 18.04/20.04, when programs were hanging
I checked dmesg and saw errors of the form "watchdog: BUG: soft lockup -
CPU#3 stuck for 22s"

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

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

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

2020-08-28 Thread Daniel van Vugt

I have an idea:

Anyone experiencing this crash reliably, please help us to find its root
cause by editing your /etc/environment and adding a line:

  MUTTER_SYNC=1

and then reboot. Then next time a crash happens please tell us (here)
the bug ID or error URL of the new crash.


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

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

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

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

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

  Similar error:
  https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd

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

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

2020-08-28 Thread Olcay Ozturkmen

It does affect linux kernel.

-- 
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
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
  --- 
  ProblemType: Bug
  ApportVersion:

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

apport information

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

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

Title:
  Double-click on a desktop app shortcut doesn't deselect the shortcut

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1
  GNOME 3.36.2
  GNOME extensions: dash-to-panel 39
  Xorg 7.7+19ubuntu14

  Starting an app from its .desktop shortcut should deselect the
  shortcut icon after double-clicking on it, because it lets the user
  know that the double-click was registered (as opposed to a single
  click) and the application is starting.

  This makes a difference if the app is slow to start, since I'm not sure 
anymore whether I should double-click again or not.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-26 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-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-extension-desktop-icons/+bug/1893265/+subscriptions

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

[Desktop-packages] [Bug 1893265] Re: Double-click on a desktop app shortcut doesn't deselect the shortcut

GitLab GNOME bug id is 217:
https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/-/issues/217

I also ran 'apport-collect 189326' and selected 'Send report (26 KB)'.
Will use 'ubuntu-bug' in the future.

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

Title:
  Double-click on a desktop app shortcut doesn't deselect the shortcut

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1
  GNOME 3.36.2
  GNOME extensions: dash-to-panel 39
  Xorg 7.7+19ubuntu14

  Starting an app from its .desktop shortcut should deselect the
  shortcut icon after double-clicking on it, because it lets the user
  know that the double-click was registered (as opposed to a single
  click) and the application is starting.

  This makes a difference if the app is slow to start, since I'm not sure 
anymore whether I should double-click again or not.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-26 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-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-extension-desktop-icons/+bug/1893265/+subscriptions

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

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

apport information

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

** Bug watch added: 
gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #217
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/217

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

Title:
  Double-click on a desktop app shortcut doesn't deselect the shortcut

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1
  GNOME 3.36.2
  GNOME extensions: dash-to-panel 39
  Xorg 7.7+19ubuntu14

  Starting an app from its .desktop shortcut should deselect the
  shortcut icon after double-clicking on it, because it lets the user
  know that the double-click was registered (as opposed to a single
  click) and the application is starting.

  This makes a difference if the app is slow to start, since I'm not sure 
anymore whether I should double-click again or not.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-26 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-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-extension-desktop-icons/+bug/1893265/+subscriptions

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

[Desktop-packages] [Bug 1893265] Re: Double-click on a desktop app shortcut doesn't deselect the shortcut

apport information

** Tags added: apport-collected

** Description changed:

  Ubuntu 20.04.1
  GNOME 3.36.2
  GNOME extensions: dash-to-panel 39
  Xorg 7.7+19ubuntu14
  
  Starting an app from its .desktop shortcut should deselect the shortcut
  icon after double-clicking on it, because it lets the user know that the
  double-click was registered (as opposed to a single click) and the
  application is starting.
  
- This makes a difference if the app is slow to start, since I'm not sure
- anymore whether I should double-click again or not.
+ This makes a difference if the app is slow to start, since I'm not sure 
anymore whether I should double-click again or not.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.8
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-08-26 (2 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ Tags:  focal
+ Uname: Linux 5.4.0-42-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/1893265/+attachment/5405422/+files/Dependencies.txt

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

Title:
  Double-click on a desktop app shortcut doesn't deselect the shortcut

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1
  GNOME 3.36.2
  GNOME extensions: dash-to-panel 39
  Xorg 7.7+19ubuntu14

  Starting an app from its .desktop shortcut should deselect the
  shortcut icon after double-clicking on it, because it lets the user
  know that the double-click was registered (as opposed to a single
  click) and the application is starting.

  This makes a difference if the app is slow to start, since I'm not sure 
anymore whether I should double-click again or not.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-26 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-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-extension-desktop-icons/+bug/1893265/+subscriptions

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

[Desktop-packages] [Bug 1893332] Re: LibreOffice dialogs are garbled

2020-08-28 Thread Sven Neuz

And here's lshw

** Attachment added: "lshw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1893332/+attachment/5405416/+files/lshw.txt

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

Title:
  LibreOffice dialogs are garbled

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Behaviour: The LibreOffice dialogs are completely unreadable, thus rendering 
the software useless.
  Expected: Normal display of the dialogs.

  See attached screenshot.

  Kubuntu 20.04 + Wayland
  Libreoffice:
  Version: 6.4.5.2
  Build ID: 1:6.4.5-0ubuntu0.20.04.1
  CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: kf5; 
  Locale: en-US (en_DE.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.5-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 28 11:43:18 2020
  InstallationDate: Installed on 2019-09-20 (342 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893332] Re: LibreOffice dialogs are garbled

2020-08-28 Thread Sven Neuz

It happens on Wayland only. Xorg works.
dmesg is attached.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1893332/+attachment/5405415/+files/dmesg.txt

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

Title:
  LibreOffice dialogs are garbled

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Behaviour: The LibreOffice dialogs are completely unreadable, thus rendering 
the software useless.
  Expected: Normal display of the dialogs.

  See attached screenshot.

  Kubuntu 20.04 + Wayland
  Libreoffice:
  Version: 6.4.5.2
  Build ID: 1:6.4.5-0ubuntu0.20.04.1
  CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: kf5; 
  Locale: en-US (en_DE.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.5-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 28 11:43:18 2020
  InstallationDate: Installed on 2019-09-20 (342 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893332] Re: LibreOffice dialogs are garbled

2020-08-28 Thread lotuspsychje

Thank you for filing this bug and make ubuntu better!
Could you please attach your dmesg log and perhaps also sudo lshw -C video ?

does your bug occur on Xorg aswell?

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

Title:
  LibreOffice dialogs are garbled

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Behaviour: The LibreOffice dialogs are completely unreadable, thus rendering 
the software useless.
  Expected: Normal display of the dialogs.

  See attached screenshot.

  Kubuntu 20.04 + Wayland
  Libreoffice:
  Version: 6.4.5.2
  Build ID: 1:6.4.5-0ubuntu0.20.04.1
  CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: kf5; 
  Locale: en-US (en_DE.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.5-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 28 11:43:18 2020
  InstallationDate: Installed on 2019-09-20 (342 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893332] [NEW] LibreOffice dialogs are garbled

2020-08-28 Thread Sven Neuz

Public bug reported:

Behaviour: The LibreOffice dialogs are completely unreadable, thus rendering 
the software useless.
Expected: Normal display of the dialogs.

See attached screenshot.

Kubuntu 20.04 + Wayland
Libreoffice:
Version: 6.4.5.2
Build ID: 1:6.4.5-0ubuntu0.20.04.1
CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: kf5; 
Locale: en-US (en_DE.UTF-8); UI-Language: en-US
Calc: threaded

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice 1:6.4.5-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Aug 28 11:43:18 2020
InstallationDate: Installed on 2019-09-20 (342 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages wayland-session

** Attachment added: "Screenshot_20200828_113448.png"
   
https://bugs.launchpad.net/bugs/1893332/+attachment/5405407/+files/Screenshot_20200828_113448.png

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

Title:
  LibreOffice dialogs are garbled

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Behaviour: The LibreOffice dialogs are completely unreadable, thus rendering 
the software useless.
  Expected: Normal display of the dialogs.

  See attached screenshot.

  Kubuntu 20.04 + Wayland
  Libreoffice:
  Version: 6.4.5.2
  Build ID: 1:6.4.5-0ubuntu0.20.04.1
  CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: kf5; 
  Locale: en-US (en_DE.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.5-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 28 11:43:18 2020
  InstallationDate: Installed on 2019-09-20 (342 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph

2020-08-28 Thread Daniel van Vugt

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

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [enhancement] Replace/extend the "Activities" label with the Ubuntu
  icon/logo/glyph

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  I suggest replacing the "Activities" label with the Ubuntu icon/logo.

  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

2020-08-28 Thread Administration

Hi,

we have discovered the exact same issue using an HP Zbook 15 G6 and an
up-to-date Ubuntu 20.04 installation.

- With standard settings, the laptop freezes at the login screen
- nomodeset does not stop the freezes from being happening
- when using snd-hda-intel dmic_detect=0 as a kernel parameter, there are no 
freezes any more, but the mic isn't working

A complete fix for this problem would be great.

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

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

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

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

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

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

[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake

2020-08-28 Thread Hui Wang

@Tessa,

Please collect some log:

fresh booting up, and select hdmi audio as output, then run pacmd list >
before.txt

suspend and resume, make sure the output is switched to on-board device,
run pacmd list > after.txt

then upload the before.txt and after.txt.

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

Title:
  pulseaudio has is buggy with hdmi audio and sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Desktop-packages] [Bug 1842048] Re: gnome-system-monitor show incorrect network speed

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

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

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

Title:
  gnome-system-monitor show incorrect network speed

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  Hello, i have Ubuntu 19.04 and internet with 100 megabit per second
  (max 12.5 megabyte per second).

  I copied file via scp over vpn from remote server to my desktop:
  vodka@vodka-PC:~$ scp -o  'ProxyJump=secret_user@192.168.228.11'  
secret_user@192.168.224.196:/tmp/28/secret_database_2019-08-27.dump /tmp/

  You can see in screen (https://i.imgur.com/OfH3GWF.png) that download
  speed was 9.1 megabytes per second (72.8 megabit per second), but in
  system-monitor we saw 187.3 megabits per second, which not
  unachievable with my network...

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-system-monitor 3.32.1-1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 30 13:04:22 2019
  InstallationDate: Installed on 2018-05-02 (484 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to disco on 2019-04-18 (133 days ago)

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

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

[Desktop-packages] [Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged

2020-08-28 Thread hugh chao

** Also affects: system-config-printer (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.
  
  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)
  
  [Expected result]
  The status should show disabled.
  
  [Actual result]
  The status shows idle.
+ 
+ [info]
+ Target:
+ HP LaserJet Pro203dw
+ HP Officejet 100 Mobile Printer
+ HP Officeject 200 Mobile Printer

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Confirmed
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer

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

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

[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph

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

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

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

Title:
  [enhancement] Replace/extend the "Activities" label with the Ubuntu
  icon/logo/glyph

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  I suggest replacing the "Activities" label with the Ubuntu icon/logo.

  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph

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

** Changed in: yaru-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  [enhancement] Replace/extend the "Activities" label with the Ubuntu
  icon/logo/glyph

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  I suggest replacing the "Activities" label with the Ubuntu icon/logo.

  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

2020-08-28 Thread juziy

** Also affects: linux
   Importance: Undecided
   Status: New

** No longer affects: linux

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

[Desktop-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2020-08-28 Thread MohammadAli

Same problem with Ubuntu 20.04.1 LTS on Asus N55sf laptop.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in pm-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Desktop-packages] [Bug 1830473] Re: Does not handle glyphless fonts, as used by tesseract

2020-08-28 Thread Bug Watch Updater

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

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

Title:
  Does not handle glyphless fonts, as used by tesseract

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  PDF documents OCRed with tesseract show black boxes when selecting text

  [Test case]
  Run ocrmypdf on a pdf, open it in evince, select some text. You should not 
see black boxes.

  [Regression potential]
  The patch is minimal invasive and only changes the behavior for the tesseract 
glyphless font.

  [Other info]
  Upstream is unhelpfully refusing to merge the patch in 
https://gitlab.freedesktop.org/poppler/poppler/merge_requests/208 because it's 
not abstract enough for them (as it only handles tesseract).

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

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

[Desktop-packages] [Bug 1886271] Re: HEIF support should be installed by default

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

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

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

Title:
  HEIF support should be installed by default

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  The HEIF image file format [1] is getting quite popular, mainly
  because this is now the default image format for iOS [2].
  Unfortunately, this is not supported by default in Ubuntu (20.04). In
  practice, this means that if someone sends you a picture from an
  iPhone, you won't be able to look at it (and the error message in eog
  is just saying this "is not a image",  not hinting at all that
  installing a small package could solve it).

  Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
  heif-gdk-pixbuf
  heif-thumbnailer

  
  [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
  [2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

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

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

[Desktop-packages] [Bug 1886271] Re: HEIF support should be installed by default

2020-08-28 Thread Joachim Bauch

Assigning to eog as per comment #1.

** Package changed: libheif (Ubuntu) => eog (Ubuntu)

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

Title:
  HEIF support should be installed by default

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  The HEIF image file format [1] is getting quite popular, mainly
  because this is now the default image format for iOS [2].
  Unfortunately, this is not supported by default in Ubuntu (20.04). In
  practice, this means that if someone sends you a picture from an
  iPhone, you won't be able to look at it (and the error message in eog
  is just saying this "is not a image",  not hinting at all that
  installing a small package could solve it).

  Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
  heif-gdk-pixbuf
  heif-thumbnailer

  
  [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
  [2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

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

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

[Desktop-packages] [Bug 1893313] [NEW] totem unable to play h.264 and many videos 20.04 Ubuntu can i tried adding many decorder

2020-08-28 Thread dev

Public bug reported:

totem can't able to play h.264 videos or acc audio file in videos.
Also old totem in 20.04 can play most of the file. after upgrading it stops 
playing.
Before installing any encoder it shows download h.264 decoder from ubuntu 
software but after clicking it it show you need to enable 3rd party repo. also 
clicking it doesn't enable it. after installing encoder different codec it 
doesn't show download from ubuntu software still. can't play.
Ultimately I have to install vlc from snap

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libgstreamer1.0-0 1.16.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
Uname: Linux 5.8.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 28 12:01:51 2020
InstallationDate: Installed on 2020-08-13 (14 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to groovy on 2020-08-21 (6 days ago)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: amd64 apport-bug groovy third-party-packages

** Attachment added: "This is first case without installing any encoder"
   
https://bugs.launchpad.net/bugs/1893313/+attachment/5405371/+files/Screenshot%20from%202020-08-28%2012-11-59.png

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

Title:
  totem unable to play h.264 and many videos 20.04 Ubuntu can i tried
  adding many decorder

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  totem can't able to play h.264 videos or acc audio file in videos.
  Also old totem in 20.04 can play most of the file. after upgrading it stops 
playing.
  Before installing any encoder it shows download h.264 decoder from ubuntu 
software but after clicking it it show you need to enable 3rd party repo. also 
clicking it doesn't enable it. after installing encoder different codec it 
doesn't show download from ubuntu software still. can't play.
  Ultimately I have to install vlc from snap

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libgstreamer1.0-0 1.16.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 12:01:51 2020
  InstallationDate: Installed on 2020-08-13 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to groovy on 2020-08-21 (6 days ago)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1893313] Re: totem unable to play h.264 and many videos 20.04 Ubuntu can i tried adding many decorder

2020-08-28 Thread dev

All logs shows the first case

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

Title:
  totem unable to play h.264 and many videos 20.04 Ubuntu can i tried
  adding many decorder

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  totem can't able to play h.264 videos or acc audio file in videos.
  Also old totem in 20.04 can play most of the file. after upgrading it stops 
playing.
  Before installing any encoder it shows download h.264 decoder from ubuntu 
software but after clicking it it show you need to enable 3rd party repo. also 
clicking it doesn't enable it. after installing encoder different codec it 
doesn't show download from ubuntu software still. can't play.
  Ultimately I have to install vlc from snap

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libgstreamer1.0-0 1.16.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 12:01:51 2020
  InstallationDate: Installed on 2020-08-13 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to groovy on 2020-08-21 (6 days ago)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1893313] Re: totem unable to play h.264 and many videos 20.04 Ubuntu can i tried adding many decorder

2020-08-28 Thread dev

I make the totem at first case all dependences and encoders.

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

Title:
  totem unable to play h.264 and many videos 20.04 Ubuntu can i tried
  adding many decorder

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  totem can't able to play h.264 videos or acc audio file in videos.
  Also old totem in 20.04 can play most of the file. after upgrading it stops 
playing.
  Before installing any encoder it shows download h.264 decoder from ubuntu 
software but after clicking it it show you need to enable 3rd party repo. also 
clicking it doesn't enable it. after installing encoder different codec it 
doesn't show download from ubuntu software still. can't play.
  Ultimately I have to install vlc from snap

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libgstreamer1.0-0 1.16.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 12:01:51 2020
  InstallationDate: Installed on 2020-08-13 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to groovy on 2020-08-21 (6 days ago)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1886271] [NEW] HEIF support should be installed by default

You have been subscribed to a public bug:

The HEIF image file format [1] is getting quite popular, mainly because
this is now the default image format for iOS [2]. Unfortunately, this is
not supported by default in Ubuntu (20.04). In practice, this means that
if someone sends you a picture from an iPhone, you won't be able to look
at it (and the error message in eog is just saying this "is not a
image",  not hinting at all that installing a small package could solve
it).

Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
heif-gdk-pixbuf
heif-thumbnailer


[1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
[2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

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

-- 
HEIF support should be installed by default
https://bugs.launchpad.net/bugs/1886271
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to eog in Ubuntu.

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

[Desktop-packages] [Bug 1893311] [NEW] Add libcurl4-openssl-dev build-dep for lumix camlib

2020-08-28 Thread William Wilhelm

Public bug reported:

The lumix camlib is in a somewhat usable state 
(https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully 
using it for a few months.
It would be good to add the libcurl4-openssl-dev to Build-Depends to enable 
building the lumix camlib.

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

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

Title:
  Add libcurl4-openssl-dev build-dep for lumix camlib

Status in libgphoto2 package in Ubuntu:
  New

Bug description:
  The lumix camlib is in a somewhat usable state 
(https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully 
using it for a few months.
  It would be good to add the libcurl4-openssl-dev to Build-Depends to enable 
building the lumix camlib.

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

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

[Desktop-packages] [Bug 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium

2020-08-28 Thread Aljoscha Vollmerhaus

I'm still able to reproduce it.
Interestingly, the new Chromium window now displays a "file not found" error 
for file:///snap/chromium/1275/firstrun/snap-en.html when launched.


$ gsettings get org.gnome.shell favorite-apps
['thunderbird.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Nautilus.desktop', 
'chromium-browser.desktop', 'org.gnome.Screenshot.desktop', 
'org.gnome.Calculator.desktop']

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

Title:
  [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking
  for chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Deleting the ~/snaps folder in ubuntu seems to permanently break gnome
  dash window tracking.

  Steps to reproduce:

  1) Add chromium-browser.desktop to your dash / dock favourites.
  Chromium Windows get attributed to this favourite when created.

  2) Delete the ~/snaps folder, quit all chromium processes and / or
  reboot

  3) The ~/snaps folder gets recreated, but Chromium windows now get
  attributed to a new chromium-browser dash icon, ignoring the favourite
  created in step 1

  I know I know, don't delete the ~/snaps folder then!

  Unfortunately, there are situations when this is beyond my control.
  These desktops are gonna get into the hands of normal users, like my dad and 
my colleagues.
  They will delete the folder by accident or because they don't know and don't 
care about snaps.
  Deleting it shouldn't permanently break window tracking.

  This is on a fully patched 20.04 system.

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2020-08-28 Thread Daniel van Vugt

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)

The problem is with GTK function stubs being declared in the wrong
sections in widget/gtk/mozgtk/mozgtk.c. Another recent upstream change
did that too: https://phabricator.services.mozilla.com/D82804.

And this patch fixes it:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.xenial/revision/1450

** Changed in: firefox (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
  (gtk_window_set_titlebar)

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When testing firefox 80.0+build2 on xenial (from https://launchpad.net
  /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm
  observing that the flash plugin (installed by flashplugin-installer)
  doesn't work. This appears to affect only xenial, flash is working in
  the bionic and focal builds.

  This is what I'm seeing when launching firefox from a terminal:

/usr/lib/firefox/plugin-container: symbol lookup error:
  /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar

  This is most likely caused by this recent upstream change:
  https://phabricator.services.mozilla.com/D84623

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

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

[Desktop-packages] [Bug 1892814] Status changed to Confirmed

2020-08-28 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  [Cambridge Silicon Radio] Bluetooth has multiple connectivity issues

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

Bug description:
  Pulseaudio has been super unstable since ubuntu 20.04.
  bluetooth has multiple connectivity issues which sometimes can only be 
resolved by unpairing and then pairing again.

  A big problem comes when a bluetooth headset is connected. Sometimes
  it does not show up as well in the sound settings or the wrong profile
  is shown. Sometimes I try changing the profile it works, but other
  times it does not alter anything - e.g. changing from hfp to a2dp
  shows the change but the profile remains. If I switch settings tabs
  and go back to sound settings the old profile remains.

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

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

[Desktop-packages] [Bug 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)