[Desktop-packages] [Bug 1800542] Re: OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6)

[Steve Langasek]

Following the debugging instructions at
https://wiki.gnome.org/Projects/NetworkManager/Debugging
#Debugging_NetworkManager-openvpn was not sufficient to get debug logs;
NM still spawned a separate nm-openvpn-service process instead of using
the one I was running from a terminal, despite supports-multiple-
connections=false being set.  Does NM have to be restarted after making
this change?

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

Title:
  OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6)

Status in network-manager-openvpn package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to Ubuntu 18.10, my connection to my employer's VPN
  server has become unstable.

  The server provides both ipv4 and ipv6 endpoints.  Since I have global
  ipv6 at home, my client defaults to connecting over ipv6.

  The connection consistently drops after only a few minutes of being
  connected.

  If I force the connection to use ipv4 (by hard-coding the host
  resolution in /etc/hosts), the connection is stable.

  If I use ipv6 and force proto-tcp=yes, the connection is stable.

  If I use the default ipv6 and udp, the connection is not stable.

  Using tcp for VPNs is suboptimal.  Hard-coding addresses in /etc/hosts
  is suboptimal.

  This may be a bug in openvpn rather than in network-manager-openvpn,
  but I'm starting here.

  It's possible there are pathMTU issues involved, but I reproduced this
  same problem when I was on a different network from my home network
  (though I did not confirm, when I had access to this other network,
  that it was ipv6-enabled).

  I will work on getting more details about both sides of the network to try to 
debug this.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2010-09-24 (2957 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: network-manager-openvpn 1.8.6-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (11 days ago)
  UserGroups: adm admin cdrom dialout docker libvirt libvirtd lpadmin lxd 
mythtv plugdev sambashare sbuild src sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 826709] Re: "save as"-weirdness when overwriting unix-style hidden files

[Launchpad Bug Tracker]

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

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  "save as"-weirdness when overwriting unix-style hidden files

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When using the saveas-dialog to download and overwrite my existing 
".signature"-file (~/.thunderbird/uq6h88eb.default/Mail/.signature) the 
following weirdness happens:
  - firefox asks me if I really want to overwrite the existing file -- as 
expected
  - I answer OK/YES
  - firefox deletes the existing file -- as could be expected
  - firefox saves the downloaded file under a new name (without the leading dot)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  Architecture: i386
  Date: Mon Aug 15 13:55:50 2011
  FirefoxPackages:
   firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2
   flashplugin-installer 10.3.183.4ubuntu0.11.04.1
   adobe-flashplugin 10.0.32.18-1
   icedtea-plugin 1.1.1-0ubuntu1~11.04.1
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2011-06-08 (68 days ago)

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

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

[Desktop-packages] [Bug 852189] Re: no global menu for reopened session with many windows

[Launchpad Bug Tracker]

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

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  no global menu for reopened session with many windows

Status in firefox package in Ubuntu:
  Expired

Bug description:
  steps to reproduce:
  1. enabled firefox session manager (should be default)
  2. preferably have bartab extention in old firefoxes or 
browser.sessionstore.max_concurrent_tabs set to 0 in newer ones to not reopen 
inactive tabs for resource usage to not crawl with many windows with many tabs 
(in my case 20-30 windows with 6-12 tabs each)
  2. open lot of firefox windows with many tabs for each with something loaded 
in them
  3. close browser selecting quit
  4. relaunch it
  5. none of restored browser windows have global menu, except 'new window' 
opened ones
  6. if browser was crashed and on reopening has single window with user query 
on further action about restoring session, then all restored windows have 
global menu as intended.

  Would love to see firefox globalmenu working as intended even for such
  bad cases as my browsing habits without having to kill browser for
  session restore window on reopen.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox-globalmenu 6.0.2+build2+nobinonly-0ubuntu0.11.04.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Fri Sep 16 23:56:25 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1814330] Re: My adblocker for the Firefox browser was removed in the last update

[Launchpad Bug Tracker]

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

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  My adblocker for the Firefox browser was removed in the last update

Status in firefox package in Ubuntu:
  Expired

Bug description:
  The adblocker just disappeared.  I am not tech savvy enough to find
  out why.

  When I checked my downloads, in the file system, it seems like some of
  them are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 65.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyn1866 F pulseaudio
  BuildID: 20190128144255
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 12:22:49 2019
  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 2017-08-03 (546 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IpRoute:
   default via 192.168.1.1 dev eno1 proto dhcp metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-f276e77a-a433-4a98-8e56-550590190124
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=65.0/20190128144255 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-f276e77a-a433-4a98-8e56-550590190124
   bp-b22f8099-c16b-4b0c-8bbb-79f220181017
   bp-d0d17655-e24b-41db-af32-9fa570181002
   bp-0aaa6a42-121b-4587-8d37-df3141180328
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (169 days ago)
  dmi.bios.date: 04/04/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.29
  dmi.board.asset.tag: 2UA1311DPS
  dmi.board.name: 1494
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA1311DPS
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.29:bd04/04/2016:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite CMT PC
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1635773] Re: fonts in the address bar of chrome/chromium are too small

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  fonts in the address bar of chrome/chromium are too small

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  After upgrade to 16.10 fonts in address bar of chromium/chrome are too
  small and cannot be tune by unity tweak tool.

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

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[kecsap]

Proposed fix works, the touchscreen is much more usable with libinput on
Lenovo Thinkpad X1 Yoga 1st gen now.

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1823440] [NEW] ubuntu-report ftbfs in disco

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924361/buildlog_ubuntu-disco-amd64
.ubuntu-report_1.4.0_BUILDING.txt.gz

   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.mod exists 
in debian/tmp but is not installed to anywhere
dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.sum exists 
in debian/tmp but is not installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: golang-github-ubuntu-ubuntu-report-dev (2), 
libsysmetrics-dev (3), libsysmetrics1 (1), ubuntu-report (6)
 * dh_installdocs: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (0)
 * dh_installman: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (4)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
make[1]: *** [debian/rules:39: override_dh_missing] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: binary] Error 2

** Affects: ubuntu-report (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: ubuntu-report (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  ubuntu-report ftbfs in disco

Status in ubuntu-report package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924361/buildlog_ubuntu-disco-amd64
  .ubuntu-report_1.4.0_BUILDING.txt.gz

 debian/rules override_dh_missing
  make[1]: Entering directory '/<>'
  dh_missing --fail-missing
  dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.mod 
exists in debian/tmp but is not installed to anywhere
  dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.sum 
exists in debian/tmp but is not installed to anywhere
  dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: golang-github-ubuntu-ubuntu-report-dev (2), 
libsysmetrics-dev (3), libsysmetrics1 (1), ubuntu-report (6)
 * dh_installdocs: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (0)
 * dh_installman: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (4)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
  make[1]: *** [debian/rules:39: override_dh_missing] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:14: binary] Error 2

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

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

[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode

[kecsap]

Similar to @Flavio Henrique Bastos, @Paul Müller, it happened on my
Lenovo X1 Yoga, running the touchscreen with libinput driver
(https://bugs.launchpad.net/ubuntu/+source/xf86-input-
wacom/+bug/1774242).

Disabling/enabling the touch screen resolved the problem:

xinput --set-prop "Wacom Pen and multitouch sensor Finger" "Device Enabled" 0
xinput --set-prop "Wacom Pen and multitouch sensor Finger" "Device Enabled" 1

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

Title:
  Mouse cursor gets stuck in "drag and drop" mode

Status in OpenShot Video Editor:
  New
Status in X.Org X server:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in rapidsvn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rapidsvn

  When clicking on the Bookmark root or on one of the bookmarks below
  the mouse cursor gets stuck in "drag n drop" mode, blocking all
  keyboard entry and also mouse clicks for the the whole GUI
  (systemwide).

  Unfortunately I cannot provide any debug or other information, as I
  have to reboot everytime.

  I am running Ubuntu 9.04 with compiz enabled.

  Many thanks in advance for your help with this problem,
  /nxT

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

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

[Desktop-packages] [Bug 1823435] [NEW] session-migration ftbfs in disco

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
.session-migration_0.3.3_BUILDING.txt.gz

make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
Scanning dependencies of target check
make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
nosetests3
...FF
==
FAIL: Test that the migration happens as expected
--
Traceback (most recent call last):
  File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
- 10_test.sh;01_test.sh;02_test.sh;
+ 01_test.sh;02_test.sh;10_test.sh;


==
FAIL: Test subsequent runs with a new script
--
Traceback (most recent call last):
  File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
- 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
+ 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;


--
Ran 9 tests in 8.615s

FAILED (failures=2)
make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:167: check] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build] Error 2

