date:20200630

it has been uploaded bow https://launchpad.net/ubuntu/+source/gnome-
software/3.36.1-0ubuntu1

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

Title:
  Update GNOME Software to 3.36.1 in Focal

Status in One Hundred Papercuts:
  New
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gnome-software.

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could cause issues in GNOME Software, which might make it hard
  to install or remove software. Default store in Ubuntu is snap-store,
  so this doesn't affect the majority of users.

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

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

[Desktop-packages] [Bug 1885669] [NEW] screen blinking while start laptop

You have been subscribed to a public bug:

screen blinking

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
Date: Tue Jun 30 11:41:00 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-108-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
InstallationDate: Installed on 2015-10-17 (1717 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.0B
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80C1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.11
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May 28 11:49:11 2020
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.4

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
screen blinking while start laptop
https://bugs.launchpad.net/bugs/1885669
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-06-30 Thread Kai-Chuan Hsieh

** Changed in: oem-priority
   Status: New => 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/1881094

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

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

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

[Desktop-packages] [Bug 1884846] Re: Can't connect to internet if second user session

it seems to be a wpasupplicant / driver issue, from the log

jun 29 18:21:27 tanquita wpa_supplicant[949]: wlp4s0: WPS-TIMEOUT
Requested operation timed out

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

Title:
  Can't connect to internet if second user session

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  My kid was using the laptop, connected to internet in his user
  session.

  I switched to my user (but his session was still active), and
  NetworkManager couldn't connect to internet.

  Error from syslog:

  Jun 23 19:30:15 tanquita NetworkManager[854]: 
  [1592951415.1979] audit: op="connection-activate" uuid="a52379fa-
  0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000
  result="fail" reason="Private connection already active on the device:
  uid 1000 has no permission to perform this operation"

  (uid 1000 is myself)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Jun 23 19:40:19 2020
  InstallationDate: Installed on 2020-06-20 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 
metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1884418] Re: Full text search does not work on Ubuntu 20.04

Thank you for your bug report, that sounds similar to e.g
https://gitlab.gnome.org/GNOME/nautilus/-/issues/502

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #502
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/502

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

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

** Summary changed:

- Full text search does not work on Ubuntu 20.04
+ Full text search restricted to some directories

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

Title:
  Full text search restricted to some directories

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Full text search does not work on Ubuntu 20.04

  * Test case
  - install tracker and restart your session
  - echo 'Nautilus is great' > ~/txt
  - open nautilus and type 'great' in the search entry

  version of nautilus 3.36.3-stable

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

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

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

This bug was fixed in the package libxau - 1:1.0.8-1ubuntu1

---
libxau (1:1.0.8-1ubuntu1) bionic; urgency=medium

  * Add debian/patches/fix-lp1559650.patch to fix a common segfault in
___vsnprintf_chk() that's crashing gnome-shell (LP: #1559650)

 -- Daniel van Vugt   Tue, 21 Apr 2020
15:33:06 +0800

** Changed in: libxau (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  Fix Released
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 42000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1559650] Update Released

2020-06-30 Thread Timo Aaltonen

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

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

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

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  Fix Released
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 42000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

Thanks, there is no point uploading only the gnome-control-center part
for now right? We will keep an eye on the other merge requests, the
pulseaudio discussion seems active though (you mentioned it was rejected
but it seems not yet, or at least solution are being discussed?)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Step to reproduce:

  1. plug-in headset
  2. select headset in pop-up window.
  3. check g-c-c

  Expected result:
correct input is selected so that mic on the headset just works

  Actual result:
The correct input is not selected.

  a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

2020-06-30 Thread Hui Wang

To fix this issue， there are 3 fixes for 3 different packages:

libgvc (no response from maintainer): https://gitlab.gnome.org/GNOME
/libgnome-volume-control/-/merge_requests/10

pulseaudio (rejected by maintainer):
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/295

gnome-control-center (upstream provided and merged a fix):
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1033

So only got the fix for gnome-control-center so far.


** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1033
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1033

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Step to reproduce:

  1. plug-in headset
  2. select headset in pop-up window.
  3. check g-c-c

  Expected result:
correct input is selected so that mic on the headset just works

  Actual result:
The correct input is not selected.

  a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

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

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

[Desktop-packages] [Bug 1885646] Re: RM ring FTBFS

Removing packages from groovy:
ring 20190215.1.f152c98~ds1-1build2 in groovy
jami 20190215.1.f152c98~ds1-1build2 in groovy amd64
jami 20190215.1.f152c98~ds1-1build2 in groovy arm64
jami 20190215.1.f152c98~ds1-1build2 in groovy armhf
jami 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
jami 20190215.1.f152c98~ds1-1build2 in groovy riscv64
jami 20190215.1.f152c98~ds1-1build2 in groovy s390x
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy amd64
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy arm64
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy armhf
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy riscv64
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy s390x
ring 20190215.1.f152c98~ds1-1build2 in groovy amd64
ring 20190215.1.f152c98~ds1-1build2 in groovy arm64
ring 20190215.1.f152c98~ds1-1build2 in groovy armhf
ring 20190215.1.f152c98~ds1-1build2 in groovy i386
ring 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
ring 20190215.1.f152c98~ds1-1build2 in groovy riscv64
ring 20190215.1.f152c98~ds1-1build2 in groovy s390x
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy amd64
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy arm64
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy armhf
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy i386
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy riscv64
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy s390x
Comment: FTBFS, RC-buggy, removed from testing (lp: #1885646)
Remove [y|N]? y


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

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

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

Title:
  RM ring FTBFS

Status in nettle package in Ubuntu:
  Incomplete
Status in ring package in Ubuntu:
  Fix Released
Status in ring package in Debian:
  New

Bug description:
  Please remove
  ring 20190215.1.f152c98~ds1-1build4 groovy-proposed
  ring 20190215.1.f152c98~ds1-1build2 groovy-release

  FTBFS, RC-buggy, removed from testing

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

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

[Desktop-packages] [Bug 1876628] Re: App list not scrolling properly with touchpad

2020-06-30 Thread Honey Yadav

I had same problem, but after removing xserver-xorg-input-synaptics and other 
touchpad related drivers except xserver-xorg-input-libinput, and then rebooting 
it got solved.
See if that helps :)

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

Title:
  App list not scrolling properly with touchpad

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

Bug description:
  Steps to reproduce (20.04), shell 3.36.1:

  1. Open 'Show Applications' -> 'All'
  2. Attempt to scroll through the pages using a touchpad.

  Expected result:
  Scrolls through pages of applications one at a time.

  Actual result:
  Scrolls to second page of applications but will go no further.
  This happens whether two-finger or edge scrolling is used.

  Using an actual mouse with a scroll wheel works as expected. Using this in 
conjunction with the touchpad reveals horribly broken behaviour:
  - Clicking on the 'dot' for any of the pages will let the touchpad scroll at 
most one page in either direction, if the mouse is not moved
  - Moving the physical mouse lets the 'momentum' of the touchpad scrolling 
advance the list further as expected.

  Incidentally, the application menu doesn't honour the 'natural scrolling' 
setting for the touchpad in the mouse settings - I will file a separate bug 
report for this but it may be of interest for whoever looks at this.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-11-12 (903 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-30 (3 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

2020-06-30 Thread Dan Ste

After I pressed log out on that screen, I ran journalctl -b 0 and I am
attaching it here. I am not sure if it is different from the previous
one, which was run after a full reboot of the PC.

** Attachment added: "newjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+attachment/5388450/+files/newjournal.txt

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-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/accountsservice/+bug/1885452/+subscriptions

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

Could someone having the issue report it upstream on
https://github.com/brailcom/speechd/issues ?

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

[Desktop-packages] [Bug 1885393] Re: Dark theme

Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Dark theme

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

Bug description:
  Je n'arrive pas à mettre le dark theme avec l'onglet apparence, et je
  ne peut pas changer le theme du shell (pour yaru-dark)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 27 20:35:00 2020
  InstallationDate: Installed on 2019-12-23 (187 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-06-27 (0 days ago)

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

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

[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

2020-06-30 Thread Dan Ste

Unfortunately, after the crash occurs and the 'something went wrong'
screen appears I cannot enter the VT. ctrl-alt-F3 makes the screen go
black and ctrl-alt-f2 reverts is to the 'something went wrong'. I took a
screenshot with PrtSc button but nothing was saved in the Pictures
Folder, but I did take a photo with my camera, just in case. I am
attaching it.

** Attachment added: "IMG_0779.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+attachment/5388449/+files/IMG_0779.jpg

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-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/accountsservice/+bug/1885452/+subscriptions

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

[Desktop-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf

2020-06-30 Thread Erik Auerswald

To test newer versions of evince I have installed evince via the snap
store.

After installation via snap, the snap version can be started using its
different program icon (I hope you can understand what I mean, I clicked
the "9 dots" icon in the bottom of the task bar on the left, typed
"evince", found two versions using different icons, and verified the
version via "Show Details").

* 3.34.2+git4.91cbe4fe (from 2020-06-01) crashes with all the RFC PDF documents 
of this bug and bug #1849888 (which does cast some doubt about that bug being 
fixed in evince version 3.34.1-1).
* 3.36.6+git2.ce03847a (from 2020-06-27) crashes as well.
* 3.37.2+git65.582b220e (from 2020-06-30) does not start, so result for the 
problematic RFC PDFs.

So at least _this_ bug is relevant to more recent versions of evince
than the 18.04 LTS default.

For the default latest/stable channel the snap package shows the
following information:

$ sudo snap info evince
name:  evince
summary:   Document viewer for popular document formats
publisher: Ken VanDine
store-url: https://snapcraft.io/evince
contact:   https://bugs.launchpad.net/ubuntu/+source/evince/+bugs?field.tag=snap
license:   unset
description: |
  This is a document viewer for the GNOME desktop.
  It supports the following document formats: PDF, PS, EPS, XPS, DjVu, TIFF,
  DVI (with SyncTeX), and Comic Books archives (CBR, CBT, CBZ, CB7).
commands:
  - evince
  - evince.evince-previewer
  - evince.evince-thumbnailer
snap-id:  EDFg87ESUg9sAIlm0Vm5Wmr0LjiEonSm
tracking: latest/stable
refresh-date: today at 13:17 CEST
channels:
  latest/stable:3.34.2+git4.91cbe4fe  2020-06-01 (434) 8MB -
  latest/candidate: 3.36.6+git2.ce03847a  2020-06-27 (469) 8MB -
  latest/beta:  ↑  
  latest/edge:  3.37.2+git65.582b220e 2020-06-30 (474) 8MB -
installed:  3.34.2+git4.91cbe4fe (434) 8MB -


** Tags added: bionic snap

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

Title:
  evince crashes when opening rfc8798.pdf

Status in evince package in Ubuntu:
  New
Status in evince package in Debian:
  New

Bug description:
  evince reproducabely crashes when opening the file rfc8798.pdf from
  https://www.rfc-editor.org/rfc/rfc8798.pdf:

  $ evince --version
  GNOME Document Viewer 3.28.4
  $ evince rfc8798.pdf
  Segmentation fault (core dumped)
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

  Required information:

  1) Ubuntu release info:
  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  2) Package version info:
  $ apt-cache policy evince
  evince:
Installed: 3.28.4-0ubuntu1.2
Candidate: 3.28.4-0ubuntu1.2
Version table:
   *** 3.28.4-0ubuntu1.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) Expected outcome:
  I expected evince to successfully open the PDF, allowing me to read the 
document.

  4) Observed behavior:
  The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation 
fault".

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

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

[Desktop-packages] [Bug 1885159] Re: Firefox 78.0 RC hangs at startup on Ubuntu 16.04

2020-06-30 Thread Pascal Mons

Confirming the fix actually works.

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

Title:
  Firefox 78.0 RC hangs at startup on Ubuntu 16.04

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  After latest FF beta update - Firefox doesn't start (also there is no
  crash). In system monitor Firefox process is visible, but still app
  doesn't appear.Starting in safe mode doesn't help.

  Previous version: 77.0.1+build1-0ubuntu0.16.04.1
  Updated version: 78.0+build1-0ubuntu0.16.04.2
  Ubuntu version: Ubuntu 16.04.6 LTS
  Apport bug report attached.

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

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

[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

2020-06-30 Thread Dan Ste

Sorry for numerous messages, but I just did other things. First, I found that
checking at install "request password at logins", I was able to also install
Nvidia Drivers without any issue at all! This change basically solved all the
problems. When installing Ubuntu focal and checking "log in automatically" a
login loop was present after nvidia drivers got installed. LightDM fixed this
as it disables automatic login. Second, I run another journalctl report, this
time instantaneously at crash. Ctrl-alt-F worked by pressing it instantaneously.
Hopefully this may help. I noticed users on askubuntu complaining about login
loops after nvidia drivers install, but have not seen as a solution just to
enable password request at login screen. LightDM partly solves the situations,
but as I mentioned, when LightDM and automatic log in are activated and
accountsservice is being upgraded, the screen still flickers weirdly.

** Attachment added: "instantjournal.txt"

https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+attachment/5388452/+files/instantjournal.txt

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

Title:
pc freezes and crashes during accountsservice upgrade on fresh ubuntu
focal fossa install

Status in accountsservice package in Ubuntu:
Incomplete

Bug description:
After a fresh install of Focal Fossa and running sudo apt update and sudo apt
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes,
then crashes. This was reproducible on another computer (laptop). I reinstalled
Ubuntu and put the package on hold. Later, I found that by installing and
activating lightdm, this problem was remediated. Found this solution
accidentally, while I was looking to correct login screen loops after I
installed the nvidia drivers. This is unrelated, since the laptop does not have
nvidia.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-06-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: accountsservice 0.6.55-0ubuntu12~20.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Tags: focal
Uname: Linux 5.4.0-39-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/accountsservice/+bug/1885452/+subscriptions

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

[Desktop-packages] [Bug 1885669] Re: screen blinking while start laptop

2020-06-30 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  screen blinking while start laptop

Status in xorg package in Ubuntu:
  New

Bug description:
  screen blinking

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 30 11:41:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
  InstallationDate: Installed on 2015-10-17 (1717 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 28 11:49:11 2020
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

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

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

[Desktop-packages] [Bug 1885378] Re: nautillus mounts nfs shares when searching

weird, does it mount if you just 'cd' to the directory on a command line
or use 'ls -R' in the snapshot directory or is it really specific to
nautilus?

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

Title:
  nautillus mounts nfs shares when searching

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a nas running readynas 6, I'm mounting on my pc its nfs shares,
  in fstab they are like

  nas:/data/Documents /media/nas.nfs/Documents nfs4
  async,user,rw,auto,user 0 2

  readynas uses the snapshot folder in its /data/Documents folder in
  order to save the daily backups

  when /media/nas.nfs/Documents is mounted, if I perform a nautilus
  search in that folder I get all the /media/nas.nfs/Documents/snapshot
  and /media/nas.nfs/Documents/snapshot/* folders mounted.

  Once mounted I cannot umount them any more, nor with sudo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 27 15:38:23 2020
  InstallationDate: Installed on 2016-11-23 (1311 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (680 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-30 Thread Bradley Pearce

The problems you are experiencing @mobilebackup and @agwin, are most
likely due to the way the workaround works. Correct me if I am wrong,
but the workaround is asking the graphics system to render a larger
canvas (say 2x, 8K or whatever) and scales this down to the viewport
size. If an application is not enabled for HiDPI mode, they will be
very squished. If you don't have sqaure pixels (like most of us), you
will get bad text, and if you don't check for orientation, the viewport
will break.

The reason I said this is a fab workaround, but won't hold for
production, apart from above, is we are asking the card to render a huge
area. If you move windows around or watch video with GPU decoding, the
card is going to have to move a huge amount of data around.

These are my ramblings, for whatever they are worth.

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

Title:
[nvidia] Screen scaling 125% gives 200%

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

Bug description:
Procedure used:
1.
Fully updated system via apt update && apt upgrade

2.
Select the screen setup in gnome control center

3.
Click the "Fractional scaling" toggle

4.
Select 125% and click the green "use" button top right (it says "Anvend" in
dansih)

5.
Observe that the window has grown a lot, click the "use new settings" button

6.
The window tells me, I am at 200% scaling. The "200%" option is now
highlighted.

7.
Switch back to 100% and file this bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.16
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 09:42:34 2020
InstallationDate: Installed on 2018-01-14 (810 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=da_DK.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

[Desktop-packages] [Bug 1884418] Re: Full text search restricted to some directories

2020-06-30 Thread Adams Jensen

thanks, but still it seems that the problem is a little different,
because searching by file name works.

i am dublicate this issues in GNOME.

https://gitlab.gnome.org/GNOME/nautilus/-/issues/1543

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1543
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/1543

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

Title:
  Full text search restricted to some directories

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Full text search does not work on Ubuntu 20.04

  * Test case
  - install tracker and restart your session
  - echo 'Nautilus is great' > ~/txt
  - open nautilus and type 'great' in the search entry

  version of nautilus 3.36.3-stable

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

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

[Desktop-packages] [Bug 1885669] Re: screen blinking while start laptop

2020-06-30 Thread Daniel van Vugt

Can you please run:

  journalctl -b0 > journal.txt

and attach the resulting text file?

Also a video of the problem would be helpful.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  screen blinking while start laptop

Status in Ubuntu:
  Incomplete

Bug description:
  screen blinking

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 30 11:41:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
  InstallationDate: Installed on 2015-10-17 (1717 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 28 11:49:11 2020
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

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

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

[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

This bug was fixed in the package network-manager - 1.24.2-1ubuntu2

---
network-manager (1.24.2-1ubuntu2) groovy; urgency=medium

  * debian/20-connectivity-ubuntu.conf: Add trailing dot to make
connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN
warning noise, thanks MarchH (lp: #1880258)

 -- Sebastien Bacher   Mon, 29 Jun 2020 16:20:07
+0200

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  
  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes
   
  Now make the hostname absolute with the trailing dot above and run:
 systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

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

[Desktop-packages] [Bug 1885579] Re: cannot add dns nm-applet

Thank you for your bug report. Could you report it upstream on
https://gitlab.gnome.org/GNOME/network-manager-applet/-/issues ?

When is the save button disable? when you start entering a dns or search
domain value?

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

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

Title:
  cannot add dns nm-applet

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

Bug description:
  Hi,

  I am under XUbuntu 20.04, dist-upgraded as of today.

  I have a working Wifi connection using WPA2 Enterprise / PEAP /
  MSCHAPv2.

  Unfortunately, I cannot add a DNS... The "Save" button is greyed-out
  (see attached screen capture)

  Looks similar to this old bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/439956

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

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

[Desktop-packages] [Bug 1860830] Re: Geolocation not working − the Google maps API always returns error codes

2020-06-30 Thread Felagund

Firefox 77.0.1 under Ubuntu 18.04 is still affected. Any news or workarounds on 
this? 
Can we somehow (manually?) override API keys to the ones that don't error out?

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

Title:
  Geolocation not working − the Google maps API always returns error
  codes

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Happened as soon as Firefox was updated to 72.0.1. I noticed sites
  could not determine my location.

  Troubleshooting page shows "missing" under Location service key.

  I have another computer running Lubuntu 18.04LTS, which I rarely use.
  Just for fun, I booted it up and as soon as the software updater
  updated Firefox to 72.0.1, location stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 72.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frank  2125 F pulseaudio
   /dev/snd/controlC1:  frank  2125 F pulseaudio
  BuildID: 20200107212822
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 19:58:30 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-82fc5472-37b3-46d6-a6fa-f47e11180406
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:727
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=72.0.1/20200107212822 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2019-07-05 (203 days ago)
  dmi.bios.date: 03/24/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.27
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1442
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 048D10242B202
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

** Also affects: gnome-control-center (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-435 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal)
   Status: New => Won't Fix

** Tags removed: rls-ff-incoming

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  New
Status in mutter source package in Focal:
  New
Status in nvidia-graphics-drivers-340 source package in Focal:
  New
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  
  When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  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.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2:

[Desktop-packages] [Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin

xxhash promoted to main now

** Changed in: xxhash (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [MIR] teckit & xxhash, new rdeps of texlive-bin

Status in teckit package in Ubuntu:
  Fix Released
Status in xxhash package in Ubuntu:
  Fix Released

Bug description:
  teckit & xxhash, new rdeps of texlive-bin

  teckit was formerly bundled in texlive-bin (I believe)

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

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

[Desktop-packages] [Bug 1864052] Re: gnome-shell crashed with SIGABRT in src/core/window.c:1591:meta_window_unmanage: assertion failed: (g_list_find (workspace->windows, window) == NULL)

** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Confirmed

** Also affects: gnome-shell (Ubuntu Groovy)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Confirmed

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Tags removed: champagne

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

Title:
  gnome-shell crashed with SIGABRT in
  src/core/window.c:1591:meta_window_unmanage: assertion failed:
  (g_list_find (workspace->windows, window) == NULL)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Focal:
  Confirmed
Status in mutter source package in Focal:
  Confirmed
Status in gnome-shell source package in Groovy:
  Confirmed
Status in mutter source package in Groovy:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3e51baba6960038ed185034581cb83e4dd4776e6

  ---

  gnome-shell crashes whenever in CHrome you pop out a video into a
  floating video, or close the floating video (move the video back into
  the main window).

  To test, you can use

  
javascript:document.getElementsByTagName('video')[0].requestPictureInPicture();

  to make a video float on any site, even if the site does not have a
  button for it. I only tested Netflix.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 20 15:36:33 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-03-14 (707 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to focal on 2019-11-25 (87 days ago)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  separator:

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

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

[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

** Tags removed: champagne

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-protocol package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-protocol source package in Focal:
  Incomplete
Status in spice-vdagent source package in Focal:
  Incomplete
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1885378] Re: nautillus mounts nfs shares when searching

Unsure, that's a feature autofs provides
https://help.ubuntu.com/community/Autofs
but you said you don't have that installed...

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

Title:
  nautillus mounts nfs shares when searching

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a nas running readynas 6, I'm mounting on my pc its nfs shares,
  in fstab they are like

  nas:/data/Documents /media/nas.nfs/Documents nfs4
  async,user,rw,auto,user 0 2

  readynas uses the snapshot folder in its /data/Documents folder in
  order to save the daily backups

  when /media/nas.nfs/Documents is mounted, if I perform a nautilus
  search in that folder I get all the /media/nas.nfs/Documents/snapshot
  and /media/nas.nfs/Documents/snapshot/* folders mounted.

  Once mounted I cannot umount them any more, nor with sudo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 27 15:38:23 2020
  InstallationDate: Installed on 2016-11-23 (1311 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (680 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

2020-06-30 Thread Hui Wang

It is a bit helpful on this bug if we could merge the fix of gnome-
control-center first, without the fix of gcc, suppose users manually
select the preferred input device, the system will not store user's
selection, but after applying the fix of gcc, the system could store the
user's selection.

So the fix of gcc could partially fix this bug (after freshly installing
the OS, need users to manually select the input device once). After
those all 3 fixes are merged, the auto selection could work out-of-box,
no need the users manually to select anymore.

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Step to reproduce:

  1. plug-in headset
  2. select headset in pop-up window.
  3. check g-c-c

  Expected result:
correct input is selected so that mic on the headset just works

  Actual result:
The correct input is not selected.

  a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

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

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

[Desktop-packages] [Bug 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs

I’m not sure if depending on a library and -common (the initial apt log
shows the client and server themselves were *not* installed) is a
particular problem, but if so, this is coming from libsnmp35.

** Package changed: ubuntu-meta (Ubuntu) => net-snmp (Ubuntu)

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

Title:
  ubuntu-desktop-minimal should not depend on mysql libs

Status in net-snmp package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 20.04 I decided to remove packages that I don't
  need or use.

  I was surprised to find that mysql client, server and common packages
  were installed, as I could not remember having installed mysql -- I
  don't use it or develop for it...

  When I removed them, ubuntu-desktop-minimal went along for the ride:

  c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common 
mysql-server-core-5.7 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'mysql-client-core-5.7' is not installed, so not removed
  Package 'mysql-server-core-5.7' is not installed, so not removed
  The following package was automatically installed and is no longer required:
libgsound0
  Use 'sudo apt autoremove' to remove it.
  The following packages will be REMOVED:
colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* 
mysql-common* ubuntu-desktop-minimal*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 28.4 MB disk space will be freed.
  (Reading database ... 381127 files and directories currently installed.)
  Removing ubuntu-desktop-minimal (1.443) ...
  Removing gnome-control-center (1:3.34.1-1ubuntu3) ...
  Removing colord (1.4.4-1ubuntu1) ...
  Removing libsane:amd64 (1.0.27-3.2ubuntu3) ...
  Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ...
  Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ...
  Removing mysql-common (5.8+1.0.5ubuntu2) ...
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ...
  Processing triggers for libc-bin (2.30-0ubuntu3) ...
  Processing triggers for man-db (2.9.0-2) ...
  Processing triggers for dbus (1.12.16-2ubuntu2) ...
  Processing triggers for udev (244-3ubuntu1) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
  (Reading database ... 380812 files and directories currently installed.)
  Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ...
  Purging configuration files for colord (1.4.4-1ubuntu1) ...

  And, reinstalling ubuntu-desktop-minimal wants to brings them back,
  even with recommends and suggests turned off:

  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-
  --no-install-recommends  --no-install-suggests
  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-suggests 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common
  Suggested packages:
colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip
  Recommended packages:
gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker 
sane-utils firefox hplip
  The following NEW packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common 
ubuntu-desktop-minimal
  0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/6,114 kB of archives.
  After this operation, 28.4 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 

  This seems really wrong... and looks like a transitive dependency, as
  I don't see it in apt-get showpkg ubuntu-desktop-minimal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop-minimal 1.443
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux 
ashmem_linux
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 19:26:53 2020
  InstallationDate: Installed on 2018-08-26 (514 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1885378] Re: nautillus mounts nfs shares when searching

2020-06-30 Thread Paolo Benvenuto

actually, cd'ing into the directories mount them, so it's not nautilus

But, then, who could be mounting them?

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

Title:
  nautillus mounts nfs shares when searching

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a nas running readynas 6, I'm mounting on my pc its nfs shares,
  in fstab they are like

  nas:/data/Documents /media/nas.nfs/Documents nfs4
  async,user,rw,auto,user 0 2

  readynas uses the snapshot folder in its /data/Documents folder in
  order to save the daily backups

  when /media/nas.nfs/Documents is mounted, if I perform a nautilus
  search in that folder I get all the /media/nas.nfs/Documents/snapshot
  and /media/nas.nfs/Documents/snapshot/* folders mounted.

  Once mounted I cannot umount them any more, nor with sudo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 27 15:38:23 2020
  InstallationDate: Installed on 2016-11-23 (1311 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (680 days ago)
  usr_lib_nautilus:

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

-- 
Mailing list: https://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 1885330] Re: System unresponsive to keyboard and mouse clicks when changing screen background

2020-06-30 Thread Lester Potter

"pidof gnome-shell" reports the same PID before and after.

On Mon, Jun 29, 2020 at 10:35 PM Daniel van Vugt <1885...@bugs.launchpad.net>
wrote:

> If the mouse cursor still moves then that means Xorg is still running
> and it was gnome-shell frozen. But we need to find out if it was just
> frozen or the result of a crash. Please use this command:
>
>   pidof gnome-shell
>
> to check the process ID before and after the freeze and tell us if it
> changes.
>
> Also immediately after the next freeze please run:
>
>   journalctl -b0 > post-freeze.txt
>
> and attach the resulting text file here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1885330
>
> Title:
>   System unresponsive to keyboard and mouse clicks when changing screen
>   background
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Right click on screen background and choose settings.
>   Then click a different background.
>   System becomes unresponsive to keyboard input and mouse clicks.
>   System returns to responsiveness after about 10 minutes.
>
>   Description:  Ubuntu 20.04 LTS
>   Release:  20.04
>
>   CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
>   Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
>   Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38
>
>   Expected behavior:
>   Changing the background happens immediately and system remains
> responsive to input.
>
>   What happened:
>   System did not change the background immediately and became unresponsive
> to keyboard and mouse input for 10 minutes at which point the background
> changed to the selected one and responsiveness returned.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-control-center 1:3.36.2-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
>   Uname: Linux 5.4.0-37-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.3
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Jun 26 15:50:44 2020
>   ExecutablePath: /usr/bin/gnome-control-center
>   InstallationDate: Installed on 2020-06-13 (13 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-control-center
>   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/1885330/+subscriptions
>

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

Title:
  System unresponsive to keyboard and mouse clicks when changing screen
  background

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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/1885330/+subscriptions

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

[Desktop-packages] [Bug 1880710] Re: [snap] Tab goes blank even after reloads (and no refresh is happening)

2020-06-30 Thread Natalia Bidart

A week later and Chrome from the .deb has never presented this blank-tab
issue.

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

Title:
  [snap] Tab goes blank even after reloads (and no refresh is happening)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Using chromium from stable:

  installed:  83.0.4103.61(1165) 163MB

  after a few hours of having it opened, some tabs started showing a
  blank page (google spreadsheets, google calendar). Even after hitting
  F5 or hard reloads, the browser will show the content is being re-
  fetched, but nothing is rendered.

  This is happening while chromium is NOT being refreshed:

  nessita@dali:~$ snap changes
  ID   Status  Spawn   Ready   Summary
  125  Doneyesterday at 12:09 -03  yesterday at 12:09 -03  Auto-refresh 
snap "lxd"

  nessita@dali:~$

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

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

[Desktop-packages] [Bug 1885330] Re: System unresponsive to keyboard and mouse clicks when changing screen background

2020-06-30 Thread Lester Potter

Here is the journalctl report.
Line 3144 is immediately prior to hanging GNOME.

** Attachment added: "post-freeze.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885330/+attachment/5388456/+files/post-freeze.txt

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

Title:
  System unresponsive to keyboard and mouse clicks when changing screen
  background

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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/1885330/+subscriptions

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

[Desktop-packages] [Bug 1880710] Re: [snap] Tab goes blank even after reloads (and no refresh is happening)

Thanks for the heads up Natalia. So that's definitely a snap-specific
issue.

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

Title:
  [snap] Tab goes blank even after reloads (and no refresh is happening)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Using chromium from stable:

  installed:  83.0.4103.61(1165) 163MB

  after a few hours of having it opened, some tabs started showing a
  blank page (google spreadsheets, google calendar). Even after hitting
  F5 or hard reloads, the browser will show the content is being re-
  fetched, but nothing is rendered.

  This is happening while chromium is NOT being refreshed:

  nessita@dali:~$ snap changes
  ID   Status  Spawn   Ready   Summary
  125  Doneyesterday at 12:09 -03  yesterday at 12:09 -03  Auto-refresh 
snap "lxd"

  nessita@dali:~$

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

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

[Desktop-packages] [Bug 1860830] Re: Geolocation not working − the Google maps API always returns error codes

2020-06-30 Thread Vadim Evard

Upd: you can indeed override the API key in about:config.
To find a value that works, download Firefox from mozilla.org, extract the 
archive, and run

grep --binary-files=text MOZ_GOOGLE_LOCATION_SERVICE_API_KEY omni.ja

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

Title:
  Geolocation not working − the Google maps API always returns error
  codes

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Happened as soon as Firefox was updated to 72.0.1. I noticed sites
  could not determine my location.

  Troubleshooting page shows "missing" under Location service key.

  I have another computer running Lubuntu 18.04LTS, which I rarely use.
  Just for fun, I booted it up and as soon as the software updater
  updated Firefox to 72.0.1, location stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 72.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frank  2125 F pulseaudio
   /dev/snd/controlC1:  frank  2125 F pulseaudio
  BuildID: 20200107212822
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 19:58:30 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-82fc5472-37b3-46d6-a6fa-f47e11180406
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:727
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=72.0.1/20200107212822 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2019-07-05 (203 days ago)
  dmi.bios.date: 03/24/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.27
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1442
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 048D10242B202
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1885743] Re: Search plugins need to be updated for browser.search.modernConfig=true

** Branch linked: lp:firefox

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

Title:
  Search plugins need to be updated for browser.search.modernConfig=true

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  In firefox 78.0, the browser.search.modernConfig setting defaults to
  true, and as a result the custom definitions installed in
  /usr/lib/firefox/distribution/searchplugins/locale/ by langpacks are
  not loaded.

  The upstream meta-bug that tracks this new modern search engine
  configuration is https://bugzilla.mozilla.org/show_bug.cgi?id=1542235.

  The setting can be reverted back to false for the 78.0 builds, but
  eventually the setting will go away
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1619926), so the custom
  definitions need to be updated.

  Relevant upstream documentation: https://hg.mozilla.org/mozilla-
  central/file/tip/toolkit/components/search/docs/SearchEngineConfiguration.rst

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

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

[Desktop-packages] [Bug 1885743] Re: Search plugins need to be updated for browser.search.modernConfig=true

Temporarily reverted the setting to false for 78.0:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.groovy/revision/1405

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

Title:
  Search plugins need to be updated for browser.search.modernConfig=true

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  In firefox 78.0, the browser.search.modernConfig setting defaults to
  true, and as a result the custom definitions installed in
  /usr/lib/firefox/distribution/searchplugins/locale/ by langpacks are
  not loaded.

  The upstream meta-bug that tracks this new modern search engine
  configuration is https://bugzilla.mozilla.org/show_bug.cgi?id=1542235.

  The setting can be reverted back to false for the 78.0 builds, but
  eventually the setting will go away
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1619926), so the custom
  definitions need to be updated.

  Relevant upstream documentation: https://hg.mozilla.org/mozilla-
  central/file/tip/toolkit/components/search/docs/SearchEngineConfiguration.rst

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

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

[Desktop-packages] [Bug 1828728] Re: White corners when CSD is enabled on Firefox under X11

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  White corners when CSD is enabled on Firefox under X11

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

Bug description:
  With CSD enabled, Firefox 66.0.4 displays white corners at the top-
  left and top-right of the window.

  Ubuntu version: 19.04 (fully updated)
  Version: Firefox 66.0.4 (64-bits)
  Desktop Environment: GNOME 3.32.1 (default)
  GTK theme: Yaru (default)
  GPU: Radeon RX 560 Series (POLARIS11, DRM 3.27.0, 5.0.0-13-generic, LLVM 
8.0.0)

  Expected behavior: rounded corners without the white corners,
  following the current theme.

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

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

[Desktop-packages] [Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.

2020-06-30 Thread Andreas Hasenack

When you manually connect, by typing in the full smb url, it doesn't
mean SMB1 is being used. You can verify that by running "sudo smbstatus"
on the server.

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

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

Title:
  Nautilus requires SMBv1 to work from "Other Locations" without
  manually typing in the address.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Navigate to Other Locations.  Your SMB share should show here.
  Clicking on the share will cause an error "Unable to access location;
  Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
  connecting by typing in the address still works.

  SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
  fully deprecate SMBv1 by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  2 11:41:18 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-10-13 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.

2020-06-30 Thread Eduardo Barretto

Hi @ahasenack, @seb128

I saw you've both have dealt with smb issues.
Could you please take a look on this issue?

Thanks!

** Information type changed from Private Security to Public Security

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

Title:
  Nautilus requires SMBv1 to work from "Other Locations" without
  manually typing in the address.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Navigate to Other Locations.  Your SMB share should show here.
  Clicking on the share will cause an error "Unable to access location;
  Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
  connecting by typing in the address still works.

  SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
  fully deprecate SMBv1 by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  2 11:41:18 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-10-13 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.

2020-06-30 Thread Andreas Hasenack

Ah, I think I see what you mean. Nautilus (gvfs actually) is temporarily
downgrading the protocol for the discovery, but it's not reverting that
when trying to actually connect to a discovered host. Is that it?

This does ring a bell, it was supposed to be fixed with an SRU on
bionic, and in the development release back then. That SRU is what
enabled this temporary fallback to smbv1 while doing discovery, and
reverted when connecting.

This needs troubleshooting.


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

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

Title:
  Nautilus requires SMBv1 to work from "Other Locations" without
  manually typing in the address.

Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Navigate to Other Locations.  Your SMB share should show here.
  Clicking on the share will cause an error "Unable to access location;
  Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
  connecting by typing in the address still works.

  SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
  fully deprecate SMBv1 by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  2 11:41:18 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-10-13 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1885610] Re: enlarged components on lock/login screen

2020-06-30 Thread Relly Valentine

Yes this problem still occurs after disabling the user-theme extension

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

Title:
  enlarged components on lock/login screen

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

Bug description:
  Source Package: usr/bin/gnome-shell
  Ubuntu Release: 20.04 LTS
  Package Version: 3.36.2-1ubuntu1~20.04.1
  Expected: Normal sized components on lock/login screen
  Happened: Enlarged components on lock/login screen

  This behavior is unaffected by resolution size from different monitors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Flat-Remix-Miami-Dark-GNOME:GNOME
  Date: Mon Jun 29 13:01:06 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-02 (331 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-06-27 (2 days ago)

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

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

[Desktop-packages] [Bug 1672139]

2020-06-30 Thread Robert Townley

Mark Banner,

why change the status from "affected"?  Maybe I not remembering what
"---" means in this context.

I am on Firefox 77.

CTRL+SHIFT+O and perform a search.  Hundreds of results returned that
need to be grouped together better.  But cannot right click on any
bookmark to find where it is currently located.  So how is not
"affected"?

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

Title:
  Add "Open Enclosing Folder" context menu to search results of
  bookmarks in the Library window (link to view/open containing folder,
  parent folder button)

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

Bug description:
  Firefox is great. It has bookmarks.
  But it is impossible to open bookmark's folder in search results.

  Steps to reproduce:
  1. Open Firefox
  2. Open its Bookmark Manager ()
  3. Search for bookmark
  4. Try to find its folder with right-click menu.
  5. It is impossible to find bookmark's folder.

  Expected results:
  Firefox is mature, so it is expected that user can find bookmark's folder. 
For example Google Chrome has "Show in folder" menu option.

  Note: original bug was reported 8 years ago, but it is not fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 52.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-110-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay8420 F pulseaudio
  BuildID: 20170303013352
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,10431507,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Channel: Unavailable
  Date: Sun Mar 12 13:59:45 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  IpRoute:
   default via 192.168.3.1 dev wlan3  proto static 
   169.254.0.0/16 dev wlan3  scope link  metric 1000 
   192.168.3.0/24 dev wlan3  proto kernel  scope link  src 192.168.3.6  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
   [Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
   
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
   
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
  Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1880710] Re: [snap] Tab goes blank even after reloads (and no refresh is happening)

2020-06-30 Thread Natalia Bidart

Would it be useful for debugging purposes if I switch back to the
Chromium snap?

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

Title:
  [snap] Tab goes blank even after reloads (and no refresh is happening)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Using chromium from stable:

  installed:  83.0.4103.61(1165) 163MB

  after a few hours of having it opened, some tabs started showing a
  blank page (google spreadsheets, google calendar). Even after hitting
  F5 or hard reloads, the browser will show the content is being re-
  fetched, but nothing is rendered.

  This is happening while chromium is NOT being refreshed:

  nessita@dali:~$ snap changes
  ID   Status  Spawn   Ready   Summary
  125  Doneyesterday at 12:09 -03  yesterday at 12:09 -03  Auto-refresh 
snap "lxd"

  nessita@dali:~$

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

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

[Desktop-packages] [Bug 1885330] Re: System unresponsive to keyboard and mouse clicks when changing screen background

2020-06-30 Thread Lester Potter

Additional info...

Upon invoking the freeze, Ctl-Alt-F3 sometimes brings up a terminal session on 
tty3.
If it does, Ctl-Alt-F2 will switch back to GNOME which will remain frozen for a 
while, but will allow switching back and forth with the Ctl-Alt-F# keys.

Running "top" on tty3 shows no processes taking much %CPU.
Observed a message "[TTM] Buffer eviction failed" 3 times (on tty3) while 
waiting for unfreeze.

Sometimes, Ctl-Alt-F3 is also unresponsive upon freeze, but did
eventually switch to tty3 (after a about 20 seconds).  This hasn't been
tested much yet.

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

Title:
  System unresponsive to keyboard and mouse clicks when changing screen
  background

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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/1885330/+subscriptions

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

[Desktop-packages] [Bug 1885743] [NEW] Search plugins need to be updated for browser.search.modernConfig=true

Public bug reported:

In firefox 78.0, the browser.search.modernConfig setting defaults to
true, and as a result the custom definitions installed in
/usr/lib/firefox/distribution/searchplugins/locale/ by langpacks are not
loaded.

The upstream meta-bug that tracks this new modern search engine
configuration is https://bugzilla.mozilla.org/show_bug.cgi?id=1542235.

The setting can be reverted back to false for the 78.0 builds, but
eventually the setting will go away
(https://bugzilla.mozilla.org/show_bug.cgi?id=1619926), so the custom
definitions need to be updated.

Relevant upstream documentation: https://hg.mozilla.org/mozilla-
central/file/tip/toolkit/components/search/docs/SearchEngineConfiguration.rst

** Affects: firefox (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged

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

Title:
  Search plugins need to be updated for browser.search.modernConfig=true

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  In firefox 78.0, the browser.search.modernConfig setting defaults to
  true, and as a result the custom definitions installed in
  /usr/lib/firefox/distribution/searchplugins/locale/ by langpacks are
  not loaded.

  The upstream meta-bug that tracks this new modern search engine
  configuration is https://bugzilla.mozilla.org/show_bug.cgi?id=1542235.

  The setting can be reverted back to false for the 78.0 builds, but
  eventually the setting will go away
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1619926), so the custom
  definitions need to be updated.

  Relevant upstream documentation: https://hg.mozilla.org/mozilla-
  central/file/tip/toolkit/components/search/docs/SearchEngineConfiguration.rst

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

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

[Desktop-packages] [Bug 1885748] Re: firefox white corners, broken theming

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

** This bug has been marked a duplicate of bug 1828728
   White corners when CSD is enabled on Firefox under X11

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

Title:
  firefox white corners, broken theming

Status in firefox package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  firefox:
Installed: 77.0.1+build1-0ubuntu0.20.04.1
Candidate: 77.0.1+build1-0ubuntu0.20.04.1
Version table:
   *** 77.0.1+build1-0ubuntu0.20.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3)
  I expected the default browser to follow the theming of the rest of the OS.

  4)
  Title bar enabled and white corners on the top rounded edges.

  The default configuration of Firefox is broken by default for some
  reason.

  The issue is futher defined and can be fixed by following this guide:
  https://www.omgubuntu.co.uk/2020/04/fix-firefox-rounded-corners-gnome

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

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

[Desktop-packages] [Bug 1885744] Re: HIde im-config in application menus/searches

2020-06-30 Thread Gunnar Hjalmarsson

** Description changed:

+ [Impact]
+ 
  I'm refering to this conversation:
  
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2
  
  Current situation:
  ===
  - Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
  - im-config is difficult to understand for "normal users"
  
- 
  Suggestion:
  ===
  Hide im-config from application menu / searches
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: im-config 0.44-1ubuntu1
- ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
- Uname: Linux 5.4.0-39-generic x86_64
- ApportVersion: 2.20.11-0ubuntu27.3
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDesktop: ubuntu:GNOME
- Date: Wed Jul  1 00:33:17 2020
- InstallationDate: Installed on 2020-06-29 (1 days ago)
- InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
- PackageArchitecture: all
- SourcePackage: im-config
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [Test Case]
+ 
+ * Open Activities and find that "Input Method" is found
+ 
+ * Install im-config from focal-proposed
+ 
+ * Open Activities and find that "Input Method" is no longer found
+ 
+ [Regression Potential]
+ 
+ Minimal; only a tiny change in the .desktop file.

** Also affects: im-config (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: im-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu)
   Status: New => Fix Committed

** Changed in: im-config (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: im-config (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu Focal)
   Status: New => In Progress

** Changed in: im-config (Ubuntu Focal)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  HIde im-config in application menus/searches

Status in im-config package in Ubuntu:
  Fix Committed
Status in im-config source package in Focal:
  In Progress

Bug description:
  [Impact]

  I'm refering to this conversation:
  
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2

  Current situation:
  ===
  - Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
  - im-config is difficult to understand for "normal users"

  Suggestion:
  ===
  Hide im-config from application menu / searches

  [Test Case]

  * Open Activities and find that "Input Method" is found

  * Install im-config from focal-proposed

  * Open Activities and find that "Input Method" is no longer found

  [Regression Potential]

  Minimal; only a tiny change in the .desktop file.

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-30 Thread David

@blitmaps I think its not as simple as that. It seems that the current
state of things, (I'm on a 4k) - I am not even talking about hidpi mode
supporting applications - even Gnome acts wierd. For example there is no
reason for the titlebar font not to update in size?

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1885749] Re: Enhancement: Remove default Emoji shortcuts

2020-06-30 Thread Gunnar Hjalmarsson

Thanks for your report.

The conflict you point at is unfortunate. Nevertheless, removing those
shortcuts is not an option. Especially Ctrl+Shift+u is a well
established method on Linux to type characters which are not available
via the keyboard layout you are using:

https://help.ubuntu.com/stable/ubuntu-help/tips-
specialchars.html#ctrlshiftu

Ctrl+Shift+e is newer, but probably used and appreciated by many users.

Your bug makes me think of this IBus issue:

https://github.com/ibus/ibus/issues/2163

That proved to be an Ubuntu specific bug which has been fixed in groovy
but not (yet) in focal. Fixing it in focal would be a way to improve the
situation. If you want that to happen, please file an ibus bug as I
suggested in my latest comment at that issue.

I think you make a too big deal of the fact that ibus-setup is not
searchable in Ubuntu. It's not an Ubuntu specific thing, btw, but it's
the same for GNOME irrespective of distro:

https://github.com/ibus/ibus/commit/66141bbc

Alt+F2 followed by ibus-setup is not "extremely difficult". But indeed,
you need be aware of the possibility to change it that way.

** Bug watch added: github.com/ibus/ibus/issues #2163
   https://github.com/ibus/ibus/issues/2163

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  New

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1885743] Re: Search plugins need to be updated for browser.search.modernConfig=true

** Branch linked: lp:~mozillateam/firefox/firefox.xenial

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

Title:
  Search plugins need to be updated for browser.search.modernConfig=true

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  In firefox 78.0, the browser.search.modernConfig setting defaults to
  true, and as a result the custom definitions installed in
  /usr/lib/firefox/distribution/searchplugins/locale/ by langpacks are
  not loaded.

  The upstream meta-bug that tracks this new modern search engine
  configuration is https://bugzilla.mozilla.org/show_bug.cgi?id=1542235.

  The setting can be reverted back to false for the 78.0 builds, but
  eventually the setting will go away
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1619926), so the custom
  definitions need to be updated.

  Relevant upstream documentation: https://hg.mozilla.org/mozilla-
  central/file/tip/toolkit/components/search/docs/SearchEngineConfiguration.rst

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

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

[Desktop-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar

I think I got a better picture. Thank you very much for your help!

I set this bug to Invalid.
I filed a new bug explicitly going after the shortcut settings in Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885749

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

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

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

[Desktop-packages] [Bug 1885748] [NEW] firefox white corners, broken theming

2020-06-30 Thread Robert Harrington

Public bug reported:

1)
Description:Ubuntu 20.04 LTS
Release:20.04

2)
firefox:
  Installed: 77.0.1+build1-0ubuntu0.20.04.1
  Candidate: 77.0.1+build1-0ubuntu0.20.04.1
  Version table:
 *** 77.0.1+build1-0ubuntu0.20.04.1 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
 75.0+build3-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

3)
I expected the default browser to follow the theming of the rest of the OS.

4)
Title bar enabled and white corners on the top rounded edges.

The default configuration of Firefox is broken by default for some
reason.

The issue is futher defined and can be fixed by following this guide:
https://www.omgubuntu.co.uk/2020/04/fix-firefox-rounded-corners-gnome

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


** Tags: firefox gnome theming

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

Title:
  firefox white corners, broken theming

Status in firefox package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  firefox:
Installed: 77.0.1+build1-0ubuntu0.20.04.1
Candidate: 77.0.1+build1-0ubuntu0.20.04.1
Version table:
   *** 77.0.1+build1-0ubuntu0.20.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   75.0+build3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3)
  I expected the default browser to follow the theming of the rest of the OS.

  4)
  Title bar enabled and white corners on the top rounded edges.

  The default configuration of Firefox is broken by default for some
  reason.

  The issue is futher defined and can be fixed by following this guide:
  https://www.omgubuntu.co.uk/2020/04/fix-firefox-rounded-corners-gnome

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

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

[Desktop-packages] [Bug 1884453] Re: Firefox, input-language-changing shortcut issue

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

Indeed you already reported this issue as bug #1843817 (marking as
duplicate).

Note: a useful link to see all the bugs that you filed:
https://bugs.launchpad.net/~gix-d/+reportedbugs.

** This bug has been marked a duplicate of bug 1843817
   Changing input method on webpages requires pressing twice the hotkey

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

Title:
  Firefox, input-language-changing shortcut issue

Status in firefox package in Ubuntu:
  New

Bug description:
  (First of all, I believe I reported a few times the similar issue
  before, but I couldn't find the old posts, so apologize if people find
  this repeating.)

  The bug is that I need to hit input-language-changing shortcut
  (ctrl+space) "twice" and "quickly" to trigger the change in boxes on
  webpages. I am using GCIN 2.9.0. There's no problem for changing input
  in URL or search boxes on the Firefox UI frame that are outside the
  webpages; I can hit ctrl+space once and it works. On the webpages, not
  just that I need to hit the shortcut twice, but the hits need to be
  sufficiently back-to-back, like less than a second. This issue also
  doesn't exist in Chrome.

  Thank you very much for the help!

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 77.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yenyung_chang   1740 F pulseaudio
  BuildID: 2020060727
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 09:11:12 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-03-26 (453 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.112 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:734
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=77.0.1/2020060727 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd02/04/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1065126]

2020-06-30 Thread Thomas-dallagnese-b

(In reply to monperrus from comment #150)
> For the record, addon "InlineDisposition (WebExtensions)" is still a valid 
> workaround: 
> https://addons.mozilla.org/en-US/firefox/addon/inlinedisposition-webexts/

InlineDispotition didn't work for me, but the more recent Display Inline
one worked (https://addons.mozilla.org/en-GB/firefox/addon/display-
inline/)

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

Title:
  "Always do this from now on" does not work

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Downloading an unknown file type in Firefox displays a dialog for choosing 
which application to use for opening the file.
  The dialog contains a check box labelled "Always do this action from now on".
  Checking this option does not work: When I download a file of the same type 
next time, the same dialog is displayed again.

  This feature is broken for as long as I can remember (> 10 years).
  It's time it was fixed (or removed).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 15.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruediger   2536 F pulseaudio
  BuildID: 20120907231657
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49'
     Mixer name : 'Analog Devices AD1984'
     Components : 'HDA:11d41984,17aa20bb,00100400'
     Controls  : 32
     Simple ctrls  : 20
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.08'
     Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Channel: Unavailable
  Date: Wed Oct 10 18:17:44 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 172.31.0.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   172.31.0.0/20 dev wlan0  proto kernel  scope link  src 172.31.9.26  metric 2
  MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu4.2
   totem-mozilla 3.0.1-0ubuntu21.1
   icedtea-6-plugin  1.2-2ubuntu1.2
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 6457BBG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6457BBG
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1885744] [NEW] HIde im-config in application menus/searches

Public bug reported:

I'm refering to this conversation:
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2

Current situation:
===
- Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
- im-config is difficult to understand for "normal users"


Suggestion:
===
Hide im-config from application menu / searches

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: im-config 0.44-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  1 00:33:17 2020
InstallationDate: Installed on 2020-06-29 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: im-config
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: im-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  HIde im-config in application menus/searches

Status in im-config package in Ubuntu:
  New

Bug description:
  I'm refering to this conversation:
  
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2

  Current situation:
  ===
  - Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
  - im-config is difficult to understand for "normal users"

  
  Suggestion:
  ===
  Hide im-config from application menu / searches

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: im-config 0.44-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:33:17 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.

2020-06-30 Thread Jon

Logically this seems to be correct. I’m not a samba developer, so I don’t
have direct insights to what is happening when.  I don’t know much about
the samba discovery process.

The easy way to test this is startup FreeNAS in a VM because they disable
SMBv1 by default.

On Tue, Jun 30, 2020 at 2:05 PM Andreas Hasenack <1881...@bugs.launchpad.net>
wrote:

> Ah, I think I see what you mean. Nautilus (gvfs actually) is temporarily
> downgrading the protocol for the discovery, but it's not reverting that
> when trying to actually connect to a discovered host. Is that it?
>
> This does ring a bell, it was supposed to be fixed with an SRU on
> bionic, and in the development release back then. That SRU is what
> enabled this temporary fallback to smbv1 while doing discovery, and
> reverted when connecting.
>
> This needs troubleshooting.
>
>
> ** Also affects: gvfs (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1881780
>
> Title:
>   Nautilus requires SMBv1 to work from "Other Locations" without
>   manually typing in the address.
>
> Status in gvfs package in Ubuntu:
>   New
> Status in nautilus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Navigate to Other Locations.  Your SMB share should show here.
>   Clicking on the share will cause an error "Unable to access location;
>   Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
>   connecting by typing in the address still works.
>
>   SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
>   fully deprecate SMBv1 by default.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: nautilus 1:3.36.1.1-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
>   Uname: Linux 5.4.0-33-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27.2
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Tue Jun  2 11:41:18 2020
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2019-10-13 (232 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: nautilus
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1881780/+subscriptions
>

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

Title:
  Nautilus requires SMBv1 to work from "Other Locations" without
  manually typing in the address.

Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Navigate to Other Locations.  Your SMB share should show here.
  Clicking on the share will cause an error "Unable to access location;
  Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
  connecting by typing in the address still works.

  SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
  fully deprecate SMBv1 by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  2 11:41:18 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-10-13 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1884803] Re: SRU the current 3.36.2 stable update

Hello Sebastien, or anyone else affected,

Accepted gnome-calendar into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
calendar/3.36.2-0ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-calendar (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.2 stable update

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that calendar editing works. Add an online account (google for
  example) is settings and see that the local calendar is correctly
  listing the events. Check that events are listed in the GNOME
  indicator

  * Regression potential

  The are some changes are start of week and event time calculation,
  make sure all day events are on right days and that timed events are
  correctly displayed

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

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

[Desktop-packages] [Bug 1672139]

2020-06-30 Thread Standard8

(In reply to Robert Townley from comment #46)
> why change the status from "affected"?  Maybe I not remembering what "---" 
> means in this context.  

"---" means we're not specifically tracking it for a particular release.
This bug is open and that is enough to record that it is still an issue.
It is not currently a priority for us as there are many other things
that we are working on (See also comment 41).

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

Title:
  Add "Open Enclosing Folder" context menu to search results of
  bookmarks in the Library window (link to view/open containing folder,
  parent folder button)

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

Bug description:
  Firefox is great. It has bookmarks.
  But it is impossible to open bookmark's folder in search results.

  Steps to reproduce:
  1. Open Firefox
  2. Open its Bookmark Manager ()
  3. Search for bookmark
  4. Try to find its folder with right-click menu.
  5. It is impossible to find bookmark's folder.

  Expected results:
  Firefox is mature, so it is expected that user can find bookmark's folder. 
For example Google Chrome has "Show in folder" menu option.

  Note: original bug was reported 8 years ago, but it is not fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 52.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-110-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay8420 F pulseaudio
  BuildID: 20170303013352
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,10431507,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Channel: Unavailable
  Date: Sun Mar 12 13:59:45 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  IpRoute:
   default via 192.168.3.1 dev wlan3  proto static 
   169.254.0.0/16 dev wlan3  scope link  metric 1000 
   192.168.3.0/24 dev wlan3  proto kernel  scope link  src 192.168.3.6  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
   [Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
   
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
   
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
  Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1672139]

2020-06-30 Thread Lina-8

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

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

Title:
  Add "Open Enclosing Folder" context menu to search results of
  bookmarks in the Library window (link to view/open containing folder,
  parent folder button)

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

Bug description:
  Firefox is great. It has bookmarks.
  But it is impossible to open bookmark's folder in search results.

  Steps to reproduce:
  1. Open Firefox
  2. Open its Bookmark Manager ()
  3. Search for bookmark
  4. Try to find its folder with right-click menu.
  5. It is impossible to find bookmark's folder.

  Expected results:
  Firefox is mature, so it is expected that user can find bookmark's folder. 
For example Google Chrome has "Show in folder" menu option.

  Note: original bug was reported 8 years ago, but it is not fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 52.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-110-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikolay8420 F pulseaudio
  BuildID: 20170303013352
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,10431507,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Channel: Unavailable
  Date: Sun Mar 12 13:59:45 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  IpRoute:
   default via 192.168.3.1 dev wlan3  proto static 
   169.254.0.0/16 dev wlan3  scope link  metric 1000 
   192.168.3.0/24 dev wlan3  proto kernel  scope link  src 192.168.3.6  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
   [Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
   
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
   
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
  Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar

** Changed in: ibus (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

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

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

[Desktop-packages] [Bug 1885743] Re: Search plugins need to be updated for browser.search.modernConfig=true

** Branch linked: lp:~mozillateam/firefox/firefox.bionic

** Branch linked: lp:~mozillateam/firefox/firefox.eoan

** Branch linked: lp:~mozillateam/firefox/firefox.focal

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

Title:
  Search plugins need to be updated for browser.search.modernConfig=true

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  In firefox 78.0, the browser.search.modernConfig setting defaults to
  true, and as a result the custom definitions installed in
  /usr/lib/firefox/distribution/searchplugins/locale/ by langpacks are
  not loaded.

  The upstream meta-bug that tracks this new modern search engine
  configuration is https://bugzilla.mozilla.org/show_bug.cgi?id=1542235.

  The setting can be reverted back to false for the 78.0 builds, but
  eventually the setting will go away
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1619926), so the custom
  definitions need to be updated.

  Relevant upstream documentation: https://hg.mozilla.org/mozilla-
  central/file/tip/toolkit/components/search/docs/SearchEngineConfiguration.rst

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

-- 
Mailing list: https://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 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.

2020-06-30 Thread Jon

No but when you use the automatic detection of smb services which I’m
guessing uses NetBios or something like that it won’t connect if SMBv1 is
disabled.

So simply navigating to Other Locations and clicking on the automatically
enumerated host names, the connection will completely fail if SMBv1 is
disabled.  This might be related to samba directly because the same thing
happens in VLC.

The current workaround is to manually specify the URL to connect to the
desired share.

On Tue, Jun 30, 2020 at 1:35 PM Andreas Hasenack <1881...@bugs.launchpad.net>
wrote:

> When you manually connect, by typing in the full smb url, it doesn't
> mean SMB1 is being used. You can verify that by running "sudo smbstatus"
> on the server.
>
> ** Changed in: nautilus (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1881780
>
> Title:
>   Nautilus requires SMBv1 to work from "Other Locations" without
>   manually typing in the address.
>
> Status in nautilus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Navigate to Other Locations.  Your SMB share should show here.
>   Clicking on the share will cause an error "Unable to access location;
>   Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
>   connecting by typing in the address still works.
>
>   SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
>   fully deprecate SMBv1 by default.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: nautilus 1:3.36.1.1-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
>   Uname: Linux 5.4.0-33-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27.2
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Tue Jun  2 11:41:18 2020
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2019-10-13 (232 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: nautilus
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881780/+subscriptions
>

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

Title:
  Nautilus requires SMBv1 to work from "Other Locations" without
  manually typing in the address.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Navigate to Other Locations.  Your SMB share should show here.
  Clicking on the share will cause an error "Unable to access location;
  Invalid Argument" if SMBv1 is disabled on the remote host.  Manually
  connecting by typing in the address still works.

  SMBv1 is deprecated due to WannaCry and other vulnerabilities.  Please
  fully deprecate SMBv1 by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  2 11:41:18 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-10-13 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1885744] Re: HIde im-config in application menus/searches

This bug was fixed in the package im-config - 0.44.1-1ubuntu2

---
im-config (0.44.1-1ubuntu2) groovy; urgency=medium

  * debian/rules:
- Don't show .desktop icon in Ubuntu (LP: #1885744)

 -- Gunnar Hjalmarsson   Tue, 30 Jun 2020 18:35:00
+0200

** Changed in: im-config (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  HIde im-config in application menus/searches

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Focal:
  In Progress

Bug description:
  [Impact]

  I'm refering to this conversation:
  
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2

  Current situation:
  ===
  - Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
  - im-config is difficult to understand for "normal users"

  Suggestion:
  ===
  Hide im-config from application menu / searches

  [Test Case]

  * Open Activities and find that "Input Method" is found

  * Install im-config from focal-proposed

  * Open Activities and find that "Input Method" is no longer found

  [Regression Potential]

  Minimal; only a tiny change in the .desktop file.

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-30 Thread Bradley Pearce

@mobilebackup - agreed that there are going to be lots of problems this
workaround will not solve. It is not yet clear whether any 'weirdness'
is caused by the original bug or the workaround.

With regards to the title bar, I am using the default gnome theme, with
'Larger Text' enabled in universal access. This seems to work with most
applications; however, in CLion and other Jetbrains IDE's im having to
set the font size to 48 to make it readable, as it does its own
rendering. Are you using a theme that renders its fonts for example? or
are you using a default theme?

Also, what other wierdness are you experiencing - I am getting lagginess
and jittering - however this is mostly when changing large amounts of
the screen (hense the comment about large rendering areas).

Sorry I'm not of more help, I would like to be, but the rendering stack
is a monolith - I was commenting on past experience of rendering larger
areas and scaling down (it doesn't work very well); that said, I can
currently do work on my configuration.

Apologies for more ramblings, if they are not helpful.

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

Title:
[nvidia] Screen scaling 125% gives 200%

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

Bug description:
Procedure used:
1.
Fully updated system via apt update && apt upgrade

2.
Select the screen setup in gnome control center

3.
Click the "Fractional scaling" toggle

4.
Select 125% and click the green "use" button top right (it says "Anvend" in
dansih)

5.
Observe that the window has grown a lot, click the "use new settings" button

6.
The window tells me, I am at 200% scaling. The "200%" option is now
highlighted.

7.
Switch back to 100% and file this bug.

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

[Desktop-packages] [Bug 1885742] [NEW] Unable to suspend, error -16

2020-06-30 Thread Kurrey Consultancy Services

Public bug reported:

Unable to suspend, error -16

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 30 20:57:50 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.138, 4.15.0-108-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
 NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
InstallationDate: Installed on 2018-08-29 (670 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=2674d4c6-6617-45bc-bd72-c1ecec60a6e9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 1/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN47WW(V3.08)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 3194STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Unable to suspend, error -16

Status in xorg package in Ubuntu:
  New

Bug description:
  Unable to suspend, error -16

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 30 20:57:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.138, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2018-08-29 (670 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=2674d4c6-6617-45bc-bd72-c1ecec60a6e9 ro quiet splash

[Desktop-packages] [Bug 1885749] [NEW] Enhancement: Remove default Emoji shortcuts

Public bug reported:

Current Situation
===

(1) 
Per default ibus preferences are hidden in Ubuntu
(I would say it's very difficult to reach ibus feature)

(2) 
ibus has two default shortcuts, apparently for Emoji-something: 
   - Ctrl+shift+e 
   - Ctrl+shift+u

(2.1) 
These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

(2.2) 
Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

(2.3) 
The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

(3)
I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)


Suggestion

Remove shortcuts as a default setting


Misc

- Why is this bug not filed in github.com/ibus/ibus/issues?
  -> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  1 00:55:25 2020
InstallationDate: Installed on 2020-06-29 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  New

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

This bug was fixed in the package usb-modeswitch - 2.6.0-2ubuntu1

---
usb-modeswitch (2.6.0-2ubuntu1) groovy; urgency=medium

  * Resynchronize on Debian
  * Remove dispatcher-c-rewrite, it has issues and no active maintainer
(LP: #1800794)
  * debian/rules:
- don't use the dynlink option, we use tcl rather libjim which
  is in Universe

  [ Gunnar Hjalmarsson ]
  * debian/control:
- Drop build-deps libpipeline-dev and libudev-dev
- Depends on tcl8.6
  * debian/rules:
- Set TCL=/usr/bin/tclsh8.6

usb-modeswitch (2.6.0-2) unstable; urgency=medium

  * Bump S-V to 4.4.1 without changes needed
  * Set Rules-Requires-Root to no

usb-modeswitch (2.6.0-1) unstable; urgency=medium

  * Update to new upstream version 2.6.0; the repack is not needed anymore as
the embedded 'jim' library has been taken out
  * Convert to git-debrebase workflow
  * Refresh patches
  * d/rules: Update make targets
  * Enable the Salsa CI Team standard pipeline

 -- Sebastien Bacher   Tue, 30 Jun 2020 16:37:41
+0200

** Changed in: usb-modeswitch (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827
  for complete issue description.

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

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

[Desktop-packages] [Bug 1884775] Re: SRU the current 3.36.3.1 stable update

Hello Sebastien, or anyone else affected,

Accepted gnome-desktop3 into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.36.3.1-0ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-desktop3 (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.3.1 stable update

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.3

  * Regression potential

  The update has some test and translations fixes and a change to the
  thumbnailing, check that nautilus still previews images correctly

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

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

[Desktop-packages] [Bug 1885630] Re: Apps becoming unresponsive

2020-06-30 Thread Rishik

I have disabled other extensions and now the problem is gone, it was a
problem with Dash To Panel and not ubuntu

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

Title:
  Apps becoming unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I know that this isn't a display issue,but when I try to send this bug
  under the "other" category I get told that I need to specify PID and
  it closes.

  Whenever a application is left opened in the background for a while
  and is not minimized, and I minimize the app that I am currently
  using,the background apps become unresponsive until I minimize and
  unminimize them from the task bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 15:59:26 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 480 Gaming X 
8GB [1462:3413]
  InstallationDate: Installed on 2020-06-17 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=1623944a-6c8f-4fe6-918e-8bdaa1315c8a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Z370M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/01/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1875477] Re: LibreOffice Base will not load my odb file. I get an error messge

2020-06-30 Thread Hugh Lupien

Thank you Davide, I did what you said to install the hsqldb driver and
it worked perfectly. Thank you, thank you, thank you!

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

Title:
  LibreOffice Base will not load my odb file. I get an error messge

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to LTS 20.04. For a data base that worked perfectly under LTS 
18.04,afterloading my database NamesU.odb, when I try to open any table, query 
or Form, I get the error messageI get the message:
  "The connection to the data source "NamesU" could not be established.
  he connection to the external data source could not be established. No SDBC 
driver was found for the URL 'sdbc:embedded:hsqldb".

  Please help by telling me how to fix this. Thank you,

  Hugh Lupien

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 15:01:45 2020
  InstallationDate: Installed on 2018-04-30 (727 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (3 days ago)
  VarLogDistupgradeTermlog:

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

-- 
Mailing list: https://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 1875477] Re: LibreOffice Base will not load my odb file. I get an error messge

2020-06-30 Thread Hugh Lupien

Thank you Davide. I did the sudo apt install libreoffice-sdbc-hsqldb as
you suggested and it worked perfectly. Thank you, thank you, thank you!

On Monday, June 29, 2020, 4:10:56 PM EDT, Davide 
<1875...@bugs.launchpad.net> wrote:  
 
 It should have been installed together with the libreoffice-base package

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1875477

Title:
  LibreOffice Base will not load my odb file. I get an error messge

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to LTS 20.04. For a data base that worked perfectly under LTS 
18.04,afterloading my database NamesU.odb, when I try to open any table, query 
or Form, I get the error messageI get the message:
  "The connection to the data source "NamesU" could not be established.
  he connection to the external data source could not be established. No SDBC 
driver was found for the URL 'sdbc:embedded:hsqldb".

  Please help by telling me how to fix this. Thank you,

  Hugh Lupien

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 15:01:45 2020
  InstallationDate: Installed on 2018-04-30 (727 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

Title:
  LibreOffice Base will not load my odb file. I get an error messge

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to LTS 20.04. For a data base that worked perfectly under LTS 
18.04,afterloading my database NamesU.odb, when I try to open any table, query 
or Form, I get the error messageI get the message:
  "The connection to the data source "NamesU" could not be established.
  he connection to the external data source could not be established. No SDBC 
driver was found for the URL 'sdbc:embedded:hsqldb".

  Please help by telling me how to fix this. Thank you,

  Hugh Lupien

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 15:01:45 2020
  InstallationDate: Installed on 2018-04-30 (727 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors

2020-06-30 Thread Danny Lawson

Since no one responded yet, I installed the updated packages from #33,
and still have the same issue.

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

Title:
  [nvidia] Dual monitor setup with secondary monitor in portrait-right
  mode cause tiled windows to occupy 1.5 monitors

Status in gnome-control-center:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted.

  I use dual screen : the main screen is on the left side (32"), the
  secondary screen (19") is at right and in portrait mode (rotated
  right). The window are improperly growed : they extend from full main
  screen to half the "witdh" of the secondary screen. Additionnally, the
  « pop-up » menus (eg. from settings) do not appear at the right place
  (see screen capture in comment). The problem disappears if I revert
  the orientation of secondary screen from « portrait turned right » to
  « landscape ». I do have gnome-shell-extension-ubuntu-dock in version
  67ubuntu20.04.5, but still got the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 11:11:25 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-19 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1885765] [NEW] Ubuntu dock and launchpad have problems to start at system boot

You have been subscribed to a public bug:

The dock and launchpad need a few minutes to work properly. Neither the dock 
nor the launchpad are showing me any icons. The search engine works perfectly 
so i can launch my programs from there. i tried reinstall 
gnome-shell-extension-ubuntu-dock but that didn't solve any problems. The 
problem happens at every boot. Currently on Ubuntu 20.04 LTS
I tried reinstall gnome-shell-extension-ubuntu-dock with version 
68ubuntu1~20.04.1 and some other programs but that didn't solve any problems.

Thank you :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 30 20:28:51 2020
InstallationDate: Installed on 2020-02-07 (143 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to focal on 2020-05-15 (45 days ago)

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session
-- 
Ubuntu dock and launchpad have problems to start at system boot
https://bugs.launchpad.net/bugs/1885765
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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 1885773] [NEW] [4125, recording] Recording problem - input device is not listed on my machine.

You have been subscribed to a public bug:

I have connected two input device to my machine (Intel BOXNUC8). One is
headphones, and the other is bluetooth speaker. I also have an HDMI
monitor which allegedly supports input device. However, the only input
device which is listed in the sound setting device is the NUC's internal
microphone. The bug report tools suggested I'd use pavucontrol or the
gnome setting interface. Pavucontrol does list the bluetooth speaker
(under monitors). I also see the headphones there, listed as built-in
input device but I can't seem to get them to work properly.

The main bug here is that I won't see the input device listed under the
computer settings.

release: 20.04

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  geffen27236 F pulseaudio
 /dev/snd/pcmC0D0c:   geffen27236 F...m pulseaudio
 /dev/snd/pcmC0D0p:   geffen27236 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 30 22:18:26 2020
InstallationDate: Installed on 2020-04-12 (79 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: 4125
Symptom_Type: None of the above
Title: [4125, recording] Recording problem
UpgradeStatus: Upgraded to focal on 2020-04-28 (62 days ago)
dmi.bios.date: 06/18/2019
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BECFL357.86A.0073.2019.0618.1409
dmi.board.name: NUC8BEB
dmi.board.vendor: Intel Corporation
dmi.board.version: J72692-308
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-308:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: BE
dmi.product.name: NUC8i5BEH
dmi.product.sku: BOXNUC8i5BEH
dmi.product.version: J72747-306
dmi.sys.vendor: Intel(R) Client Systems
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-08T16:19:26.048126

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


** Tags: amd64 apport-bug focal
-- 
[4125, recording] Recording problem - input device is not listed on my machine. 
https://bugs.launchpad.net/bugs/1885773
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver 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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-06-30 Thread Michael Scott Roelker

#63 and #65 did not work for me, resulted in dummy audio - #66 also did
not work for me.

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

2020-06-30 Thread Michael Scott Roelker

for #78 my specs

Linux michaelroelker-Lenovo-YOGA-C930-13IKB 5.4.0-39-generic #43-Ubuntu
SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC298 Analog [ALC298 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

experiencing issues in 18.04 and 20.04. headset workaround for now.

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1885773] Re: [4125, recording] Recording problem - input device is not listed on my machine.

2020-06-30 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [4125, recording] Recording problem - input device is not listed on my
  machine.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have connected two input device to my machine (Intel BOXNUC8). One
  is headphones, and the other is bluetooth speaker. I also have an HDMI
  monitor which allegedly supports input device. However, the only input
  device which is listed in the sound setting device is the NUC's
  internal microphone. The bug report tools suggested I'd use
  pavucontrol or the gnome setting interface. Pavucontrol does list the
  bluetooth speaker (under monitors). I also see the headphones there,
  listed as built-in input device but I can't seem to get them to work
  properly.

  The main bug here is that I won't see the input device listed under
  the computer settings.

  release: 20.04

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  geffen27236 F pulseaudio
   /dev/snd/pcmC0D0c:   geffen27236 F...m pulseaudio
   /dev/snd/pcmC0D0p:   geffen27236 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 30 22:18:26 2020
  InstallationDate: Installed on 2020-04-12 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 4125
  Symptom_Type: None of the above
  Title: [4125, recording] Recording problem
  UpgradeStatus: Upgraded to focal on 2020-04-28 (62 days ago)
  dmi.bios.date: 06/18/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0073.2019.0618.1409
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72692-308
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-308:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: BE
  dmi.product.name: NUC8i5BEH
  dmi.product.sku: BOXNUC8i5BEH
  dmi.product.version: J72747-306
  dmi.sys.vendor: Intel(R) Client Systems
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-08T16:19:26.048126

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

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

[Desktop-packages] [Bug 1885765] Re: Ubuntu dock and launchpad have problems to start at system boot

2020-06-30 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)

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

Title:
  Ubuntu dock and launchpad have problems to start at system boot

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  The dock and launchpad need a few minutes to work properly. Neither the dock 
nor the launchpad are showing me any icons. The search engine works perfectly 
so i can launch my programs from there. i tried reinstall 
gnome-shell-extension-ubuntu-dock but that didn't solve any problems. The 
problem happens at every boot. Currently on Ubuntu 20.04 LTS
  I tried reinstall gnome-shell-extension-ubuntu-dock with version 
68ubuntu1~20.04.1 and some other programs but that didn't solve any problems.

  Thank you :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 30 20:28:51 2020
  InstallationDate: Installed on 2020-02-07 (143 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-05-15 (45 days ago)

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

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

[Desktop-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()

2020-06-30 Thread Sergey

I reported a bug https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885272
marked as duplicate of this
Please tell me what I can do to make the system work stably?

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from
  xf86MoveCursor() from miPointerMoveNoEvent() from
  miPointerSetPosition() from positionSprite()

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1881918] Re: Update GNOME Software to 3.36.1 in Focal

Hello AsciiWolf, or anyone else affected,

Accepted gnome-software into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.36.1-0ubuntu0.20.04.0 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-focal

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

Title:
  Update GNOME Software to 3.36.1 in Focal

Status in One Hundred Papercuts:
  New
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gnome-software.

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could cause issues in GNOME Software, which might make it hard
  to install or remove software. Default store in Ubuntu is snap-store,
  so this doesn't affect the majority of users.

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

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

[Desktop-packages] [Bug 1875665] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

2020-06-30 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

[Desktop-packages] [Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling

Hello Iain, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

  
  * Test Case

  Do this in an Ubuntu/Xorg session:

  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle

  Now everything is shrunk - it's not been returned to 100% properly.
  See the attached screenshot where the text is tiny instead of regular
  100% size. If you do this instead of step 5:

  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle

  Then everything returns to the normal size.

  I'm on nvidia(-440), but Séb said that he saw this on his Intel
  machine too.

  
  * Regression potential

  Verify that scaling changes are correctly applied on different setup

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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

[Desktop-packages] [Bug 1871864] Re: Toggle "Fractional Scaling" does nothing on wayland

Hello Grant, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Toggle "Fractional Scaling" does nothing on wayland

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact 
  In the setting there is option called "Fractional Scaling" but this option 
only works for X11.

  * Test Case
  Enable the experimental scaling option in settings and verify that non 
integer values are listed in the choices

  * Regression potential
  Check that turning the option on and off works in xorg and wayland

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

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

[Desktop-packages] [Bug 1884063] Re: SRU the current 3.36.3 stable update

Hello Sebastien, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.3 stable update

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the GNOME settings still work correctly

  * Regression potential

  Nothing specific to test in this update

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

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

[Desktop-packages] [Bug 1877441] Re: Fingerprint icons during enrollment are selectable

Hello Marco, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Fingerprint icons during enrollment are selectable

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Fingerprint enrollment icons are selectable while they should support no 
interaction.
  See picture at 
https://www.reddit.com/r/Ubuntu/comments/g6st9d/2004_comes_with_fingerprint_locks/

  [ Test case ]

  - Start enrolling a finger
  - Clicking or changing focus with tab should not highlight an icon

  [ Regression potential ]

  Print icons are not properly rendered

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

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

[Desktop-packages] [Bug 1876891] Re: The fractional scaling toggle applies instantly and not when "Apply" is pressed

Hello Iain, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

  * Test Case

  Do this when in an Xorg/Ubuntu session:

  0. Have fractional scaling disabled and set to 100%
  1. Go to gnome-control-center -> displays
  2. Turn on the fractional scaling toggle
  3. Select 125%
  4. Press apply (the scaling should apply correctly)
  5. Turn off the toggle
  6. Turn the toggle back on

  At 5 and 6, the scaling changes. It shouldn't - this should only
  happen when you press 'Apply'. The toggle needs to not be directly
  connected to GSettings.

  * Regression potential

  Check that screen settings changed are correctly applied and only when
  clicking the corresponding button

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:35:48 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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

[Desktop-packages] [Bug 1876937] Re: Dock location reversed in RTL

Hello Yaron, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Dock location reversed in RTL

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  he dock location is horizontally reversed, selecting left puts the
  dock to the right and vice versa.

  
  * Test Case

  Steps to reproduce (Ubuntu 20.04):

  1. Switch to an RTL language of your choice

  2. Open GNOME Settings

  3. Observe the Appearance icon (The default dock location is to the
  right while the icon shows as if it's to the left)

  4. The selection says "Left" (שמאל in Hebrew) yet the dock is aligned
  to the right, selecting the opposite option moves the dock to the left
  although I selected "Right" (ימין in Hebrew).

  
  * Regression potential

  Check that the position setting does match what the dock is doing

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

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

[Desktop-packages] [Bug 1877108] Re: Ubuntu Dock appears on the display opposite to that indicated on Appearance tab

Hello Paul, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.3-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Ubuntu Dock appears on the display opposite to that indicated on
  Appearance tab

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The screen labels displayed when settigns are open are inverted

  * Test Case

  Display 1 is the laptop's built-in monitor
  Display 2 is the external monitor set as being the primary display

  To reproduce:

  1) Go to the Appearance tab
  2) "Show on" will indicate on which display the dock is being shown
  3) In my case it is set to "1. Built in display" but it appears on the second 
or primary display
  4) Change the setting and the dock will move but...
  5) In my case if I change to "2. GKE 24 (Primary display)" the dock appears 
on the built-in display.

  
  * Regression potential

  Checking that in settings -> display the screen labels are correct

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

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

[Desktop-packages] [Bug 1877108] Re: Ubuntu Dock appears on the display opposite to that indicated on Appearance tab

2020-06-30 Thread Paul White

I started gnome-control-center to verify I was still seeing the bug and
then enabled -proposed and updated to version 1:3.36.3-0ubuntu1.

I restarted gnome-control-center and saw the drop-down now correctly
shows on which display the dock is being shown. All three settings work
as they should as the dock can be moved between displays, or shown on
both displays and the drop-down always shows the correct text unlike
previously.

Marking as verified.


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

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

Title:
  Ubuntu Dock appears on the display opposite to that indicated on
  Appearance tab

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The screen labels displayed when settigns are open are inverted

  * Test Case

  Display 1 is the laptop's built-in monitor
  Display 2 is the external monitor set as being the primary display

  To reproduce:

  1) Go to the Appearance tab
  2) "Show on" will indicate on which display the dock is being shown
  3) In my case it is set to "1. Built in display" but it appears on the second 
or primary display
  4) Change the setting and the dock will move but...
  5) In my case if I change to "2. GKE 24 (Primary display)" the dock appears 
on the built-in display.

  
  * Regression potential

  Checking that in settings -> display the screen labels are correct

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

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

[Desktop-packages] [Bug 1885610] Re: enlarged components on lock/login screen

2020-06-30 Thread Daniel van Vugt

Oops. Come to think of it the login screen runs as a different user and
that's a system extension. So disabling anything in the GUI won't
work... Please try:

1. Uninstall the user-theme extension and any other non-Ubuntu
extensions.

2. Reboot.

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

Title:
  enlarged components on lock/login screen

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

Bug description:
  Source Package: usr/bin/gnome-shell
  Ubuntu Release: 20.04 LTS
  Package Version: 3.36.2-1ubuntu1~20.04.1
  Expected: Normal sized components on lock/login screen
  Happened: Enlarged components on lock/login screen

  This behavior is unaffected by resolution size from different monitors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Flat-Remix-Miami-Dark-GNOME:GNOME
  Date: Mon Jun 29 13:01:06 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-02 (331 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-06-27 (2 days ago)

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

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

[Desktop-packages] [Bug 1884326] Re: SRU the current 2.48.7 stable update