** Affects: session-migration (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: session-migration (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  

[Desktop-packages] [Bug 1823437] [NEW] shotwell ftbfs in disco

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924359/buildlog_ubuntu-disco-
amd64.shotwell_0.30.2-0ubuntu1_BUILDING.txt.gz

multiple vala/glib errors

** Affects: shotwell (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

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

** Tags added: ftbfs rls-dd-incoming

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

Title:
  shotwell ftbfs in disco

Status in shotwell package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924359/buildlog_ubuntu-disco-
  amd64.shotwell_0.30.2-0ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

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

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

[Desktop-packages] [Bug 1823432] [NEW] openexr ftbfs in disco (i386 only)

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

compression 7, x sampling 2, y sampling 2: writing reading comparing
compression 8, x sampling 2, y sampling 2: writing reading comparing
compression 9, x sampling 2, y sampling 2: writing reading comparing
random bits
compression 0, x sampling 1, y sampling 1: writing reading comparingIlmImfTest: 
testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
FAIL IlmImfTest (exit status: 134)


Testsuite summary for OpenEXR 2.2.1

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See IlmImfTest/test-suite.log

make[5]: *** [Makefile:966: test-suite.log] Error 1
make[5]: Leaving directory '/<>/IlmImfTest'
make[4]: *** [Makefile:1074: check-TESTS] Error 2
make[4]: Leaving directory '/<>/IlmImfTest'
make[3]: *** [Makefile:1148: check-am] Error 2
make[3]: Leaving directory '/<>/IlmImfTest'
make[2]: *** [Makefile:498: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:25: build-arch] Error 2

** Affects: openexr (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

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

** Tags added: ftbfs rls-dd-incoming

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

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

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

[Desktop-packages] [Bug 1823425] [NEW] libdmapsharing ftbfs in disco

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924367/buildlog_ubuntu-disco-
amd64.libdmapsharing_2.9.39-4_BUILDING.txt.gz

Making all in tests
make[3]: Entering directory '/<>/tests'
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject  
dacplisten.vala vala-dmap-db.vala vala-dmap-container-db.vala -C
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gtk+-2.0 --pkg 
gstreamer-1.0 --pkg libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg 
avahi-gobject dpapview.vala vala-dmap-db.vala vala-dpap-record.vala -C
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapcopy.vala vala-dmap-db.vala vala-dpap-record.vala -C
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapserve.vala vala-dmap-db.vala vala-dpap-record.vala 
vala-dmap-container-db.vala -C
vala-dpap-record.vala:120.3-120.42: warning: unhandled error `GLib.FileError'
GLib.FileUtils.get_data (path, out data);

vala-dmap-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'
db.add (((DMAP.Record) record));
^^
vala-dmap-db.vala:27.2-27.46: vala-dmap-db.vala:31.10-31.16: error: The name 
`size' does not exist in the context of `ValaDMAPDb.db'
return db.size;
   ^^^
vala-dmap-db.vala:43.10-43.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
error: Cannot convert from 
`Gee.ArrayList'vala-dmap-db.vala:58.10-58.15: error: The name 
`get' does not exist in the context of `ValaDMAPDb.db'
return db.get ((int) id - 1);
   ^^
vala-dmap-container-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
 to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
vala-dmap-container-db.vala:30.10-30.16: error: The name `size' does not exist 
in the context of `ValaDMAPContainerDb.db'
return db.size;
   ^^   ^
^^^vala-dmap-container-db.vala:35.19-35.25: 
^^
vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'error: The name `size' does not exist in the context 
of `ValaDMAPContainerDb.db'
for (i = 0; i < db.size; i++) {
^^^

db.add (((DMAP.Record) record));
dmapserve.vala:34.40-34.43: ^^
vala-dmap-db.vala:31.10-31.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
warning: Argument 2: Cannot pass null to non-null parameter type
vala-dmap-db.vala:43.10-43.16: error: The name  share = new DPAP.Share 
("dmapserve", null, db, container_db, null);
 
dmapserve.vala:34.64-34.67: warning: Argument 5: Cannot pass null to non-null 
parameter type
share = new DPAP.Share ("dmapserve", null, db, container_db, 
null);
 

`size' does not exist in the context of 
`ValaDMAPDb.db'dmapserve.vala:57.6-57.32: 
return db.size;
   ^^^
warning: unhandled error `GLib.Error'
vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
var dmapcopy = new DPAPServe ();
^^^vala-dmap-db.vala:58.10-58.15: error: The name `get' does not 
exist in the context of `ValaDMAPDb.db'
return db.get ((int) id - 1);
   ^^

Compilation failed: 9 error(s), 4 warning(s)
vala-dpap-record.vala:120.3-120.42: warning: unhandled error `GLib.FileError'
GLib.FileUtils.get_data (path, out data);

dmapcopy.vala:95.6-95.31: warning: unhandled error `GLib.Error'
var dmapcopy = new DPAPCopy 

[Desktop-packages] [Bug 1823426] [NEW] librsvg ftbfs in disco (i386 only)

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

   Compiling phf_generator v0.7.23
 Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
error[E0428]: the name `U1024` is defined multiple times
--> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
 |
2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
 | 
-
 previous definition of the type `U1024` here
2111 | pub type P1024 = PInt; pub type N1024 = NInt;
2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
 | 
^
 `U1024` redefined here
 |
 = note: `U1024` must be defined only once in the type namespace of this 
module

error[E0428]: the name `P1024` is defined multiple times
--> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
 |
2111 | pub type P1024 = PInt; pub type N1024 = NInt;
 | - previous definition of the type 
`P1024` here
2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;
 | ^ `P1024` redefined here
 |
 = note: `P1024` must be defined only once in the type namespace of this 
module

error[E0428]: the name `N1024` is defined multiple times
--> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
 |
2111 | pub type P1024 = PInt; pub type N1024 = NInt;
 |   - previous 
definition of the type `N1024` here
2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;
 |   ^ `N1024` 
redefined here
 |
 = note: `N1024` must be defined only once in the type namespace of this 
module

   Compiling quote v0.6.8
 Running `rustc --crate-name quote /<>/vendor/quote/src/lib.rs 
--color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C 
debuginfo=2 --cfg 'feature="default"' --cfg 'feature="proc-macro"' --cfg 
'feature="proc-macro2"' -C metadata=7bcb03a3954c3d99 -C 
extra-filename=-7bcb03a3954c3d99 --out-dir /<>/target/release/deps 
-L dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0428`.
error: Could not compile `typenum`.

Caused by:
  process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
warning: build failed, waiting for other jobs to finish...
error: build failed
make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:1457: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:940: all] Error 2

** Affects: librsvg (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

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

** Tags added: ftbfs rls-dd-incoming

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 

[Desktop-packages] [Bug 1823423] [NEW] ibus ftbfs in disco

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco-
amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz

multiple vala/glib errors

** Affects: ibus (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Tags added: ftbfs rls-dd-incoming

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

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

Title:
  ibus ftbfs in disco

Status in ibus package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco-
  amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

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

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

[Desktop-packages] [Bug 1823421] [NEW] deja-dup ftbfs in disco

[Matthias Klose]

Public bug reported:

https://launchpadlibrarian.net/417924442/buildlog_ubuntu-disco-amd64
.deja-dup_38.3-1_BUILDING.txt.gz

make[1]: Leaving directory '/<>'
   dh_auto_build -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
[1/96] glib-compile-resources data/resources.vars.xml --sourcedir ../data/ui 
--sourcedir ../data --internal --generate --target data/resources.h
[2/96] glib-compile-resources data/resources.vars.xml --sourcedir ../data/ui 
--sourcedir ../data --internal --generate --target data/resources.c 
--dependency-file data/resources.c.d
[3/96] valac -C --debug --pkg gio-2.0 --color=always --directory 
deja-dup/nautilus/248796f@@dirhandling@sta --basedir ../deja-dup/nautilus 
--library dirhandling --header deja-dup/nautilus/dirhandling.h --vapi 
../dirhandling.vapi --pkg=config --pkg=posix --target-glib=2.46 --vapidir 
/<>/vapi --define=HAS_PACKAGEKIT 
/<>/libdeja/DirHandling.vala
[4/96] valac -C --debug --pkg libsecret-1 --pkg libpeas-1.0 --pkg 
packagekit-glib2 --pkg goa-backend-1.0 --pkg goa-1.0 --pkg gio-unix-2.0 --pkg 
gio-2.0 --color=always --directory libdeja/ccd1814@@deja@sha --basedir 
../libdeja --library deja --header libdeja/deja.h --vapi ../deja.vapi 
--pkg=config --pkg=posix --target-glib=2.46 --vapidir /<>/vapi 
--define=HAS_PACKAGEKIT --pkg=secret --pkg=uriutils ../libdeja/Backend.vala 
../libdeja/BackendAuto.vala ../libdeja/BackendDrive.vala 
../libdeja/BackendFile.vala ../libdeja/BackendGCS.vala 
../libdeja/BackendGOA.vala ../libdeja/BackendLocal.vala 
../libdeja/BackendOpenstack.vala ../libdeja/BackendRackspace.vala 
../libdeja/BackendRemote.vala ../libdeja/BackendS3.vala 
../libdeja/BackendU1.vala ../libdeja/CommonUtils.vala 
../libdeja/DirHandling.vala ../libdeja/FilteredSettings.vala 
../libdeja/Network.vala ../libdeja/Operation.vala 
../libdeja/OperationBackup.vala ../libdeja/OperationFiles.vala 
../libdeja/OperationRestore.vala ../libdeja/OperationStatus.vala 
../libdeja/OperationVerify.vala ../libdeja/RecursiveDelete.vala 
../libdeja/RecursiveMove.vala ../libdeja/RecursiveOp.vala 
../libdeja/ToolPlugin.vala
FAILED: libdeja/ccd1814@@deja@sha/Backend.c 
libdeja/ccd1814@@deja@sha/BackendAuto.c 
libdeja/ccd1814@@deja@sha/BackendDrive.c 
libdeja/ccd1814@@deja@sha/BackendFile.c libdeja/ccd1814@@deja@sha/BackendGCS.c 
libdeja/ccd1814@@deja@sha/BackendGOA.c libdeja/ccd1814@@deja@sha/BackendLocal.c 
libdeja/ccd1814@@deja@sha/BackendOpenstack.c 
libdeja/ccd1814@@deja@sha/BackendRackspace.c 
libdeja/ccd1814@@deja@sha/BackendRemote.c libdeja/ccd1814@@deja@sha/BackendS3.c 
libdeja/ccd1814@@deja@sha/BackendU1.c libdeja/ccd1814@@deja@sha/CommonUtils.c 
libdeja/ccd1814@@deja@sha/DirHandling.c 
libdeja/ccd1814@@deja@sha/FilteredSettings.c 
libdeja/ccd1814@@deja@sha/Network.c libdeja/ccd1814@@deja@sha/Operation.c 
libdeja/ccd1814@@deja@sha/OperationBackup.c 
libdeja/ccd1814@@deja@sha/OperationFiles.c 
libdeja/ccd1814@@deja@sha/OperationRestore.c 
libdeja/ccd1814@@deja@sha/OperationStatus.c 
libdeja/ccd1814@@deja@sha/OperationVerify.c 
libdeja/ccd1814@@deja@sha/RecursiveDelete.c 
libdeja/ccd1814@@deja@sha/RecursiveMove.c 
libdeja/ccd1814@@deja@sha/RecursiveOp.c libdeja/ccd1814@@deja@sha/ToolPlugin.c 
libdeja/deja.h libdeja/deja.vapi 
valac -C --debug --pkg libsecret-1 --pkg libpeas-1.0 --pkg packagekit-glib2 
--pkg goa-backend-1.0 --pkg goa-1.0 --pkg gio-unix-2.0 --pkg gio-2.0 
--color=always --directory libdeja/ccd1814@@deja@sha --basedir ../libdeja 
--library deja --header libdeja/deja.h --vapi ../deja.vapi --pkg=config 
--pkg=posix --target-glib=2.46 --vapidir /<>/vapi 
--define=HAS_PACKAGEKIT --pkg=secret --pkg=uriutils ../libdeja/Backend.vala 
../libdeja/BackendAuto.vala ../libdeja/BackendDrive.vala 
../libdeja/BackendFile.vala ../libdeja/BackendGCS.vala 
../libdeja/BackendGOA.vala ../libdeja/BackendLocal.vala 
../libdeja/BackendOpenstack.vala ../libdeja/BackendRackspace.vala 
../libdeja/BackendRemote.vala ../libdeja/BackendS3.vala 
../libdeja/BackendU1.vala ../libdeja/CommonUtils.vala 
../libdeja/DirHandling.vala ../libdeja/FilteredSettings.vala 
../libdeja/Network.vala ../libdeja/Operation.vala 
../libdeja/OperationBackup.vala ../libdeja/OperationFiles.vala 
../libdeja/OperationRestore.vala ../libdeja/OperationStatus.vala 
../libdeja/OperationVerify.vala ../libdeja/RecursiveDelete.vala 
../libdeja/RecursiveMove.vala ../libdeja/RecursiveOp.vala 
../libdeja/ToolPlugin.vala
../libdeja/ToolPlugin.vala:79.7-79.40: error: Assignment: Cannot convert from 
`GLib.List' to `GLib.List'
  this._restore_files = value.copy();
  ^^
../libdeja/OperationRestore.vala:36.7-36.40: error: Assignment: Cannot convert 
from `GLib.List' to `GLib.List'
  this._restore_files = value.copy();
  ^^
Compilation failed: 2 error(s), 0 warning(s)
[5/96] cc -Ideja-dup/nautilus/248796f@@dirhandling@sta -Ideja-dup/nautilus 
-I../deja-dup/nautilus -I/usr/include/libmount -I/usr/include/blkid 

[Desktop-packages] [Bug 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

[Nico Jakob]

** Description changed:

  To try the new support for EGLStreams and Wayland I have directly tried some 
programs to see how this performs. Unfortunately there are multiple problems: 
Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes 
while scrolling on normal pages).
- Also the automatic resizing when a program is moved from one display to 
another only works with system applications such as settings, terminal etc. The 
programs then are still scaled 2x on the Non-HIDPI screen.
+ Also the automatic resizing when a program is moved from one display to 
another only works with system applications such as settings, terminal etc. The 
other programs are scaled 2x on the Non-HIDPI screen.
  I am running the latest NVIDIA Drivers with 418.56.
  Is there a fix for this behaviour?
  
- Best 
+ Best
  Nicolas
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
-  GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
+  GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 11:25:53 2019
  DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia, 418.56, 5.0.0-8-generic, x86_64: installed
-  rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed
-  rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed
+  nvidia, 418.56, 5.0.0-8-generic, x86_64: installed
+  rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed
+  rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070 Ti] [1462:c303]
+  NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070 Ti] [1462:c303]
  InstallationDate: Installed on 2019-01-04 (87 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7976
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/usr/bin/zsh
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  nvidia-settings:
-  ERROR: Unable to find display on any available system
-  
-  
-  ERROR: Unable to find display on any available system
+  ERROR: Unable to find display on any available system
+ 
+  ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.

[Desktop-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.32.1-1ubuntu1

---
gnome-control-center (1:3.32.1-1ubuntu1) disco; urgency=medium

  * New upstream stable version, based on the Debian update
- Only show Bluetooth devices in Bluetooth section (lp: #1785311)
  * Remove the patches included in the new version

 -- Sebastien Bacher   Fri, 05 Apr 2019 23:01:07
+0200

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

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

Title:
  VLAN in GUI's network setting is under Bluetooth section

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  I install vlan package and  setup VLAN successfully. But when I check
  the Network settings in GUI, the created VLAN interface is under
  Bluetooth section.

  For reference, here is the screen shot of the issue.

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

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

[Desktop-packages] [Bug 1823405] Re: baobab crashed with SIGSEGV in gtk_tree_model_get_valist()

[El jinete sin cabeza]

https://gitlab.gnome.org/GNOME/baobab/issues/20

** Bug watch added: gitlab.gnome.org/GNOME/baobab/issues #20
   https://gitlab.gnome.org/GNOME/baobab/issues/20

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

Title:
  baobab crashed with SIGSEGV in gtk_tree_model_get_valist()

Status in baobab package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/baobab/issues/20

  ---

  [Impact]
  By opening the 'baobab' program and choosing to set up a u...@gmail.com 
account, and then setting up the gmail account. And I hit a click to open a 
folder of u...@gmail.com crashes 'baobab'.

  [Test Case]
  1. Open baobab
  2. Mount u...@gmail.com
  3. Wait for the content of the account u...@gmail.com to be displayed in 
baobab
  3. Select a folder of the account u...@gmail.com
  4. Click on it to display the options in that folder
  5. Select 'Open Folder'
  6. baobab crashes

  Original Description
  
  Opening a folder in baobab with connection to google drive.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: baobab 3.32.0-1
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 17:40:41 2019
  ExecutablePath: /usr/bin/baobab
  InstallationDate: Installed on 2018-12-02 (124 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/baobab --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f57537d00ee :
mov0x30(%rax),%rdi
   PC (0x7f57537d00ee) ok
   source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: baobab
  StacktraceTop:
   gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   baobab_window_open_item ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: baobab crashed with SIGSEGV in gtk_tree_model_get_valist()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 277281] Re: pptp does not start automatically in Intrepid

[C de-Avillez]

Setting WONTFIX as requested.

** Changed in: pptp-linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  pptp does not start automatically in Intrepid

Status in knetworkmanager package in Ubuntu:
  Won't Fix
Status in pptp-linux package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: knetworkmanager

  after update to Interpid pptp are not started automatically. i need to
  restart network manually.

  https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/277279

  ALSO firefox refused to show any Internet pages even after network
  restart. I need to switch off "work offline" every time.

  May be it is a but of knetworkmanager, because it can switch Firefox
  to "off-line mode"

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

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

[Desktop-packages] [Bug 277281] Re: pptp does not start automatically in Intrepid

[Morten Kjeldgaard]

This bug is still Undecided in the pptp-linux project, however, the
comment above says the bug will not be fixed but another applet is
available in KDE4 for Kubuntu 9.10. Please set to "Won't Fix"

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

Title:
  pptp does not start automatically in Intrepid

Status in knetworkmanager package in Ubuntu:
  Won't Fix
Status in pptp-linux package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: knetworkmanager

  after update to Interpid pptp are not started automatically. i need to
  restart network manually.

  https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/277279

  ALSO firefox refused to show any Internet pages even after network
  restart. I need to switch off "work offline" every time.

  May be it is a but of knetworkmanager, because it can switch Firefox
  to "off-line mode"

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

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

[Desktop-packages] [Bug 1823405] Re: baobab crashed with SIGSEGV in gtk_tree_model_get_valist()

[El jinete sin cabeza]

** Description changed:

+ [Impact]
+ By opening the 'baobab' program and choosing to set up a u...@gmail.com 
basin, and then setting up the gmail account. And I hit a click to open a 
folder of u...@gmail.com crashes 'baobab'.
+ 
+ [Test Case]
+ 1. Open baobab
+ 2. Mount u...@gmail.com
+ 3. Wait for the content of the account u...@gmail.com to be displayed in 
baobab
+ 3. Select a folder of the account u...@gmail.com
+ 4. Click on it to display the options in that folder
+ 5. Select 'Open Folder'
+ 6. baobab crashes
+ 
+ Original Description
+ 
  Opening a folder in baobab with connection to google drive.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: baobab 3.32.0-1
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 17:40:41 2019
  ExecutablePath: /usr/bin/baobab
  InstallationDate: Installed on 2018-12-02 (124 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/baobab --gapplication-service
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANGUAGE=es_CL:es
-  LANG=es_CL.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANGUAGE=es_CL:es
+  LANG=es_CL.UTF-8
  SegvAnalysis:
-  Segfault happened at: 0x7f57537d00ee :
mov0x30(%rax),%rdi
-  PC (0x7f57537d00ee) ok
-  source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
-  destination "%rdi" ok
+  Segfault happened at: 0x7f57537d00ee :
mov0x30(%rax),%rdi
+  PC (0x7f57537d00ee) ok
+  source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
+  destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: baobab
  StacktraceTop:
-  gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  baobab_window_open_item ()
-  ?? ()
-  g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  baobab_window_open_item ()
+  ?? ()
+  g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: baobab crashed with SIGSEGV in gtk_tree_model_get_valist()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Information type changed from Private to Public

** Description changed:

+ https://gitlab.gnome.org/GNOME/baobab/issues/20
+ 
+ ---
+ 
  [Impact]
  By opening the 'baobab' program and choosing to set up a u...@gmail.com 
basin, and then setting up the gmail account. And I hit a click to open a 
folder of u...@gmail.com crashes 'baobab'.
  
  [Test Case]
  1. Open baobab
  2. Mount u...@gmail.com
  3. Wait for the content of the account u...@gmail.com to be displayed in 
baobab
  3. Select a folder of the account u...@gmail.com
  4. Click on it to display the options in that folder
  5. Select 'Open Folder'
  6. baobab crashes
  
  Original Description
  
  Opening a folder in baobab with connection to google drive.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: baobab 3.32.0-1
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 17:40:41 2019
  ExecutablePath: /usr/bin/baobab
  InstallationDate: Installed on 2018-12-02 (124 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/baobab --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f57537d00ee :
mov0x30(%rax),%rdi
   PC (0x7f57537d00ee) ok
   source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: baobab
  StacktraceTop:
   gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   baobab_window_open_item ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: baobab crashed with SIGSEGV in gtk_tree_model_get_valist()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Description changed:

  https://gitlab.gnome.org/GNOME/baobab/issues/20
  
  ---
  
  [Impact]
- By opening the 'baobab' program and choosing to set up a u...@gmail.com 
basin, and then setting up the gmail account. And I hit a click to open a 
folder of 

[Desktop-packages] [Bug 277281] Re: pptp not start automatically in Intrepid

[C de-Avillez]

** Summary changed:

- pptp not starts sutomatically in Intrepid
+ pptp not start automatically in Intrepid

** Summary changed:

- pptp not start automatically in Intrepid
+ pptp does not start automatically in Intrepid

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

Title:
  pptp does not start automatically in Intrepid

Status in knetworkmanager package in Ubuntu:
  Won't Fix
Status in pptp-linux package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: knetworkmanager

  after update to Interpid pptp are not started automatically. i need to
  restart network manually.

  https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/277279

  ALSO firefox refused to show any Internet pages even after network
  restart. I need to switch off "work offline" every time.

  May be it is a but of knetworkmanager, because it can switch Firefox
  to "off-line mode"

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

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

[Desktop-packages] [Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_sc

[Treviño]

Can you please test packages from this PPA [1] and see if the issue is
fixed for you?

If not I can be even more conservative in the checks :)

 [1] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3695

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: budgie-desktop (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT
  "assertion failed: (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1748943] Re: Gnome-Terminal Giant terminal icon is blocking out the Terminal window buttons

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Gnome-Terminal Giant terminal icon is blocking out the Terminal window
  buttons

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Giant terminal icon is blocking out the Terminal window buttons

  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

  When changing from the default icon pack to any other the terminal icon 
becomes stretched across the whole window, blocking the window title buttons 
from view. 
  https://imgur.com/a/Dk6jk

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Mike Clark]

I have an identical setup and problem.

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1481835]

[Stéphane Guillou]

For the sake of completeness: confirmed in LO 6.2 with original
attachment.

Details:

Version: 6.2.2.2
Build ID: 1:6.2.2-0ubuntu0.18.04.1~lo1
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-AU (en_AU.UTF-8); UI-Language: en-US

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

Title:
  [UPSTREAM] Unable to group raster image(s) with drawing object(s)

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

Bug description:
  Steps to reproduce:
 1. Create new document in LibreOffice Writer
 2. put rester images into document and put on images some drawing objects 
(arrows, other shapes), text. 
 3. try to group images with drawing objects.

  Expected behaviour:
 User can select and group image(s) with drawing object(s)

  Actual behaviour:
 User can not select and group image(s) with drawing object(s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  Date: Wed Aug  5 18:59:59 2015
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1746585] Re: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all

[Ryan]

Hi Daniel,

Thank you for reaching out. I ran

sudo apt remove timidity*

and then rebooted. It did not fix the issue.


Thanks,

-- Ryan Viertel


On Sun, Mar 31, 2019 at 11:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Please try uninstalling 'timidity' and all 'timidity' related packages.
> Then reboot.
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746585
>
> Title:
>   [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at
>   all
>
> Status in alsa-driver package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Speakers and HDMI sound work fine, only headphones not working. I went
>   through all of the steps on
>
>   https://help.ubuntu.com/community/SoundTroubleshootingProcedure
>   https://help.ubuntu.com/community/SoundTroubleshooting
>   and
>   https://wiki.ubuntu.com/DebuggingSoundProblems
>
>   and submitted this report with ubuntu-bug -s audio
>
>   Some possibly relevant information: This installation of Ubuntu was
>   originally installed on a Dell Inspiron 15, but I cloned the partition
>   onto an SSD that I installed on the Latitude 6420. It is the Latitude
>   that is affected, the headphones work fine on the Inspiron.
>
>   Let me know if any more information is required.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
>   Uname: Linux 4.13.0-32-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
>/dev/snd/controlC0:  rviertel   2881 F pulseaudio
> rviertel   4589 F alsamixer
>   CurrentDesktop: Unity
>   Date: Wed Jan 31 12:22:17 2018
>   InstallationDate: Installed on 2015-04-27 (1009 days ago)
>   InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150218.1)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
>/dev/snd/controlC0:  rviertel   2881 F pulseaudio
> rviertel   4589 F alsamixer
>/dev/snd/seq:timidity   1191 F timidity
>   Symptom_Jack: Black Headphone Out, Left
>   Symptom_Type: No sound at all
>   Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No
> sound at all
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/11/2011
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A06
>   dmi.board.name: 0K0DNP
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A02
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Latitude E6420
>   dmi.product.version: 01
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746585/+subscriptions
>

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

Title:
  [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Speakers and HDMI sound work fine, only headphones not working. I went
  through all of the steps on

  https://help.ubuntu.com/community/SoundTroubleshootingProcedure
  https://help.ubuntu.com/community/SoundTroubleshooting
  and
  https://wiki.ubuntu.com/DebuggingSoundProblems

  and submitted this report with ubuntu-bug -s audio

  Some possibly relevant information: This installation of Ubuntu was
  originally installed on a Dell Inspiron 15, but I cloned the partition
  onto an SSD that I installed on the Latitude 6420. It is the Latitude
  that is affected, the headphones work fine on the Inspiron.

  Let me know if any more information is required.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
   /dev/snd/controlC0:  rviertel   2881 F pulseaudio
    rviertel   4589 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Jan 31 12:22:17 2018
  

[Desktop-packages] [Bug 1816808] Re: [disco] OSK does not appear under wayland when a text-entry is focused

[Timo Aaltonen]

it's not a hard requirement anymore, actually.. so, fixing cosmic is
'nice to have' if you can provide the fix and test it, but not strictly
required

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

Title:
  [disco] OSK does not appear under wayland when a text-entry is focused

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  OSK does not work properly in Wayland sessions. Besides not showing
  up, as reported in this bug report, certain characters can't be typed
  (bug #1761554).

  The proposed upload unset's the GTK_IM_MODULE variable, which fixes
  the issues.

  [Test Case]

  To confirm that the OSK works properly:

  1. Install im-config from bionic-proposed and reboot

  2. Log in to an Ubuntu on Wayland session

  3. Open gedit and enable the screen keyboard
 (Settings -> Universal Access -> Typing)

  4. When OSK shows up, confirm that you can enter accented characters
 via long-press.
 Example: long-press a and select à from the popup

 Also, confirm that certain keys for special characters result in
 correct characters. Examples: ~, √, ÷, ×, <, >, ¢

  [Fix]

  A proposed fix has been uploaded to the bionic queue.

  [Regression Potential]

  Well, this very fix did cause a regression a few months ago;
  LibreOffice and the GNOME search bar crashed when trying to use IBus
  input methods. Those issues have now been fixed.

  The change is only made for Wayland sessions, which is not default in
  18.04. Given this limitation, the regression risk is deemed to be low.

  [Original description]

  1. Login in a wayland session
  2. Open an application with a text entry (e.g. gedit)
  3. Focus gedit using the touch screen

  Expected result:
  The OSK appears

  Actual results:
  The OSK does not appear.

  ---

  This is caused by the fact that we still set GTK_IM_MODULE in Wayland.
  IIRC during the cosmic cycle we introduced a change to not set
  GTK_IM_MODULE under Wayland but we dropped it because there were users
  experiencing crashes when using libreoffice: upstream should have
  fixed those crashes to my knowledge.

  

  Also why are we setting GTK_IM_MODULE in X11 too? gnome-settings-
  daemon should be smart enough to load/unload that at run-time when
  required/not-required.

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

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

[Desktop-packages] [Bug 1823382] [NEW] backport openssl 1.1.1 fixes to bionic and cosmic

[Dimitri John Ledkov]

Public bug reported:

[Impact]

 * neon27 doesn't work with openssl 1.1.1
 * backport fixes from disco to cosmic and bionic to resolve that

[Test Case]

 * does not FTBFS

[Regression Potential]

 * currently broken in cosmic, and will break once openssl is upgraded
in bionic, so for all practical purposes it's completely busted at the
moment.

[Other Info]
 
 * Fixes already in disco and unstable.

** Affects: neon27 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: neon27 (Ubuntu Bionic)
 Importance: Undecided
 Status: In Progress

** Affects: neon27 (Ubuntu Cosmic)
 Importance: Undecided
 Status: In Progress

** Affects: neon27 (Ubuntu Disco)
 Importance: Undecided
 Status: Fix Released

** Also affects: neon27 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: neon27 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: neon27 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: neon27 (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: neon27 (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

Status in neon27 package in Ubuntu:
  Fix Released
Status in neon27 source package in Bionic:
  In Progress
Status in neon27 source package in Cosmic:
  In Progress
Status in neon27 source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

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

[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day

[Sebastien Bacher]

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: gnome-calendar (Ubuntu)
   Status: Opinion => New

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

Title:
  gnome calendar automatically moves event back 1 day

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Step to reproduce:
  1. Create an all day event
  2. Set it to repeat monthly
  --> Surprise, it goes back one day

  Additional information:
  Time belt: GMT+7

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

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

[Desktop-packages] [Bug 1823336] Re: Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake

[Sebastien Bacher]

Unsure it's really a bug, mouse wheel scrolling is supposed to scroll on
sliders and it's always a chance that you end up over a slider depending
of the UI/screen size parameters

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Critical => 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/1823336

Title:
  Scrolling the sound panel with the mouse wheel can result in sliders
  being moved by mistake

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

Bug description:
  = Steps to reproduce =

  1. Open the control center
  2. Open the sound panel
  3. Position the mouse in the middle of the panel and scroll up and down with 
the wheel
  4. If a slider box moves to be under the mouse then the slider is moved 
instead of scrolling the window

  A video to try and show this is here:
  https://www.youtube.com/watch?v=IgqP25wYymU

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

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

[Desktop-packages] [Bug 1823354] Re: printer is no longer visable

[Sebastien Bacher]

Thank you for your bug report. Could you make a screenshot showing the
issue? What printer do you use and how is it connected to the system?

** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)

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

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

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

Title:
  printer is no longer visable

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

Bug description:
  This is what system sais when I click on Printers in system settings for 
Ubuntu
  Sorry! The system printing service doesnt seem to be available

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr  5 10:33:13 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0501]
  InstallationDate: Installed on 2019-03-12 (23 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=3e6b4fed-11bf-458e-bda1-131b0681e85c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1823346] Re: SD card stays locked even when unlocked

[Sebastien Bacher]

it's more likely a kernel issue, reassigning

** Package changed: udisks2 (Ubuntu) => linux (Ubuntu)

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

Title:
  SD card stays locked even when unlocked

Status in linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  After card reader device is used with write-protected SD card, write-
  protection incorrectly persists to future SD cards, even non-protected
  ones.

  To reproduce:
  1) Insert non-protected SD card in card reader (confirm system normal):
  $ sudo hdparm -r /dev/sdd
   /dev/sdd:
readonly  =  0 (off)
  [result is correct]

  2) Eject card, set physical lock on side of card, reinsert:
  $ sudo hdparm -r /dev/sdd
  /dev/sdd:
readonly  =  1 (on)
  [result is correct - card read-only]

  3) Eject card again, unlock card, reinsert
  $ sudo hdparm -r /dev/sdd
  /dev/sdd:
readonly  =  1 (on)
  [result is **incorrect** (card still locked)]

  Because the lock is still set, the device always appears read-only.
  (For example, I cannot "dd" to /dev/sdd)

  Workaround:
  after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. 
 Then insert the unlocked card and the device will appear read/write.

  (I don't know if this is the right package to report against.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules
  Date: Fri Apr  5 14:50:32 2019
  InstallationDate: Installed on 2016-09-28 (919 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Z620 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.asset.tag: CZC4086C7Q
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: CZC4086C7Q
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

[Derk Willem te Bokkel]

just some summary thoughts in addition to point to some anomalies ..

the "failures in lightdm appear to correspond with shorter journal logs .. 
so certain processes are not running as expected .. 

plymouth also does not appear on the screen .. 
as it needs the proper graphics support ..

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+subscriptions

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

[Desktop-packages] [Bug 1823380] Re: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  was able to boot into ubuntu generic but unable to boot into regular
  mode

  would get flip_done time out if I attempted to boot normally

  Computer is dual booted with Windows 7

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: policykit-1 0.105-14.1ubuntu0.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Apr  5 13:08:57 2019
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2019-01-15 (80 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: policykit-1
  Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823380] [NEW] package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[bryan]

Public bug reported:

was able to boot into ubuntu generic but unable to boot into regular
mode

would get flip_done time out if I attempted to boot normally

Computer is dual booted with Windows 7

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: policykit-1 0.105-14.1ubuntu0.4
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Apr  5 13:08:57 2019
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2019-01-15 (80 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: policykit-1
Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  was able to boot into ubuntu generic but unable to boot into regular
  mode

  would get flip_done time out if I attempted to boot normally

  Computer is dual booted with Windows 7

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: policykit-1 0.105-14.1ubuntu0.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Apr  5 13:08:57 2019
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2019-01-15 (80 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: policykit-1
  Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_sc

[Treviño]

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

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

Title:
  [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT
  "assertion failed: (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

Cosmic verification (continued)

Now installing the updated samba packages, and rebuilding gvfs locally:

samba:
  Installed: 2:4.8.4+dfsg-2ubuntu2.2
  Candidate: 2:4.8.4+dfsg-2ubuntu2.2
  Version table:
 *** 2:4.8.4+dfsg-2ubuntu2.2 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 
Packages

gvfs:
ubuntu@ubuntu:~/deb/gvfs/gvfs-1.38.1$ grep smbc_setOptionProtocol ../build.log 
Checking for function "smbc_setOptionProtocols" : YES

$ apt-cache policy gvfs-backends
gvfs-backends:
  Installed: 1.38.1-0ubuntu1.3~andreas1
  Candidate: 1.38.1-0ubuntu1.3
  Version table:
 1.38.1-0ubuntu1.3 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 
Packages
 *** 1.38.1-0ubuntu1.3~andreas1 100
100 /var/lib/dpkg/status

Note: there is an old gvfs in proposed already, but it was NOT rebuilt
with this samba version.

Reboot, login, access windows network, and the workgroup and computer
are displayed (see attached screenshot).

Accessing the "pub" share works after authenticating, and in that case 
smbstatus shows SMB3.11 was used:
root@ubuntu:~# smbstatus

Samba version 4.8.4-Ubuntu
PID Username GroupMachine   
Protocol Version  Encryption   Signing  

2033nobody   nogroup  ubuntu (ipv4:192.168.122.79:51830)NT1 
  --
2044nobody   nogroup  ubuntu (ipv4:192.168.122.79:51834)NT1 
  --
2240nobody   nogroup  ubuntu (ipv4:192.168.122.79:51844)NT1 
  --
2420ubuntu   ubuntu   192.168.122.79 (ipv4:192.168.122.79:48332) 
SMB3_11   -partial(AES-128-CMAC)

Service  pid Machine   Connected at Encryption  
 Signing 
-
IPC$ 2044ubuntuFri Apr  5 16:07:06 2019 UTC -   
 -   
IPC$ 2033ubuntuFri Apr  5 16:07:04 2019 UTC -   
 -   
pub  2420192.168.122.79 Fri Apr  5 16:08:54 2019 UTC -  
  -   
IPC$ 2240ubuntuFri Apr  5 16:08:07 2019 UTC - 



Cosmic verification succeeded.

** Attachment added: "cosmic-windows-network-full.png"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5253146/+files/cosmic-windows-network-full.png

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

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

I think I mixed the verification-done tags, but both are done now.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

Cosmic verification

Confirming the bug:
ubuntu@ubuntu:~$ apt-cache policy samba gvfs-backends
samba:
  Installed: 2:4.8.4+dfsg-2ubuntu2.1
  Candidate: 2:4.8.4+dfsg-2ubuntu2.1
  Version table:
 *** 2:4.8.4+dfsg-2ubuntu2.1 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
...
gvfs-backends:
  Installed: 1.38.1-0ubuntu1.2
  Candidate: 1.38.1-0ubuntu1.2
  Version table:
 *** 1.38.1-0ubuntu1.2 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
...


Bug reproduced, see attached screenshot. Windows network browsing is empty.

(continued)


** Attachment added: "cosmic-windows-network-empty.png"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5253145/+files/cosmic-windows-network-empty.png

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive

[Michael Terry]

I have prepared a new beta release of deja-dup that might fix this
issue. The 39.x series has switched from GNOME's Google keys to our own
keys and from the GIO duplicity backend to the pydrive one. Which may
alleviate some of these issues (on the presumption that part of it is
that the GNOME key's quotas are being hit or how GIO is re-authorizing).

To test if the new 39.1 release helps, you can run:
snap install deja-dup --classic --beta

Or if you already had the snap installed:
snap refresh deja-dup --beta

When you next back up, you will be prompted to re-authorize deja-dup to
access your Google account (with vastly diminished access than the GNOME
keys, which is nice).

I will optimistically close the deja-dup side of this ticket. Please re-
open and comment if the above release does not help matters.

** Changed in: deja-dup
   Status: Confirmed => Fix Released

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

Title:
  Authentication error with google drive

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

Bionic verification (continued)

Now installing the new samba packages. Since I need a gvfs rebuild with
the new samba packages, I'm doing that locally.

So in the end I now have:
samba from proposed:
 *** 2:4.7.6+dfsg~ubuntu-0ubuntu2.8 500
500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages

gvfs built locally:
ubuntu@ubuntu:~/deb/gvfs/gvfs-1.36.1$ grep smbc_setOptionProtocol ../build.log 
Checking for function "smbc_setOptionProtocols": YES
gvfs-backends:
  Installed: 1.36.1-0ubuntu1.4~andreas1
  Candidate: 1.36.1-0ubuntu1.4~andreas1
  Version table:
 *** 1.36.1-0ubuntu1.4~andreas1 100
100 /var/lib/dpkg/status

I then reboot, login, and the windows network is populated with the
workgroup and the host.

I then connect to the host, and the pub share, authenticate, and smbstatus 
confirms the connection and that SMB3_11 was used:
root@ubuntu:~# smbstatus

Samba version 4.7.6-Ubuntu
PID Username GroupMachine   
Protocol Version  Encryption   Signing  

1828nobody   nogroup  ubuntu (ipv4:192.168.122.28:35678)NT1 
  --
2084nobody   nogroup  ubuntu (ipv4:192.168.122.28:35694)NT1 
  --
2093ubuntu   ubuntu   192.168.122.28 (ipv4:192.168.122.28:41040) 
SMB3_11   -partial(AES-128-CMAC)


Bionic verification succeeded.

** Attachment added: "bionic-windows-network-full.png"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5253141/+files/bionic-windows-network-full.png

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other 

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

Bionic:

full smbstatus output, showing the connection to the pub share as well:
root@ubuntu:~# smbstatus

Samba version 4.7.6-Ubuntu
PID Username GroupMachine   
Protocol Version  Encryption   Signing  

1828nobody   nogroup  ubuntu (ipv4:192.168.122.28:35678)NT1 
  --
2084nobody   nogroup  ubuntu (ipv4:192.168.122.28:35694)NT1 
  --
2093ubuntu   ubuntu   192.168.122.28 (ipv4:192.168.122.28:41040) 
SMB3_11   -partial(AES-128-CMAC)

Service  pid Machine   Connected at Encryption  
 Signing 
-
IPC$ 2084ubuntuFri Apr  5 15:33:26 2019 UTC -   
 -   
IPC$ 1828ubuntuFri Apr  5 15:31:23 2019 UTC -   
 -   
pub  2093192.168.122.28 Fri Apr  5 15:33:32 2019 UTC -  
  -   

No locked files


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

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with 

[Desktop-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

[Mohammad Kazemi]

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

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  New
Status in gnome-shell source package in Bionic:
  Triaged
Status in upower source package in Bionic:
  New
Status in gnome-shell source package in Cosmic:
  Triaged
Status in upower source package in Cosmic:
  New
Status in gnome-shell source package in Disco:
  Fix Released
Status in upower source package in Disco:
  New

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1823339] Re: Ubuntu 19.04: Simple scan found network scanner but could not connect to scanner

[Stephen Waines]

I tried to run app Port collect and it did not work

On April 5, 2019 10:15:46 AM Paul White <1823...@bugs.launchpad.net>
wrote:

> ** Package changed: ubuntu => simple-scan (Ubuntu)
>
> ** Tags added: disco
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1823339
>
> Title:
>  Ubuntu 19.04: Simple scan found network scanner but could not connect
>  to scanner
>
> Status in simple-scan package in Ubuntu:
>  New
>
> Bug description:
>  Upon trying to scan to network scanner, simple scan found the scanner
>  but could not connect to scan. Tried multiple times with a reboot in
>  b/t
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1823339/+subscriptions

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

Title:
  Ubuntu 19.04: Simple scan found network scanner but could not connect
  to scanner

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Upon trying to scan to network scanner, simple scan found the scanner
  but could not connect to scan. Tried multiple times with a reboot in
  b/t

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

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

[Desktop-packages] [Bug 1797373]

[Stéphane Guillou]

I can confirm with 6.2, although I've got a couple extras that didn't
work:

Fade, Cut, Tiles, Cube, Circles, Helix, Fall, Turn around, Iris, Turn
down, Rochade, 3D venetian, Static, Fine dissolve, Vortex, Ripple,
Glitter, Honeycomb, Newsflash.

Sometimes nothing happens, sometimes there's that tearing happening.

Removing hardware acceleration doesn't change anything.

Version: 6.2.2.2
Build ID: 1:6.2.2-0ubuntu0.18.04.1~lo1
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-AU (en_AU.UTF-8); UI-Language: en-US
Calc: threaded

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

Title:
  3D slide transitions don't work at all or tear when played + repeat
  animations don't work

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

Bug description:
  Normal effects *work*: Wipe, Wheel, Uncover, Bars, Checkers, Shape,
  Box, Wedge, Venetian, Fade, Cut, Cover, Dissolve, Comb, Push, Split,
  Diagonal.

  3D-Effects *don’t work*: Tiles, Cube, Circles, Helix, Fall, Turn
  Around, Iris, Turn Down, Rochade, 3D Venetian, Static, Fine Dissolve,
  Vortex, Ripple, Glitter, Honeycomb, Newsflash.

  Normal effects works perfectly, 3D-effects either don't work at all or when 
played with F5, shows a flashing screen.
  Tearing is also seen. Hardware acceleration is checked.
  Animations don't repeat when checked "Repeat until next slide" or "Repeat 
until next click".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 11 17:59:04 2018
  InstallationDate: Installed on 2017-10-28 (348 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (14 days ago)

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

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

[Desktop-packages] [Bug 662840] Re: Spell checking more than one language in Firefox

[Bug Watch Updater]

** Changed in: firefox
   Importance: Wishlist => 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/662840

Title:
  Spell checking more than one language in Firefox

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

Bug description:
  Binary package hint: firefox

  After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox
  capability to spell check for multiple languages in text forms. This
  is very annoying as I use two or three different languages in a single
  form when composing emails for example, and also switch between
  tabs/firefox windows to fill out forms in different languages, and now
  I have to switch between dictionaries back and forth. Never was an
  issue before.

  There is a need to set up multiple dictionaries/languages to be used
  at once for seamless spell check on a text form. Am I missing
  something?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.10+build1+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Oct 18 21:59:46 2010
  FirefoxPackages:
   firefox 3.6.10+build1+nobinonly-0ubuntu3
   firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3
   firefox-branding 3.6.10+build1+nobinonly-0ubuntu3
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Andreas Hasenack]

Bionic verification

Bug reproduced with the following packages:
ubuntu@ubuntu:~$ apt-cache policy samba gvfs-backends
samba:
...
 *** 2:4.7.6+dfsg~ubuntu-0ubuntu2.7 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
...
gvfs-backends:
...
 *** 1.36.1-0ubuntu1.3 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://br.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
...

(see attached screenshot)

** Attachment added: "bionic-windows-network-empty.png"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5253140/+files/bionic-windows-network-empty.png

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Triaged
Status in samba source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Triaged
Status in samba source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be 

[Desktop-packages] [Bug 1823363] [NEW] "Running Junk Mail Controls" does not appear in Activity Manager

[Jeb E.]

Public bug reported:

"Running Junk Mail Controls" does not appear in Activity Manager

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jeb3837 F pulseaudio
 /dev/snd/controlC1:  jeb3837 F pulseaudio
 /dev/snd/controlC0:  jeb3837 F pulseaudio
BuildID: 20190325141154
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  5 11:09:14 2019
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 2018-08-17 (231 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
 192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 192.168.86.25 
metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago)
dmi.bios.date: 09/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A880G+
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A880G+
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: BIOSTAR Group

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


** Tags: amd64 apport-bug cosmic

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

Title:
  "Running Junk Mail Controls" does not appear in Activity Manager

Status in thunderbird package in Ubuntu:
  New

Bug description:
  "Running Junk Mail Controls" does not appear in Activity Manager

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb3837 F pulseaudio
   /dev/snd/controlC1:  jeb3837 F pulseaudio
   /dev/snd/controlC0:  jeb3837 F pulseaudio
  BuildID: 20190325141154
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 11:09:14 2019
  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 2018-08-17 (231 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
   169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
   192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 
192.168.86.25 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends 

[Desktop-packages] [Bug 1823361] [NEW] WeTransfer filelink provider is missing

[Olivier Tilloy]

Public bug reported:

Upstream builds of thunderbird include the WeTransfer filelink provider.
The Ubuntu package doesn't.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: thunderbird 1:60.6.1+build2-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  osomon 2794 F pulseaudio
BuildID: 20190325095516
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  5 17:05:04 2019
EcryptfsInUse: Yes
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 2016-07-02 (1006 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2306CTO
dmi.product.sku: LENOVO_MT_2306
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

** Affects: thunderbird (Ubuntu)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged


** Tags: amd64 apport-bug disco

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

Title:
  WeTransfer filelink provider is missing

Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Upstream builds of thunderbird include the WeTransfer filelink
  provider. The Ubuntu package doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: thunderbird 1:60.6.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  osomon 2794 F pulseaudio
  BuildID: 20190325095516
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 17:05:04 2019
  EcryptfsInUse: Yes
  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 2016-07-02 (1006 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.sku: LENOVO_MT_2306
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1823354] [NEW] printer is no longer visable

[Michael Hendrick]

Public bug reported:

This is what system sais when I click on Printers in system settings for Ubuntu
Sorry! The system printing service doesnt seem to be available

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CompositorRunning: None
Date: Fri Apr  5 10:33:13 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0501]
InstallationDate: Installed on 2019-03-12 (23 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=3e6b4fed-11bf-458e-bda1-131b0681e85c ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic 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/1823354

Title:
  printer is no longer visable

Status in xorg package in Ubuntu:
  New

Bug description:
  This is what system sais when I click on Printers in system settings for 
Ubuntu
  Sorry! The system printing service doesnt seem to be available

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr  5 10:33:13 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0501]
  InstallationDate: Installed on 2019-03-12 (23 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=3e6b4fed-11bf-458e-bda1-131b0681e85c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  

[Desktop-packages] [Bug 1823322] Re: Changing Heading 1 to Heading 2 and then updating table of contents cuts of the whole Heading 2 section

[Olivier Tilloy]

Thank you for the report. This doesn't look like an Ubuntu-specific bug at a 
first glance, would you mind filing an upstream bug report at 
https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice=guided
 and sharing the link to it here?
Thanks in advance!

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

Title:
  Changing Heading 1 to Heading 2 and then updating table of contents
  cuts of the whole Heading 2 section

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
  table of contents. I've got a heading (the last heading in the
  document) which was Heading 1 (style), I think, but is now Heading 2.
  The table of contents indicates that it is Heading 1 (hence I think it
  was probably originally Heading 1), I make it Heading 2 and update the
  table of contents and the content under the heading, as well as the
  heading itself, disappears, despite the heading still being on the
  table of contents.

  I then tried changing the heading to Heading 1 and updating the index
  to see what would happen, and it becomes clear that the text is being
  cut off from the document, not that it's actually gone (the word count
  only seems to change by 2 each time this happens).

  I can't post the file since it's possible it would cause a false
  positive, as it were, with plagiarism software, and it has a lot of
  copyrighted text, but I've posted screencasts demonstrating the issue.

  Workaround: Save the file and re-open, the text that was cut off will
  now be visible again (even with the table of contents update)!

  ```
  $ snap info libreoffice
  tracking: edge
  refresh-date: 3 days ago, at 22:19 BST
  channels:
    stable:6.2.2.2 2019-03-28 (112) 548MB -
    candidate: 6.2.3.1 2019-04-02 (113) 545MB -
    beta:  ↑
    edge:  ↑
  installed:   6.2.3.1(113) 545MB -
  $ snap version
  snap2.38+git1224.5ec5133~ubuntu16.04.1
  snapd   2.38+git1224.5ec5133~ubuntu16.04.1
  series  16
  ubuntu  18.10
  kernel  4.18.0-17-generic
  $ snap info core
  tracking: edge
  refresh-date: today at 12:10 BST
  channels:
    stable:16-2.38 2019-03-28 (6673) 93MB -
    candidate: 16-2.38 2019-03-22 (6673) 93MB -
    beta:  16-2.38 2019-03-21 (6673) 93MB -
    edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
  installed:   16-2.38+git1224.5ec5133(6764) 92MB core
  ```

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

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

[Desktop-packages] [Bug 1823339] Re: Ubuntu 19.04: Simple scan found network scanner but could not connect to scanner

[Paul White]

** Package changed: ubuntu => simple-scan (Ubuntu)

** Tags added: disco

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

Title:
  Ubuntu 19.04: Simple scan found network scanner but could not connect
  to scanner

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Upon trying to scan to network scanner, simple scan found the scanner
  but could not connect to scan. Tried multiple times with a reboot in
  b/t

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

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

[Desktop-packages] [Bug 1823336] Re: Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake

[Will Cooke]

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

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Scrolling the sound panel with the mouse wheel can result in sliders
  being moved by mistake

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

Bug description:
  = Steps to reproduce =

  1. Open the control center
  2. Open the sound panel
  3. Position the mouse in the middle of the panel and scroll up and down with 
the wheel
  4. If a slider box moves to be under the mouse then the slider is moved 
instead of scrolling the window

  A video to try and show this is here:
  https://www.youtube.com/watch?v=IgqP25wYymU

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

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

[Desktop-packages] [Bug 1823339] [NEW] Ubuntu 19.04: Simple scan found network scanner but could not connect to scanner

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upon trying to scan to network scanner, simple scan found the scanner
but could not connect to scan. Tried multiple times with a reboot in b/t

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Ubuntu 19.04: Simple scan found network scanner but could not connect to scanner
https://bugs.launchpad.net/bugs/1823339
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to simple-scan 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 1637988] Re: Enable the nfs backend

[Adam Conrad]

I'm deleting this SRU from bionic-proposed to unbreak image builds.  It
can always be copied back in over itself if we decide to go ahead with
it after the MIR is completed.

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

Title:
  Enable the nfs backend

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The gio/nautilus nfs:// locations handling is missing

  * Test case
  Try to connect to/browse a nfs server from nautilus by using a nfs:// location

  * Regression potential
  It's a new backend being enabled, it shouldn't have an impact on the existing 
ones

  Note that the backend relies on libnfs which got promoted in disco and
  would need to be promoted in cosmic/bionic as well then

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

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

[Desktop-packages] [Bug 584632] Re: composer changes font mid email

[Paul White]

Upstream report was closed "RESOLVED FIXED" on 2015-03-29
Unable to reproduce with Thunderbird 60.6 in Ubuntu 18.04
No comments here or upstream for 4 years so closing as fixed

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

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

Title:
  composer changes font mid email

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: thunderbird

  As I'm typing my emails in Thunderbird, I can see what appears to be a
  font size change on screen, normally in the second line of text. The
  second line appear smaller than the first. It's barely perceptible, so
  half them time I think I am imagining it.

  Well, I've started Bccing to myself to check, and the emails I am
  receiving from myself are not only a different size, they're also a
  different font. Composer starts in some default serif, and by the
  second line is sans. I'd bee glad to email someone viz thunderbird,
  and also send along a screenshot of how it looks while I am typing.

  Thanks.

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

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

[Desktop-packages] [Bug 1823346] [NEW] SD card stays locked even when unlocked

[Andrew Kay]

Public bug reported:

Description:Ubuntu 18.04.2 LTS
Release:18.04

After card reader device is used with write-protected SD card, write-
protection incorrectly persists to future SD cards, even non-protected
ones.

To reproduce:
1) Insert non-protected SD card in card reader (confirm system normal):
$ sudo hdparm -r /dev/sdd
 /dev/sdd:
  readonly  =  0 (off)
[result is correct]

2) Eject card, set physical lock on side of card, reinsert:
$ sudo hdparm -r /dev/sdd
/dev/sdd:
  readonly  =  1 (on)
[result is correct - card read-only]

3) Eject card again, unlock card, reinsert
$ sudo hdparm -r /dev/sdd
/dev/sdd:
  readonly  =  1 (on)
[result is **incorrect** (card still locked)]

Because the lock is still set, the device always appears read-only.
(For example, I cannot "dd" to /dev/sdd)

Workaround:
after removing the locked card, issue "sudo hdparm -r0" to turn off the lock.  
Then insert the unlocked card and the device will appear read/write.

(I don't know if this is the right package to report against.)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udisks2 2.7.6-3ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules
Date: Fri Apr  5 14:50:32 2019
InstallationDate: Installed on 2016-09-28 (919 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP Z620 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago)
dmi.bios.date: 05/27/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J61 v03.88
dmi.board.asset.tag: CZC4086C7Q
dmi.board.name: 158A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 0.00
dmi.chassis.asset.tag: CZC4086C7Q
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53335X G=D
dmi.product.name: HP Z620 Workstation
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

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

Title:
  SD card stays locked even when unlocked

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  After card reader device is used with write-protected SD card, write-
  protection incorrectly persists to future SD cards, even non-protected
  ones.

  To reproduce:
  1) Insert non-protected SD card in card reader (confirm system normal):
  $ sudo hdparm -r /dev/sdd
   /dev/sdd:
readonly  =  0 (off)
  [result is correct]

  2) Eject card, set physical lock on side of card, reinsert:
  $ sudo hdparm -r /dev/sdd
  /dev/sdd:
readonly  =  1 (on)
  [result is correct - card read-only]

  3) Eject card again, unlock card, reinsert
  $ sudo hdparm -r /dev/sdd
  /dev/sdd:
readonly  =  1 (on)
  [result is **incorrect** (card still locked)]

  Because the lock is still set, the device always appears read-only.
  (For example, I cannot "dd" to /dev/sdd)

  Workaround:
  after removing the locked card, issue "sudo hdparm -r0" to turn off the lock. 
 Then insert the unlocked card and the device will appear read/write.

  (I don't know if this is the right package to report against.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 69-basler-cameras.rules 99-realsense-libusb.rules
  Date: Fri Apr  5 14:50:32 2019
  InstallationDate: Installed on 2016-09-28 (919 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Z620 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=1a9272d2-8838-4bb4-8f63-ce571641c48c ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: Upgraded to bionic on 2019-01-14 (81 days ago)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.asset.tag: CZC4086C7Q
  

[Desktop-packages] [Bug 1816808] Re: [disco] OSK does not appear under wayland when a text-entry is focused

[Gunnar Hjalmarsson]

On 2019-04-05 11:08, Timo Aaltonen wrote:
> shouldn't this be fixed in cosmic too?

Well, I skipped it since there are only three months left. If it is a
requirement, I'll do it. Please let me know.

I installed im-config 0.34-1ubuntu1.3 from bionic-proposed and verified
the test case.

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

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

Title:
  [disco] OSK does not appear under wayland when a text-entry is focused

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  OSK does not work properly in Wayland sessions. Besides not showing
  up, as reported in this bug report, certain characters can't be typed
  (bug #1761554).

  The proposed upload unset's the GTK_IM_MODULE variable, which fixes
  the issues.

  [Test Case]

  To confirm that the OSK works properly:

  1. Install im-config from bionic-proposed and reboot

  2. Log in to an Ubuntu on Wayland session

  3. Open gedit and enable the screen keyboard
 (Settings -> Universal Access -> Typing)

  4. When OSK shows up, confirm that you can enter accented characters
 via long-press.
 Example: long-press a and select à from the popup

 Also, confirm that certain keys for special characters result in
 correct characters. Examples: ~, √, ÷, ×, <, >, ¢

  [Fix]

  A proposed fix has been uploaded to the bionic queue.

  [Regression Potential]

  Well, this very fix did cause a regression a few months ago;
  LibreOffice and the GNOME search bar crashed when trying to use IBus
  input methods. Those issues have now been fixed.

  The change is only made for Wayland sessions, which is not default in
  18.04. Given this limitation, the regression risk is deemed to be low.

  [Original description]

  1. Login in a wayland session
  2. Open an application with a text entry (e.g. gedit)
  3. Focus gedit using the touch screen

  Expected result:
  The OSK appears

  Actual results:
  The OSK does not appear.

  ---

  This is caused by the fact that we still set GTK_IM_MODULE in Wayland.
  IIRC during the cosmic cycle we introduced a change to not set
  GTK_IM_MODULE under Wayland but we dropped it because there were users
  experiencing crashes when using libreoffice: upstream should have
  fixed those crashes to my knowledge.

  

  Also why are we setting GTK_IM_MODULE in X11 too? gnome-settings-
  daemon should be smart enough to load/unload that at run-time when
  required/not-required.

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

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

[Desktop-packages] [Bug 1823336] [NEW] Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake

[Will Cooke]

Public bug reported:

= Steps to reproduce =

1. Open the control center
2. Open the sound panel
3. Position the mouse in the middle of the panel and scroll up and down with 
the wheel
4. If a slider box moves to be under the mouse then the slider is moved instead 
of scrolling the window

A video to try and show this is here:
https://www.youtube.com/watch?v=IgqP25wYymU

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

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

Title:
  Scrolling the sound panel with the mouse wheel can result in sliders
  being moved by mistake

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  = Steps to reproduce =

  1. Open the control center
  2. Open the sound panel
  3. Position the mouse in the middle of the panel and scroll up and down with 
the wheel
  4. If a slider box moves to be under the mouse then the slider is moved 
instead of scrolling the window

  A video to try and show this is here:
  https://www.youtube.com/watch?v=IgqP25wYymU

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

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

[Desktop-packages] [Bug 1513282] Re: Timer resets when pausing or ending game

[Paul White]

Upstream bug showing "RESOLVED FIXED" on 2015-10-29
Checked working version 3.28 in Ubuntu 18.04
So closing as fixed.


** Changed in: gnome-mines (Ubuntu)
   Status: New => Fix Released

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

Title:
  Timer resets when pausing or ending game

Status in gnome-mines package in Ubuntu:
  Fix Released

Bug description:
  In gnome-mines 3.18.1, any action that would normally pause the timer instead 
causes it to reset to zero.  That is to say pausing the game results in a 
displayed time of zero, and finishing the game records zero to the history. 
This will led all best times to be 0, regardless of how much time you had spent 
to solve the game.
  There is an upstream bug fix for this issue here and the problem has been 
fixed in the unstable development version: 
https://bugzilla.gnome.org/show_bug.cgi?id=756302

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-mines 1:3.18.1-1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  5 05:10:50 2015
  InstallationDate: Installed on 2015-04-24 (194 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: gnome-mines
  UpgradeStatus: Upgraded to xenial on 2015-11-01 (3 days ago)

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

-- 
Mailing list: https://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 1823270] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-

[scoobbs]

Ok. I'm no expert but I will try and do it.
.
Will let you know what happens next if I do not screw it all... lol
.
Cordially,
.
Scoobbs
===//===


Em sex, 5 de abr de 2019 09:01, Timo Aaltonen 
escreveu:

> forcibly uninstall nvidia-340, then run updates and reinstall nvidia-340
> and make sure it's the new one.. or just force install the new nvidia..
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1823270
>
> Title:
>   package libgles1 (not installed) failed to install/upgrade: trying to
>   overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
>   in package nvidia-340 340.106-0ubuntu3
>
> Status in libglvnd package in Ubuntu:
>   Invalid
>
> Bug description:
>   I suppose I messed up with the package installer system programs -
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: libgles1 (not installed)
>   ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
>   Uname: Linux 4.15.0-32-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.20.9-0ubuntu7.2
>   AptOrdering:
>libglvnd-dev:amd64: Install
>libgles1:amd64: Install
>gnome-gmail:amd64: Install
>NULL: ConfigurePending
>   Architecture: amd64
>   Date: Thu Apr  4 18:51:21 2019
>   DpkgHistoryLog:
>Start-Date: 2019-04-04  18:51:19
>Commandline: packagekit role='install-packages'
>Requested-By: scoobbs (1000)
>Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic),
> gnome-gmail:amd64 (2.5.4-3)
>Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
>   DuplicateSignature:
>package:libgles1:(not installed)
>Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1)
> ...
>dpkg: error processing archive
> /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
> trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which
> is also in package nvidia-340 340.106-0ubuntu3
>   ErrorMessage: trying to overwrite
> '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package
> nvidia-340 340.106-0ubuntu3
>   InstallationDate: Installed on 2018-08-09 (238 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal,
> 3.6.7-1~18.04
>   PythonDetails: N/A
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2.1
>apt  1.6.3
>   SourcePackage: libglvnd
>   Title: package libgles1 (not installed) failed to install/upgrade:
> trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is
> also in package nvidia-340 340.106-0ubuntu3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1823270/+subscriptions
>

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  Invalid

Bug description:
  I suppose I messed up with the package installer system programs -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libglvnd-dev:amd64: Install
   libgles1:amd64: Install
   gnome-gmail:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Apr  4 18:51:21 2019
  DpkgHistoryLog:
   Start-Date: 2019-04-04  18:51:19
   Commandline: packagekit role='install-packages'
   Requested-By: scoobbs (1000)
   Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic), gnome-gmail:amd64 
(2.5.4-3)
   Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: libglvnd
  Title: package libgles1 

[Desktop-packages] [Bug 1751479] Re: On arm64, Firefox always reports download "Failed" even if it downloads successfully

[Paul White]

Upstream report closed "RESOLVED WORKSFORME" on 2019-04-04
Reporter says issue resolved, see comment #8


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

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

Title:
  On arm64, Firefox always reports download "Failed" even if it
  downloads successfully

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

Bug description:
  
  Firefox version: 
Installed: 58.0.2+build1-0ubuntu0.16.04.1
Candidate: 58.0.2+build1-0ubuntu0.16.04.1
Version table:
   *** 58.0.2+build1-0ubuntu0.16.04.1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-updates/main arm64 Packages
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-security/main arm64 Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main 
arm64 Packages

  
  Architecture: 
  Arm64 (aarch64)

  Distro (lsb_release): 
  Ubuntu xenial 16.04.4 LTS

  Desktop Environment: 
  Xfce 4.12 and Mate 1.20

  Hardware: 
  Samsung Chromebook plus with crouton (a Ubuntu Xenial chroot) installed.

  What I did:
  I want to download files in Firefox. Just open any website, click "Download" 
link.

  Actual results:
  I can not see my downloading items on browser panel, it just says "No 
downloads for this session". What's more, if I click  "Show all downloads", I 
can see my downloading items whose status is "Failed". However, I can confirm 
it's downloading background successfully, and the downloaded file appears on my 
computer. I tried to remove my profile, say, the ".mozilla" folder, and 
downloaded again, but nothing improved.

  Expected results:
  It should download successfully. I just downgrade my Firefox to 57.x, 
everything is fine, and this downloading issue is gone.

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

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

[Desktop-packages] [Bug 1823270] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340

[Timo Aaltonen]

forcibly uninstall nvidia-340, then run updates and reinstall nvidia-340
and make sure it's the new one.. or just force install the new nvidia..

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  Invalid

Bug description:
  I suppose I messed up with the package installer system programs -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libglvnd-dev:amd64: Install
   libgles1:amd64: Install
   gnome-gmail:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Apr  4 18:51:21 2019
  DpkgHistoryLog:
   Start-Date: 2019-04-04  18:51:19
   Commandline: packagekit role='install-packages'
   Requested-By: scoobbs (1000)
   Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic), gnome-gmail:amd64 
(2.5.4-3)
   Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2)
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823322] Re: Changing Heading 1 to Heading 2 and then updating table of contents cuts of the whole Heading 2 section

[Ads20000]

** Summary changed:

- Changing Heading 1 to Heading 2 and then updating table of contents deletes 
the whole Heading 2 section
+ Changing Heading 1 to Heading 2 and then updating table of contents cuts of 
the whole Heading 2 section

** Description changed:

  I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
  table of contents. I've got a heading (the last heading in the document)
  which was Heading 1 (style), I think, but is now Heading 2. The table of
  contents indicates that it is Heading 1 (hence I think it was probably
  originally Heading 1), I make it Heading 2 and update the table of
  contents and the content under the heading, as well as the heading
  itself, disappears, despite the heading still being on the table of
  contents.
  
  I then tried changing the heading to Heading 1 and updating the index to
  see what would happen, and it becomes clear that the text is being cut
  off from the document, not that it's actually gone (the word count only
  seems to change by 2 each time this happens).
  
  I can't post the file since it's possible it would cause a false
  positive, as it were, with plagiarism software, and it has a lot of
  copyrighted text, but I've posted screencasts demonstrating the issue.
  
+ Workaround: Save the file and re-open, the text that was cut off will
+ now be visible again (even with the table of contents update)!
+ 
  ```
  $ snap info libreoffice
  tracking: edge
  refresh-date: 3 days ago, at 22:19 BST
  channels:
-   stable:6.2.2.2 2019-03-28 (112) 548MB -
-   candidate: 6.2.3.1 2019-04-02 (113) 545MB -
-   beta:  ↑  
-   edge:  ↑  
+   stable:6.2.2.2 2019-03-28 (112) 548MB -
+   candidate: 6.2.3.1 2019-04-02 (113) 545MB -
+   beta:  ↑
+   edge:  ↑
  installed:   6.2.3.1(113) 545MB -
  $ snap version
  snap2.38+git1224.5ec5133~ubuntu16.04.1
  snapd   2.38+git1224.5ec5133~ubuntu16.04.1
  series  16
  ubuntu  18.10
  kernel  4.18.0-17-generic
  $ snap info core
  tracking: edge
  refresh-date: today at 12:10 BST
  channels:
-   stable:16-2.38 2019-03-28 (6673) 93MB -
-   candidate: 16-2.38 2019-03-22 (6673) 93MB -
-   beta:  16-2.38 2019-03-21 (6673) 93MB -
-   edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
+   stable:16-2.38 2019-03-28 (6673) 93MB -
+   candidate: 16-2.38 2019-03-22 (6673) 93MB -
+   beta:  16-2.38 2019-03-21 (6673) 93MB -
+   edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
  installed:   16-2.38+git1224.5ec5133(6764) 92MB core
  ```

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

Title:
  Changing Heading 1 to Heading 2 and then updating table of contents
  cuts of the whole Heading 2 section

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
  table of contents. I've got a heading (the last heading in the
  document) which was Heading 1 (style), I think, but is now Heading 2.
  The table of contents indicates that it is Heading 1 (hence I think it
  was probably originally Heading 1), I make it Heading 2 and update the
  table of contents and the content under the heading, as well as the
  heading itself, disappears, despite the heading still being on the
  table of contents.

  I then tried changing the heading to Heading 1 and updating the index
  to see what would happen, and it becomes clear that the text is being
  cut off from the document, not that it's actually gone (the word count
  only seems to change by 2 each time this happens).

  I can't post the file since it's possible it would cause a false
  positive, as it were, with plagiarism software, and it has a lot of
  copyrighted text, but I've posted screencasts demonstrating the issue.

  Workaround: Save the file and re-open, the text that was cut off will
  now be visible again (even with the table of contents update)!

  ```
  $ snap info libreoffice
  tracking: edge
  refresh-date: 3 days ago, at 22:19 BST
  channels:
    stable:6.2.2.2 2019-03-28 (112) 548MB -
    candidate: 6.2.3.1 2019-04-02 (113) 545MB -
    beta:  ↑
    edge:  ↑
  installed:   6.2.3.1(113) 545MB -
  $ snap version
  snap2.38+git1224.5ec5133~ubuntu16.04.1
  snapd   2.38+git1224.5ec5133~ubuntu16.04.1
  series  16
  ubuntu  18.10
  kernel  4.18.0-17-generic
  $ snap info core
  tracking: edge
  refresh-date: today at 12:10 BST
  channels:
    stable:16-2.38 2019-03-28 (6673) 93MB -
    candidate: 16-2.38 2019-03-22 (6673) 93MB -
    beta:  16-2.38 2019-03-21 (6673) 93MB -
    edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
  

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

[Derk Willem te Bokkel]

I've been merrily switching between OS's without this kind of issue for more 
than 10 years .. 
the behaviour changed recently in the last 30 days .. 
it was fine prior to that .. 
This is a regression bug and will annoy anyone working with multiple instances 
of disco xubuntu for testing..

yes it is particular to intel graphics.. i915 based

I have another older laptop amd/ati based which does not react this was
way

no it is not a show stopper except when the power button refuses to
work..

I'm trying to figure it out .. thus the questions.. sorry if that is
inappropriate.

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To 

[Desktop-packages] [Bug 1823322] Re: Changing Heading 1 to Heading 2 and then updating table of contents deletes the whole Heading 2 section

[Ads20000]

** Attachment added: "Heading 1 update bug"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1823322/+attachment/5253052/+files/Screencast%20from%2005-04-19%2012%3A40%3A22.webm

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

Title:
  Changing Heading 1 to Heading 2 and then updating table of contents
  cuts of the whole Heading 2 section

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
  table of contents. I've got a heading (the last heading in the
  document) which was Heading 1 (style), I think, but is now Heading 2.
  The table of contents indicates that it is Heading 1 (hence I think it
  was probably originally Heading 1), I make it Heading 2 and update the
  table of contents and the content under the heading, as well as the
  heading itself, disappears, despite the heading still being on the
  table of contents.

  I then tried changing the heading to Heading 1 and updating the index
  to see what would happen, and it becomes clear that the text is being
  cut off from the document, not that it's actually gone (the word count
  only seems to change by 2 each time this happens).

  I can't post the file since it's possible it would cause a false
  positive, as it were, with plagiarism software, and it has a lot of
  copyrighted text, but I've posted screencasts demonstrating the issue.

  Workaround: Save the file and re-open, the text that was cut off will
  now be visible again (even with the table of contents update)!

  ```
  $ snap info libreoffice
  tracking: edge
  refresh-date: 3 days ago, at 22:19 BST
  channels:
    stable:6.2.2.2 2019-03-28 (112) 548MB -
    candidate: 6.2.3.1 2019-04-02 (113) 545MB -
    beta:  ↑
    edge:  ↑
  installed:   6.2.3.1(113) 545MB -
  $ snap version
  snap2.38+git1224.5ec5133~ubuntu16.04.1
  snapd   2.38+git1224.5ec5133~ubuntu16.04.1
  series  16
  ubuntu  18.10
  kernel  4.18.0-17-generic
  $ snap info core
  tracking: edge
  refresh-date: today at 12:10 BST
  channels:
    stable:16-2.38 2019-03-28 (6673) 93MB -
    candidate: 16-2.38 2019-03-22 (6673) 93MB -
    beta:  16-2.38 2019-03-21 (6673) 93MB -
    edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
  installed:   16-2.38+git1224.5ec5133(6764) 92MB core
  ```

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

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

[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day

[Toan Nguyen]

I don't really understand your question so I recorded the steps to
reproduce the bug. Please note that no matter the event is 'personal' or
sync with gmail, this bug still happens.

** Attachment added: "Steps to reproduce"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+attachment/5253050/+files/calendar_bug-2019-04-05_18.34.24.mp4

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

Title:
  gnome calendar automatically moves event back 1 day

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  Step to reproduce:
  1. Create an all day event
  2. Set it to repeat monthly
  --> Surprise, it goes back one day

  Additional information:
  Time belt: GMT+7

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

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

[Desktop-packages] [Bug 1823322] [NEW] Changing Heading 1 to Heading 2 and then updating table of contents cuts of the whole Heading 2 section

[Ads20000]

Public bug reported:

I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
table of contents. I've got a heading (the last heading in the document)
which was Heading 1 (style), I think, but is now Heading 2. The table of
contents indicates that it is Heading 1 (hence I think it was probably
originally Heading 1), I make it Heading 2 and update the table of
contents and the content under the heading, as well as the heading
itself, disappears, despite the heading still being on the table of
contents.

I then tried changing the heading to Heading 1 and updating the index to
see what would happen, and it becomes clear that the text is being cut
off from the document, not that it's actually gone (the word count only
seems to change by 2 each time this happens).

I can't post the file since it's possible it would cause a false
positive, as it were, with plagiarism software, and it has a lot of
copyrighted text, but I've posted screencasts demonstrating the issue.

Workaround: Save the file and re-open, the text that was cut off will
now be visible again (even with the table of contents update)!

```
$ snap info libreoffice
tracking: edge
refresh-date: 3 days ago, at 22:19 BST
channels:
  stable:6.2.2.2 2019-03-28 (112) 548MB -
  candidate: 6.2.3.1 2019-04-02 (113) 545MB -
  beta:  ↑
  edge:  ↑
installed:   6.2.3.1(113) 545MB -
$ snap version
snap2.38+git1224.5ec5133~ubuntu16.04.1
snapd   2.38+git1224.5ec5133~ubuntu16.04.1
series  16
ubuntu  18.10
kernel  4.18.0-17-generic
$ snap info core
tracking: edge
refresh-date: today at 12:10 BST
channels:
  stable:16-2.38 2019-03-28 (6673) 93MB -
  candidate: 16-2.38 2019-03-22 (6673) 93MB -
  beta:  16-2.38 2019-03-21 (6673) 93MB -
  edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
installed:   16-2.38+git1224.5ec5133(6764) 92MB core
```

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


** Tags: cosmic snap

** Attachment added: "Heading 2 update bug"
   
https://bugs.launchpad.net/bugs/1823322/+attachment/5253051/+files/Screencast%20from%2005-04-19%2012%3A38%3A13.webm

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

Title:
  Changing Heading 1 to Heading 2 and then updating table of contents
  cuts of the whole Heading 2 section

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
  table of contents. I've got a heading (the last heading in the
  document) which was Heading 1 (style), I think, but is now Heading 2.
  The table of contents indicates that it is Heading 1 (hence I think it
  was probably originally Heading 1), I make it Heading 2 and update the
  table of contents and the content under the heading, as well as the
  heading itself, disappears, despite the heading still being on the
  table of contents.

  I then tried changing the heading to Heading 1 and updating the index
  to see what would happen, and it becomes clear that the text is being
  cut off from the document, not that it's actually gone (the word count
  only seems to change by 2 each time this happens).

  I can't post the file since it's possible it would cause a false
  positive, as it were, with plagiarism software, and it has a lot of
  copyrighted text, but I've posted screencasts demonstrating the issue.

  Workaround: Save the file and re-open, the text that was cut off will
  now be visible again (even with the table of contents update)!

  ```
  $ snap info libreoffice
  tracking: edge
  refresh-date: 3 days ago, at 22:19 BST
  channels:
    stable:6.2.2.2 2019-03-28 (112) 548MB -
    candidate: 6.2.3.1 2019-04-02 (113) 545MB -
    beta:  ↑
    edge:  ↑
  installed:   6.2.3.1(113) 545MB -
  $ snap version
  snap2.38+git1224.5ec5133~ubuntu16.04.1
  snapd   2.38+git1224.5ec5133~ubuntu16.04.1
  series  16
  ubuntu  18.10
  kernel  4.18.0-17-generic
  $ snap info core
  tracking: edge
  refresh-date: today at 12:10 BST
  channels:
    stable:16-2.38 2019-03-28 (6673) 93MB -
    candidate: 16-2.38 2019-03-22 (6673) 93MB -
    beta:  16-2.38 2019-03-21 (6673) 93MB -
    edge:  16-2.38+git1224.5ec5133 2019-04-05 (6764) 92MB -
  installed:   16-2.38+git1224.5ec5133(6764) 92MB core
  ```

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

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

[Desktop-packages] [Bug 1751479]

[Justin Yang]

Hi, all;

I find this issue is gone recently by using the latest version of
Firefox on ArchlinuxArm. Not sure what happened, but it works now.
Thanks.

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

Title:
  On arm64, Firefox always reports download "Failed" even if it
  downloads successfully

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  New

Bug description:
  
  Firefox version: 
Installed: 58.0.2+build1-0ubuntu0.16.04.1
Candidate: 58.0.2+build1-0ubuntu0.16.04.1
Version table:
   *** 58.0.2+build1-0ubuntu0.16.04.1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-updates/main arm64 Packages
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-security/main arm64 Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main 
arm64 Packages

  
  Architecture: 
  Arm64 (aarch64)

  Distro (lsb_release): 
  Ubuntu xenial 16.04.4 LTS

  Desktop Environment: 
  Xfce 4.12 and Mate 1.20

  Hardware: 
  Samsung Chromebook plus with crouton (a Ubuntu Xenial chroot) installed.

  What I did:
  I want to download files in Firefox. Just open any website, click "Download" 
link.

  Actual results:
  I can not see my downloading items on browser panel, it just says "No 
downloads for this session". What's more, if I click  "Show all downloads", I 
can see my downloading items whose status is "Failed". However, I can confirm 
it's downloading background successfully, and the downloaded file appears on my 
computer. I tried to remove my profile, say, the ".mozilla" folder, and 
downloaded again, but nothing improved.

  Expected results:
  It should download successfully. I just downgrade my Firefox to 57.x, 
everything is fine, and this downloading issue is gone.

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

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

[Desktop-packages] [Bug 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

[Nico Jakob]

And funny sidenode which may be also relevant:
nvidia-settings gives me an empty program.

** Attachment added: "Bildschirmfoto vom 2019-04-05 13-22-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1822754/+attachment/5253049/+files/Bildschirmfoto%20vom%202019-04-05%2013-22-58.png

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

Title:
  Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  To try the new support for EGLStreams and Wayland I have directly tried some 
programs to see how this performs. Unfortunately there are multiple problems: 
Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes 
while scrolling on normal pages).
  Also the automatic resizing when a program is moved from one display to 
another only works with system applications such as settings, terminal etc. The 
programs then are still scaled 2x on the Non-HIDPI screen.
  I am running the latest NVIDIA Drivers with 418.56.
  Is there a fix for this behaviour?

  Best 
  Nicolas

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 11:25:53 2019
  DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-8-generic, x86_64: installed
   rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed
   rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070 Ti] [1462:c303]
  InstallationDate: Installed on 2019-01-04 (87 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7976
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1751479] Re: On arm64, Firefox always reports download "Failed" even if it downloads successfully

[Bug Watch Updater]

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

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

Title:
  On arm64, Firefox always reports download "Failed" even if it
  downloads successfully

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  New

Bug description:
  
  Firefox version: 
Installed: 58.0.2+build1-0ubuntu0.16.04.1
Candidate: 58.0.2+build1-0ubuntu0.16.04.1
Version table:
   *** 58.0.2+build1-0ubuntu0.16.04.1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-updates/main arm64 Packages
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-security/main arm64 Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main 
arm64 Packages

  
  Architecture: 
  Arm64 (aarch64)

  Distro (lsb_release): 
  Ubuntu xenial 16.04.4 LTS

  Desktop Environment: 
  Xfce 4.12 and Mate 1.20

  Hardware: 
  Samsung Chromebook plus with crouton (a Ubuntu Xenial chroot) installed.

  What I did:
  I want to download files in Firefox. Just open any website, click "Download" 
link.

  Actual results:
  I can not see my downloading items on browser panel, it just says "No 
downloads for this session". What's more, if I click  "Show all downloads", I 
can see my downloading items whose status is "Failed". However, I can confirm 
it's downloading background successfully, and the downloaded file appears on my 
computer. I tried to remove my profile, say, the ".mozilla" folder, and 
downloaded again, but nothing improved.

  Expected results:
  It should download successfully. I just downgrade my Firefox to 57.x, 
everything is fine, and this downloading issue is gone.

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

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

[Desktop-packages] [Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

[Didier Roche]

https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365502
doesn't fix it.

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

Title:
  [regression][nvidia] All on screen text is tiny. Icons are normal size
  but text is nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Triaged
Status in mutter source package in Disco:
  Triaged
Status in nvidia-graphics-drivers-418 source package in Disco:
  Confirmed

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

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

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

[Desktop-packages] [Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

[Didier Roche]

FYI, this happens even without drm enabled and only on Xorg session.
Alt+F2 -> r fixes it until next reboot.

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

Title:
  [regression][nvidia] All on screen text is tiny. Icons are normal size
  but text is nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Triaged
Status in mutter source package in Disco:
  Triaged
Status in nvidia-graphics-drivers-418 source package in Disco:
  Confirmed

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

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

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

[Desktop-packages] [Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1

[Didier Roche]

-> I'm using 2 monitors (1 internal and 1 external).
-> The nvidia GPU is enabled, monitor is plugged to it through HDMI.
-> The CPU usage of GNOME Shell spikes. There is no writed at the same time 
(the led doesn't blink) and no other process seems to run for it. The memory 
usages seems stable though. See log attachement which is a snapshot of CPU and 
MEM usage every second (you can see at the end a freeze for multiple seconds 
corresponding to GNOME Shell CPU spike). CPU spike can go up to 200%.
-> I've run a wayland session for a period of time and didn't notice any 
issues. So seems Xorg specific.

Note that this is a regression as I'm running Xorg + drm modeset for a
year or so without experiencing that previously.


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

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

Title:
  [nvidia] Shell hangs up at random times when using nvidia-
  drm.modeset=1

Status in mutter package in Ubuntu:
  New

Bug description:
  Mutter is hanging for multiple seconds (5 or so) at random times, especially 
when your user session starts and you open new applications from the launcher:
  - the screen freeze (apps & Shell) completely
  - you have a second cursor that you can move and refresh during that period

  It seems that disabling drm nvidia support prevent the issue from
  happening so far. More update if it's not the case anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 10:21:09 2019
  InstallationDate: Installed on 2018-05-24 (315 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-01-08 (86 days ago)

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

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

[Desktop-packages] [Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1

[Didier Roche]

** Attachment added: "cpu_mem.logs"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+attachment/5253048/+files/cpu_mem.logs

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

Title:
  [nvidia] Shell hangs up at random times when using nvidia-
  drm.modeset=1

Status in mutter package in Ubuntu:
  New

Bug description:
  Mutter is hanging for multiple seconds (5 or so) at random times, especially 
when your user session starts and you open new applications from the launcher:
  - the screen freeze (apps & Shell) completely
  - you have a second cursor that you can move and refresh during that period

  It seems that disabling drm nvidia support prevent the issue from
  happening so far. More update if it's not the case anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 10:21:09 2019
  InstallationDate: Installed on 2018-05-24 (315 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-01-08 (86 days ago)

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

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

[Desktop-packages] [Bug 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

[Nico Jakob]

Ok thank you and sorry for the late reply I caught a cold over the last
days:

This is after installing the mutter builds:
➜ dpkg -l | grep 'mutter'   
ii  gir1.2-mutter-4:amd64  3.32.0-1 
amd64GObject introspection data for Mutter
ii  libmutter-4-0:amd643.32.0-1 
amd64window manager library from the Mutter window manager
ii  libmutter-4-0-dbgsym:amd64 3.32.0-1 
amd64debug symbols for libmutter-4-0
ii  libmutter-4-dev:amd64  3.32.0-1 
amd64Development files for the Mutter window manager
ii  mutter 3.32.0-1 
amd64lightweight GTK+ window manager
ii  mutter-common  3.32.0-1 
all  shared files for the Mutter window manager
ii  mutter-dbgsym  3.32.0-1 
amd64debug symbols for mutter

Unfortunately Chrome,Firefox and other programs seem to run only
software accelerated and do not adjust their scaling for example if
moved from screen A (HiDPI) to screen B (low-DPI).


** Attachment added: "Here is the glxinfo.txt run during opened Chrome with one 
Window on each screen opened, so one is correctly scaled (on HIDPI) and one 
twice as large on screen 2"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1822754/+attachment/5253043/+files/glxinfo.txt

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

Title:
  Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  To try the new support for EGLStreams and Wayland I have directly tried some 
programs to see how this performs. Unfortunately there are multiple problems: 
Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes 
while scrolling on normal pages).
  Also the automatic resizing when a program is moved from one display to 
another only works with system applications such as settings, terminal etc. The 
programs then are still scaled 2x on the Non-HIDPI screen.
  I am running the latest NVIDIA Drivers with 418.56.
  Is there a fix for this behaviour?

  Best 
  Nicolas

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 11:25:53 2019
  DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-8-generic, x86_64: installed
   rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed
   rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070 Ti] [1462:c303]
  InstallationDate: Installed on 2019-01-04 (87 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7976
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.sku: Default string
  

[Desktop-packages] [Bug 1822754] Re: Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

[Nico Jakob]

Forgot to mention: I did of course restart after installing the new
mutter packages.

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

Title:
  Chrome and other programs not resizing on HiDPI and Non-Hidpi setup

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  To try the new support for EGLStreams and Wayland I have directly tried some 
programs to see how this performs. Unfortunately there are multiple problems: 
Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes 
while scrolling on normal pages).
  Also the automatic resizing when a program is moved from one display to 
another only works with system applications such as settings, terminal etc. The 
programs then are still scaled 2x on the Non-HIDPI screen.
  I am running the latest NVIDIA Drivers with 418.56.
  Is there a fix for this behaviour?

  Best 
  Nicolas

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 11:25:53 2019
  DistUpgraded: 2019-03-31 23:11:06,205 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-8-generic, x86_64: installed
   rtl8814au, 4.3.21, 4.18.0-16-generic, x86_64: installed
   rtl8814au, 4.3.21, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070 Ti] [1462:c303]
  InstallationDate: Installed on 2019-01-04 (87 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7976
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=UUID=367ba2c7-63e9-46a2-9d19-aa86d3dcc21d ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-03-31 (1 days ago)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1823319] [NEW] syslog reporting a lot of "org.gnome.Shell" fail error and laptop hanging

[Hemanta Kumar G]

Public bug reported:

syslog reporting a lot of "org.gnome.Shell" fail error and laptop
hanging

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_46_49_generic_49
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Fri Apr  5 16:33:17 2019
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2019-03-18 (18 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  syslog reporting a lot of "org.gnome.Shell" fail error and laptop
  hanging

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  syslog reporting a lot of "org.gnome.Shell" fail error and laptop
  hanging

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_46_49_generic_49
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Fri Apr  5 16:33:17 2019
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-03-18 (18 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day

[Sebastien Bacher]

What type of calendar? Local? webdav? outlook?

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

Title:
  gnome calendar automatically moves event back 1 day

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  Step to reproduce:
  1. Create an all day event
  2. Set it to repeat monthly
  --> Surprise, it goes back one day

  Additional information:
  Time belt: GMT+7

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

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

[Desktop-packages] [Bug 1823176] Re: After connecting the usb docking station, the gnome-shell process loads one processor core 100%

[Sebastien Bacher]

Could you add your journalctl log when getting the issue?

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

Title:
  After connecting the usb docking station, the gnome-shell process
  loads one processor core 100%

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After connecting the usb docking station, the gnome-shell process
  loads one processor core 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 20:15:25 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-20 (15 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when using zsh

[Daniel van Vugt]

BTW, Didier is now using bug 1823301 instead.

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

Title:
  gnome-shell high memory and CPU usage when using zsh

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete
Status in gnome-shell source package in Disco:
  Incomplete
Status in gnome-shell-extension-desktop-icons source package in Disco:
  Incomplete
Status in zsh source package in Disco:
  Incomplete

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1821849] Re: LibreOffice Impress 6.2.2.2 Embedded Video Problem

[Sam Colegrove]

That is indeed interesting that Ubuntu 19.04 does not have this 
problem.  I have just install the latest build of Kubuntu 19.04 into 
another partition of my HP Spectre x360 15-ch004ng which has a 1TB SSD.  
I tested the video after all the latest LibreOffice updates and it still 
gave the same problems that I reported. Basically, when a video is 
started the display goes full screen and is a mess.

On 05/04/19 19:38, Olivier Tilloy wrote:
> In comment #4 I stated that I am testing on disco.
>
> Unless otherwise noted, a bug against a source package on Launchpad
> always targets the current development series (i.e. at the moment 19.04,
> aka Disco).
>
> I have been testing on stock Ubuntu though (with GNOME), not Kubuntu.
>

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

Title:
  LibreOffice Impress 6.2.2.2 Embedded Video Problem

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The following bugs are for LibreOffice 6.2.2.2 Impress on Kubuntu
  19.04.

  When I start a slide-show with Impress by using either F5 or Shift F5,
  I get a white screen.  When I click on it, the slide is displayed.
  When I exit the presentation with say "Esc", soffice.bin is in the
  taskbar with the odp file used for the presentation.  If I click on
  the odp file and exit, both tasks are removed.

  Now when I advance to an embedded video I get the image shown with
  this report. When the video is started, the previous slide is shown on
  top of the video as it is being played. Not a good view This
  happens when either starting from the first slide or the one preceding
  embedded video.

  I have tried the gtk3 options in https://launchpad.net/bugs/1820062
  and the changes make no difference to this problem.  I have also
  installed gstreamer1.0-plugins-* which solved  previous problem with
  LibreOffice.

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

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

[Desktop-packages] [Bug 545778] Re: xul-ext-lightning is only available in English

[Olivier Tilloy]

** Changed in: thunderbird (Ubuntu)
   Importance: Medium => High

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

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

[Desktop-packages] [Bug 1228906] Re: Lightning not available even though xul-ext-lightning is installed

[Olivier Tilloy]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Thunderbird since that
time.

As of today in Ubuntu 19.04, installing xul-ext-lightning makes the
calendar work in thunderbird, I suspect what happened at the time this
bug was reported is that thunderbird and the lightning extension got out
of sync.

Thunderbird now ships lightning by default, so we are going to reflect
that in the packaging, meaning such a situation should never happen
again.

Thanks for the report, and sorry for the lack of feedback.

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

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

Title:
  Lightning not available even though xul-ext-lightning is installed

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  After the update of Thunderbird and Lightning from version 17 to 24,
  Thunderbird does not show anymore the calendar pane or tab. All the
  calendar function that should be made available from Lightning are not
  available even from the menus.

  It seems that Thunderbird does not realize that the Lightning add-on
  is available system-wide. The add-ons pane shows that no add-ons are
  installed. In the previous versions system-wide add-ons were displayed
  along the others installed by the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xul-ext-lightning 1:24.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20
  Uname: Linux 3.5.0-40-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1674 F pulseaudio
   /dev/snd/pcmC0D0p:   gioele 1674 F...m pulseaudio
  BuildID: 20130913150425
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 43'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1462f603,0012'
 Controls  : 49
 Simple ctrls  : 22
  Channel: Unavailable
  Date: Sun Sep 22 20:15:19 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
  IpRoute:
   default via 192.168.61.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.61.0/24 dev eth0  proto kernel  scope link  src 192.168.61.21  
metric 1
  IwConfig:
   sit0  no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MarkForUpload: True
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.utf8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=24.0/20130913150425 (In use)
  RelatedPackageVersions:
   adobe-flashplugin 11.2.202.310-0precise1
   rhythmbox-mozilla 2.96-0ubuntu4.3
   totem-mozilla 3.0.1-0ubuntu21.1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to precise on 2013-05-24 (120 days ago)
  dmi.bios.date: 101507
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.5
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7276
  dmi.board.vendor: MSI
  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.:bvrV3.5:bd101507:svnToBeFilledByO.E.M.:pnMS-7276:pvr1.0:rvnMSI:rnMS-7276:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7276
  dmi.product.version: 1.0
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1822513] Re: [regression] gnome-shell aspect ratio doesn't rotate with the rest of the screen

[Daniel van Vugt]

https://git.launchpad.net/~ubuntu-
desktop/ubuntu/+source/mutter/commit/?id=c7befcdb9cdc9916351cba36b41568c44d11b16d


** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [regression] gnome-shell aspect ratio doesn't rotate with the rest of
  the screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I'm testing 19.04 on an Acer-One S1003. An interesting quirk of that
  tablet is that the default screen orientation is portrait (as can be
  seen in BIOS setup, grub etc.)

  Ubuntu 19.04 support screen rotation out of the box. But after a
  recent update, the landscape mode is broken.

  In landscape, only the left hand portion the screen displays an image.
  The right hand part is black.

  The part that's shown is about as wide as the screen would be in
  portrait orientation.

  Another quirk is that landscape screenshots (taken with printscreen) have a 
portrait size, with some garbage at the bottom.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1821160] Re: Desktop freezes refuses input

[Recep GUCLUER]

No freezes. Can be closed. I can not reproduce the freeze.

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

Title:
  Desktop freezes refuses input

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  At random intervals desktop freezes. mouse does not function. Sometimes 
Alt+Tab works.
  I use virtualbox. Sometimes it captures the mouse and dont release it, and it 
take a few seconds to recognise that.
  I release the mouse with rigt Ctrl, that shows to pointer and I can move it.
  But click does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 21 12:34:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RV710 [Radeon HD 4350/4550] [1043:0274]
  InstallationDate: Installed on 2019-03-16 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=3b8dc91d-1d7d-412f-ba84-ebeb03723557 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1

[Daniel van Vugt]

Didier:

 * Are you using multiple monitors?

 * Which GPUs have a monitor plugged in?

 * (from an SSH login) Do you see high CPU or memory usage of the gnome-
shell process?

 * Is the problem only Xorg sessions, only Wayland sessions, or both?

** Tags added: nvidia-drm.modeset

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

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

Title:
  [nvidia] Shell hangs up at random times when using nvidia-
  drm.modeset=1

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Mutter is hanging for multiple seconds (5 or so) at random times, especially 
when your user session starts and you open new applications from the launcher:
  - the screen freeze (apps & Shell) completely
  - you have a second cursor that you can move and refresh during that period

  It seems that disabling drm nvidia support prevent the issue from
  happening so far. More update if it's not the case anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 10:21:09 2019
  InstallationDate: Installed on 2018-05-24 (315 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-01-08 (86 days ago)

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

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

[Desktop-packages] [Bug 1822838] Re: [regression][nvidia] gnome-shell is very large

[Daniel van Vugt]

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

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

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

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

Title:
  [regression][nvidia] gnome-shell is very large

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

Bug description:
  Everything from gnome-shell is very large.

  I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled
  extensions, checked scaling, deleted setting files, nothing worked.

  I created a new user, gnome-shell has the same issue in the beginning. Alt + 
F2 resets shell to normal size, but on logout/login everything is large again. 
This doesn't work on my user tho.
  Notifications, etc are extremely large.

  Just everything from the shell is like 40% larger than it should be.
  This also happens with default themes, settings, etc.

  Screenshot: https://imgur.com/a/oo5I7lZ

  gnome-shell: 3.32.0
  OS: Ubuntu 19.04 Development Branch

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:14:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-09 (82 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago)

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

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

[Desktop-packages] [Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

[Daniel van Vugt]

** Changed in: nvidia-graphics-drivers-418 (Ubuntu Disco)
   Importance: Undecided => High

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

Title:
  [regression][nvidia] All on screen text is tiny. Icons are normal size
  but text is nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Triaged
Status in mutter source package in Disco:
  Triaged
Status in nvidia-graphics-drivers-418 source package in Disco:
  Confirmed

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

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

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

[Desktop-packages] [Bug 1818987] Re: broken symlink to changelog.Debian.gz in chromium-browser

[Olivier Tilloy]

Ah, I see what you mean now, sorry I had misunderstood.

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

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

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

Title:
  broken symlink to changelog.Debian.gz in chromium-browser

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
  which has to do with saving space, for some reason, the chromium-
  browser has its changelog symlinked to an optional package.

  Version: 72.0.3626.119-0ubuntu0.18

  Right now, I have chromium-codecs-ffmpeg installed, but the changelog
  links to documentation in chromium-codecs-ffmpeg-extra.

  ```
  $ dpkg -L chromium-browser | grep changelog.Debian
  /usr/share/doc/chromium-browser/changelog.Debian.gz

  $ dpkg -l | grep chromium-
  ii chromium-browser 72.0.3626.119-0ubuntu0.18.04.1 amd64 Chromium web 
browser, open-source version of Chrome
  ii chromium-codecs-ffmpeg 72.0.3626.119-0ubuntu0.18.04.1 amd64 Free ffmpeg 
codecs for the Chromium Browser

  $ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz
  lrwxrwxrwx 1 root root 51 feb 25 15:56 
/usr/share/doc/chromium-browser/changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz

  $ ls -l ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  ls: cannot access '../chromium-codecs-ffmpeg-extra/changelog.Debian.gz': No 
such file or directory
  ```

  I don't think saving 2k warrants breaking sane access to the changelog:
  ```
  $ ls -l /usr/share/doc/chromium-browser/
  total 1108
  lrwxrwxrwx 1 root root 51 feb 25 15:56 changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  -rw-r--r-- 1 root root 2512 okt 25 2017 copyright.problems.gz
  -rw-r--r-- 1 root root 2975 okt 25 2017 README.source

  $ ls -l /usr/share/doc/chromium-codecs-ffmpeg/
  total 1104
  -rw-r--r-- 1 root root 2263 feb 25 15:56 changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  ```

  That copyright file takes up actual space but is not symlinked, 
:thinking_face:
  ```
  $ md5sum /usr/share/doc/chromium-{browser,codecs-ffmpeg}/copyright
  983091d3a4c4e207f2146a911a7f7387 /usr/share/doc/chromium-browser/copyright
  983091d3a4c4e207f2146a911a7f7387 
/usr/share/doc/chromium-codecs-ffmpeg/copyright
  ```

  If anything, I would guess that the symlink should be the other way
  around:

  - chromium-codecs-ffmpeg/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz
  - chromium-codecs-ffmpeg-extra/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz

  (And optionally that copyright file as well.)

  Cheers,
  Walter Doekes
  OSSO B.V.

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

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

[Desktop-packages] [Bug 1822616] Re: [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size

[Daniel van Vugt]

On my desktop this bug appears to have two causes, and undoing either
one fixes it:

 * mutter 3.32.0-1ubuntu1
   Solution: Downgrade to mutter-3.32.0-1

 * nvidia-drm.modeset=1 kernel parameter
   Solution: Remove it

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

** Changed in: budgie-desktop (Ubuntu)
   Importance: Medium => High

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

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

** Summary changed:

- [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width 
> 0 && height > 0 && scale > 0)" in 
meta_monitor_manager_xrandr_update_screen_size
+ [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion 
failed: (width > 0 && height > 0 && scale > 0)" in 
meta_monitor_manager_xrandr_update_screen_size

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

Title:
  [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT
  "assertion failed: (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1818347] Re: LibreOffice don't go full screen but sometimes it does.

[Olivier Tilloy]

Please can you elaborate on the exact steps you take to try and go
fullscreen? Which libreoffice application do you run, how do you request
fullscreen?

Can you also run the following command in a terminal and share the
output here?

apt policy libreoffice-core

Thanks!

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

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

Title:
  LibreOffice don't go full screen but sometimes it does.

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Install LibreOffice and try to go fullscreen. 1 out 10 chances, you
  will be getting fullscreen otherwise there is still top notch &
  sidebar showing up whenever u go fullscreen in LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  2 23:09:13 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0641]
  InstallationDate: Installed on 2018-12-24 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. Inspiron 5548
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=aad43495-2006-41af-bcb1-f91673ac405e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0FFJC4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/15/2018:svnDellInc.:pnInspiron5548:pvrA09:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Inspiron 5548
  dmi.product.sku: 0641
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1822838] Re: [regression][nvidia] gnome-shell is very large

[Daniel van Vugt]

I feel like this bug is going to be related to bug 1822478. Since
they're both caused by the same change in the same update.

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

Title:
  [regression][nvidia] gnome-shell is very large

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

Bug description:
  Everything from gnome-shell is very large.

  I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled
  extensions, checked scaling, deleted setting files, nothing worked.

  I created a new user, gnome-shell has the same issue in the beginning. Alt + 
F2 resets shell to normal size, but on logout/login everything is large again. 
This doesn't work on my user tho.
  Notifications, etc are extremely large.

  Just everything from the shell is like 40% larger than it should be.
  This also happens with default themes, settings, etc.

  Screenshot: https://imgur.com/a/oo5I7lZ

  gnome-shell: 3.32.0
  OS: Ubuntu 19.04 Development Branch

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:14:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-09 (82 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago)

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

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

[Desktop-packages] [Bug 1823035] Re: Buttons in Night Light menu in settings weird behaviour

[Efthimios Chaskaris]

I can't say those bugs are related to mine.

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

Title:
  Buttons in Night Light menu in settings weird behaviour

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

Bug description:
  When you press the pressed button (eg the sunset to sunrise button), it gets 
unpressed and nothing changes.
  Then, when you press that button again, the opposite button (manual) is 
pressed.

  Ubuntu 18.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-25 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Tags:  cosmic
  Uname: Linux 4.18.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1822616] Re: [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size

[Daniel van Vugt]

Confirmed reverting to mutter 3.32.0-1 fixes this crash. But I am having
other issues too.

** Changed in: budgie-desktop (Ubuntu)
   Status: Incomplete => Confirmed

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

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

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

Title:
  [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed:
  (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821403] Re: chromium browser crash on fresh offline system install

[Olivier Tilloy]

chromium-browser requires a newer version of libnss3 than what was
initially installed. This is not a bug in chromium or libnss itself. A
half-updated system is in an inconstistent state, and will result in
undefined behaviours like this crash.

If you had run "sudo apt-get dist-upgrade" before "sudo apt-get install
-y chromium-browser", this would have avoided the problem.

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

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

Title:
  chromium browser crash on fresh offline system install

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (and also what I expected and what happened):

  1. Disconnect computer from Internet
  2. Install Ubuntu (complete with reboot at the end).
  3. After running the (freshly installed) system, connect it to Internet
 and open a terminal and follow with the session outlined below. Enter
 commands on lines starting with "$" into the terminal. Things on lines
 starting with "//" are my comments and/or descriptions of what is
 expected output of the preceding command.

  $ sudo apt-get update
  // you should get the normal apt-get update output with no errors
  $ sudo apt-get install -y chromium-browser
  // you should get the normal apt-get install output here with no errors
  $ chromium-browser
  // expected result is to have the browser running and possibly some harmless
  // warnings below the "$ chromium-browser" line. What actually happens instead
  // is this:
  Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any 
effect anymore. please remove it from your fonts.conf
  [2805:2844:0322/144827.306513:FATAL:nss_util.cc(631)] 
NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the 
latest NSS, and if you still get this error, contact your distribution 
maintainer.
  Aborted (core dumped)
  // I believe that the problem is that the package "chromium-browser"
  // is either missing dependency on "libnss3-nssdb" or broken dependency
  // on "libnss3" (missing version number). To see, why, continue with:
  $ sudo apt-get install -y libnss3
  // What I got on the terminal myself follows (with some comments)
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libnss3-nssdb
  // This is why I said the missing dependency might be "libnss3-nssdb"
  // Here apt-get is telling me that "libnss3-nssdb" is going to be
  // installed.
  The following packages will be upgraded:
libnss3 libnss3-nssdb
  2 upgraded, 0 newly installed, 0 to remove and 452 not upgraded.
  Need to get 1,135 kB of archives.
  After this operation, 2,048 B of additional disk space will be used.
  // I didn't use "-y" on my command line so apt-get asked for permission.
  // You might be missing the line below if you follow the session
  // exactly. I included the rest of apt-get output to show you what
  // exactly got installed by the command.
  Do you want to continue? [Y/n] 
  Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libnss3-nssdb 
all 2:3.28.4-0ubuntu0.14.04.5 [10.6 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libnss3 amd64 
2:3.28.4-0ubuntu0.14.04.5 [1,124 kB]
  Fetched 1,135 kB in 2s (477 kB/s)  
  (Reading database ... 166878 files and directories currently installed.)
  Preparing to unpack .../libnss3-nssdb_2%3a3.28.4-0ubuntu0.14.04.5_all.deb ...
  Unpacking libnss3-nssdb (2:3.28.4-0ubuntu0.14.04.5) over 
(2:3.23-0ubuntu0.14.04.1) ...
  Preparing to unpack .../libnss3_2%3a3.28.4-0ubuntu0.14.04.5_amd64.deb ...
  Unpacking libnss3:amd64 (2:3.28.4-0ubuntu0.14.04.5) over 
(2:3.23-0ubuntu0.14.04.1) ...
  Setting up libnss3-nssdb (2:3.28.4-0ubuntu0.14.04.5) ...
  Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.14.04.5) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
  // Now when I try to run the browser ...
  $ chromium-browser
  // ... this warning is still there ...
  Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any 
effect anymore. please remove it from your fonts.conf
  [2991:2991:0322/145149.851132:ERROR:gpu_process_transport_factory.cc(1019)] 
Lost UI shared context.
  // ... but no more "NSS_VersionCheck failed" nor "Aborted (core dumped)"
  // (and, of course, the terminal window on the desktop is no longer
  // alone as the fresh google-chrome window is making a company to it ...

  Final notes:

  - This bug may not occur if you try to install Ubuntu while connected to 
Internet.
  - The reason why I did a "fresh offline install" was that installing it while 
online
takes over a hour on my system, installing offline and then doing the 
commands above
took only about 10 minutes. You might want to try to 

[Desktop-packages] [Bug 1822838] Re: [regression][nvidia] gnome-shell is very large

[Josh]

Bug has returned, not sure why to be honest but it seems like this
should be fixed, I saw other people having trouble with this as well.

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

Title:
  [regression][nvidia] gnome-shell is very large

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Everything from gnome-shell is very large.

  I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled
  extensions, checked scaling, deleted setting files, nothing worked.

  I created a new user, gnome-shell has the same issue in the beginning. Alt + 
F2 resets shell to normal size, but on logout/login everything is large again. 
This doesn't work on my user tho.
  Notifications, etc are extremely large.

  Just everything from the shell is like 40% larger than it should be.
  This also happens with default themes, settings, etc.

  Screenshot: https://imgur.com/a/oo5I7lZ

  gnome-shell: 3.32.0
  OS: Ubuntu 19.04 Development Branch

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:14:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-09 (82 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago)

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

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

[Desktop-packages] [Bug 1822616] Re: [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size

[Daniel van Vugt]

** Summary changed:

- gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && 
height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
+ [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width 
> 0 && height > 0 && scale > 0)" in 
meta_monitor_manager_xrandr_update_screen_size

** Tags added: nvidia

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

Title:
  [nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed:
  (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Olivier Tilloy]

I have resurrected the candidate/vaapi channel with an up-to-date build,
however it's currently pending a manual review in the store.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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