date:20180507

** Changed in: gnome-software (Ubuntu Cosmic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Snap branches shown in random order

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Snap branches are shown in a random order.

  [Test Case]
  1. Open GNOME Software
  2. Search for and select "communitheme" snap
  3. Select available channels (requires LP: #1768779 to be fixed).

  Expected result:
  Branches are shown in some predictable order.

  Observed result:
  Branches are shown in a random order.

  [Regression Potential]
  Solution is to sort branches alphabetically, could introduce new bugs in 
channel code.

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

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

[Desktop-packages] [Bug 1768743] Re: /usr/lib/gnome-initial-setup/gnome-initial-setup:11:add_ubuntusso_account:login_and_enable_livepatch:on_livepatch_permission_acquired:g_simple_async_result_complet

** Also affects: gnome-initial-setup (Ubuntu Cosmic)
   Importance: Low
 Assignee: Andrea Azzarone (azzar1)
   Status: Fix Committed

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

Title:
  /usr/lib/gnome-initial-setup/gnome-initial-
  
setup:11:add_ubuntusso_account:login_and_enable_livepatch:on_livepatch_permission_acquired:g_simple_async_result_complete:acquire_cb

Status in gnome-initial-setup package in Ubuntu:
  Fix Committed
Status in gnome-initial-setup source package in Bionic:
  New
Status in gnome-initial-setup source package in Cosmic:
  Fix Committed

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

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

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

[Desktop-packages] [Bug 1765269] Re: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_

And see also bug 1767956

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

Title:
  gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from
  meta_gpu_kms_read_current() from meta_gpu_read_current() from
  meta_monitor_manager_read_current_state() from
  meta_monitor_manager_setup()

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

Bug description:
  https://errors.ubuntu.com/problem/1e18be3177eec7b64bb8d8b6f51d7dc727e21bc1

  ---

  At upstart the problem occurred

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Apr 18 19:50:57 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2018-04-08 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f01cd93a89b:mov0x30(%rax),%edi
   PC (0x7f01cd93a89b) ok
   source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%edi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_gpu_read_current () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_read_current_state () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_manager_setup () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1767957] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display

** Summary changed:

- gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from 
g_log_structured_standard() from _gdk_x11_display_error_event()
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from 
g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap 
(invalid Pixmap parameter)"]

** Summary changed:

- gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from 
g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap 
(invalid Pixmap parameter)"]
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from 
g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap 
(invalid Pixmap parameter)"] from meta_pre_paint_func()

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

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured_standard() from _gdk_x11_display_error_event()
  ["BadPixmap (invalid Pixmap parameter)"] from meta_pre_paint_func()

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

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

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

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

[Desktop-packages] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

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

** This bug has been marked a duplicate of bug 1754296
   [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf (intel mesa driver)

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

Title:
  [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [35.781] X Protocol Version 11, Revision 0
  [35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [35.783] Current Operating System: Linux bdcomputerclub 
4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [35.787] Build Date: 22 February 2018  08:04:42PM
  [35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [35.789] Current version of pixman: 0.34.0
  [35.792]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [35.792] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
  [35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [35.803] (==) No Layout section.  Using the first Screen section.
  [35.803] (==) No screen section available. Using defaults.
  [35.803] (**) |-->Screen "Default Screen Section" (0)
  [35.803] (**) |   |-->Monitor ""
  [35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
  [35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [35.804] (==) Automatically adding devices
  [35.804] (==) Automatically enabling devices
  [35.804] (==) Automatically adding GPU devices
  [35.804] (==) Automatically binding GPU devices
  [35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [35.809]  Entry deleted from font path.
  [35.822] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
  [35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [35.822] (**) Extension "Composite" is disabled
  [35.822] (II) The server relies on udev to provide the list of input 
devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [35.822] (II) Loader magic: 0x55cfd2964020
  [35.822] (II) Module ABI versions:
  [35.822]  X.Org ANSI C Emulation: 0.4
  [35.822]  X.Org Video Driver: 23.0
  [35.822]  X.Org XInput driver : 24.1
  [35.822]  X.Org Server Extension : 10.0
  [35.824] (++) using VT number 1

  [35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 
paused 0
  [35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [35.832] (--) PCI:

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  [bionic] startx / xinit crashes with GLX backtrace if Composite
  Disabled in xorg.conf (intel mesa driver)

Status in xorg-server package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
  [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [ 35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 
0xd340/1048576
  [ 35.833] (II) LoadModule:

[Desktop-packages] [Bug 1769810] [NEW] Featured snaps doesn't align well when part page

Public bug reported:

[Impact]
When there is not a full page of featured apps they don't align to the grid.

[Test Case]
1. Run initial setup:
$ /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-user
2. Go to the "Ready to go" page
3. Scroll to the last page in the featured apps

Expected result:
The last page is aligned the same as the other page(s), even if it doesn't have 
a full 15 apps to show.

Observed result:
The apps are spread out.

[Regression Potential]
Solved by adding spacer elements to fill out page. Could cause other bugs.

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-initial-setup (Ubuntu Bionic)
 Importance: Medium
 Status: Triaged

** Affects: gnome-initial-setup (Ubuntu Cosmic)
 Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

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

Title:
  Featured snaps doesn't align well when part page

Status in gnome-initial-setup package in Ubuntu:
  Fix Committed
Status in gnome-initial-setup source package in Bionic:
  Triaged
Status in gnome-initial-setup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  When there is not a full page of featured apps they don't align to the grid.

  [Test Case]
  1. Run initial setup:
  $ /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-user
  2. Go to the "Ready to go" page
  3. Scroll to the last page in the featured apps

  Expected result:
  The last page is aligned the same as the other page(s), even if it doesn't 
have a full 15 apps to show.

  Observed result:
  The apps are spread out.

  [Regression Potential]
  Solved by adding spacer elements to fill out page. Could cause other bugs.

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

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

[Desktop-packages] [Bug 1769810] Re: Featured snaps doesn't align well when part page

Screenshot of issue. Note that this depends on how many snaps are being
featured at the time of testing.

** Attachment added: "Screenshot from 2018-05-08 16-50-39.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1769810/+attachment/5135827/+files/Screenshot%20from%202018-05-08%2016-50-39.png

** Also affects: gnome-initial-setup (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gnome-initial-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-initial-setup (Ubuntu Cosmic)
   Status: New => Fix Committed

** Changed in: gnome-initial-setup (Ubuntu Cosmic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-initial-setup (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: gnome-initial-setup (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: gnome-initial-setup (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  Featured snaps doesn't align well when part page

Status in gnome-initial-setup package in Ubuntu:
  Fix Committed
Status in gnome-initial-setup source package in Bionic:
  Triaged
Status in gnome-initial-setup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  When there is not a full page of featured apps they don't align to the grid.

  [Test Case]
  1. Run initial setup:
  $ /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-user
  2. Go to the "Ready to go" page
  3. Scroll to the last page in the featured apps

  Expected result:
  The last page is aligned the same as the other page(s), even if it doesn't 
have a full 15 apps to show.

  Observed result:
  The apps are spread out.

  [Regression Potential]
  Solved by adding spacer elements to fill out page. Could cause other bugs.

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

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

[Desktop-packages] [Bug 1755971] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured() from _gdk_x11_display_error_ev

** Summary changed:

- gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from g_log_structured() 
from _gdk_x11_display_error_event()
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from g_log_structured() 
from _gdk_x11_display_error_event() ["BadMatch (invalid parameter attributes)"] 
from do_send_frame_timings()

** Also affects: mutter (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/1755971

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured() from _gdk_x11_display_error_event() ["BadMatch
  (invalid parameter attributes)"] from do_send_frame_timings()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1769811] [NEW] Livepatch / Help improve images too dark

Public bug reported:

[Impact]
The Livepatch / Help improve images aren't transparent enough to match the 
design.

[Test Case]
1. Run initial setup:
$ /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-user
2. Go to the "Livepatch" page

Expected result:
Images are shown with 75% transparency

Observed result:
Images are shown with much less transparency (too dark).

[Regression Potential]
Low, just adjusted alpha value.

** Affects: gnome-initial-setup (Ubuntu)
 Importance: Low
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-initial-setup (Ubuntu Bionic)
 Importance: Low
 Status: Triaged

** Affects: gnome-initial-setup (Ubuntu Cosmic)
 Importance: Low
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Also affects: gnome-initial-setup (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gnome-initial-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-initial-setup (Ubuntu Cosmic)
   Importance: Undecided => Low

** Changed in: gnome-initial-setup (Ubuntu Cosmic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-initial-setup (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: gnome-initial-setup (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: gnome-initial-setup (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  Livepatch / Help improve images too dark

Status in gnome-initial-setup package in Ubuntu:
  Fix Committed
Status in gnome-initial-setup source package in Bionic:
  Triaged
Status in gnome-initial-setup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The Livepatch / Help improve images aren't transparent enough to match the 
design.

  [Test Case]
  1. Run initial setup:
  $ /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-user
  2. Go to the "Livepatch" page

  Expected result:
  Images are shown with 75% transparency

  Observed result:
  Images are shown with much less transparency (too dark).

  [Regression Potential]
  Low, just adjusted alpha value.

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

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

[Desktop-packages] [Bug 1766277] Re: Ubuntu changes graphic is not translatable

** Changed in: gnome-initial-setup (Ubuntu)
   Status: In Progress => Fix Committed

** Also affects: gnome-initial-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-initial-setup (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
   Status: Fix Committed

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

Title:
  Ubuntu changes graphic is not translatable

Status in gnome-initial-setup package in Ubuntu:
  Fix Committed
Status in gnome-initial-setup source package in Bionic:
  New
Status in gnome-initial-setup source package in Cosmic:
  Fix Committed

Bug description:
  The graphic showing the changes in Ubuntu is a png located in the
  debian/ directory and is not translatable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-initial-setup 3.28.0-2ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 23 17:02:28 2018
  InstallationDate: Installed on 2014-07-15 (1378 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (30 days ago)

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

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

[Desktop-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)

2018-05-07 Thread David Rennie-Waldock

I'm getting the same problem with Telegram and Steam, both packages were 
installed in the same way on both systems.
Indicator was visibile prior to upgrade, is not after upgrade, works in a clean 
install of bionic.

Even the basic example in
http://candidtim.github.io/appindicator/2014/09/13/ubuntu-appindicator-
step-by-step.html does not work on the upgraded system.

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

Title:
  nm-applet symbol not displayed on mate (18.04)

Status in ubuntu-mate:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1769480] Missing required logs.

2018-05-07 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1769480

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: cosmic

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

Title:
  Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

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

Bug description:
  how to reproduce:

  dd the iso to an usb drive and boot from it.
  List all wifi devices in live-mode and connect to one of it. Use the web for 
some minutes. Open up the wifi on the top right again and list the available 
networks - it dont show any others any more. Just the one you are connected to.

  How to overcome the bug: put the computer into airplane mode and go
  away from airplane mode again. Or: disconnect the usb wifi device and
  connect it again.

  Does this bug exist also on installed 18.04 and updated to last (apt update, 
apt upgrade, apt dist-upgrade)?
  Yes

  What wifi device is been used:
  ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
  ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected
  ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  usbcore: registered new interface driver rt2800usb
  ...
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 
'rt2870.bin'
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - 
version: 0.36

  uname -a
  Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 826283] Re: size of internal HDDs differs/wrong

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

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

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

Title:
  size of internal HDDs differs/wrong

Status in Ubuntu Translations:
  Invalid
Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have a dual boot scenario. On sda1 is windows 7 hosted and i partitioned 
with an Ubuntu Lucid Live-CD the size to 48,0 GB.
  After the installation i got this informations:
  - If the partition is mounted it shows on the desktop an size of 52 GB (52 GB 
Dateisystem)
  - If i want to see the proporties with an right-click, it shows me an size of 
48 GB (Name: 52 GB Dateisystem, Gesamte Kapazität 48 GB)
  - In the system monitor is also the size given with 48,0 GB

  So the automatic name is wrong and should the same as the proporties
  show!

  
  Ubuntu Lucid 10.04.3
  Linux bloedbommel3 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:07:13 UTC 
2011 x86_64 GNU/Linux

  Package: gnome
  Versions: 
  1:2.28+1ubuntu3 
(/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_lucid_universe_binary-amd64_Packages)
   Description Language: de

  Package: nautilus
  Versions: 
  1:2.30.1-0ubuntu1.2 
(/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)
   Description Language:
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NonfreeKernelModules: fglrx
  Package: nautilus 1:3.2.1-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Tags:  oneiric
  Uname: Linux 3.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  usr_lib_nautilus:
   evince   3.2.1-0ubuntu2
   file-roller  3.2.1-0ubuntu1
   nautilus-dropbox 0.7.1

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

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

[Desktop-packages] [Bug 874471] Re: Pendrive/USB drive cannot be open in folder

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

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

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

Title:
  Pendrive/USB drive cannot be open in folder

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When I plug in my pendrive/USB drive, my Ubuntu cannot open the
  pendrive/USB drive in a folder, however it keep open the pendrive/USB
  drive with the software centre application. Now I can't do anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: software-center 5.0.1.4
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sat Oct 15 01:45:32 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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

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

[Desktop-packages] [Bug 823168] Re: gvfs webdav to common name

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

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

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

Title:
  gvfs webdav to common name

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  If I connect 2 webdav site on the same server but different directories, only 
one is accessable from applications (/ and /). Cause: 
for mounting a to common name is used in nautulis "Webdav as  on " 
so the /home//.gvfs/ provides only the last mounted webdav (names are 
equal)
  Please use a less common name like SMB mounts:  on . --> For 
webdav: webdav(s): on . Don' t forget escape signs.

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

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

[Desktop-packages] [Bug 708546] Re: USB keys freeze the computer

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

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

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

Title:
  USB keys freeze the computer

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  When I use "unity layout", I can't open any USB key.
  The icon shows on the desktop but if I click on it, this freezes the computer 
for ever.
  I have to switch off the computer and use the gnome layout to open USB key

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Jan 27 10:58:35 2011
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 
(20101007)
  ProcEnviron:
   LANG=fr_FR.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1706154] Re: Chromium Lockup on some js enabled sites(ups, paypal, etc)

[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/1706154

Title:
  Chromium Lockup on some js enabled sites(ups, paypal, etc)

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  see apport, chromium is constantly locking up and eating all my cpu,
  chromium task manager reports 0 memory usage?

  Lockup dissipates after about 5 minutes
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk=
   modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 
1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
  DetectedPlugins:
   
  DistroRelease: Linux 18.1
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-07-13 (375 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Load-Avg-1min: 4.22
  Load-Processes-Running-Percent: #  1.1%
  MachineType: MSI MS-7786
  Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1291 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Tags: serena third-party-packages
  ThirdParty: True
  Uname: Linux 4.8.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-P33 (MS-7786)
  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: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7786
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-03-16T14:53:53.556952

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

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

[Desktop-packages] [Bug 1704893] Re: Writer closes when finished loading without error

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

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

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

Title:
  Writer closes when finished loading without error

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  When I attempt to open a document in LibreOffice Writer, by any
  method, I am shown a loading dialog with a progress bar. The progress
  bar advances to about 95%, then disappears, and nothing happens.

  I have tried launching LibreOffice Writer by several methods:
  - Start LibreOffice, click "Create/Writer Document"
  - Open a filetype associated with LibreOffice Writer in a file browser
  - Launch libreoffice --writer in a terminal (This outputs nothing)

  I have confirmed via ps -A that LibreOffice is truly closed, and not
  merely invisible.

  Things I tried, with no difference:
  - sudo apt-get install --reinstall libreoffice-writer
  - rm ~/.config/libreoffice
  - cp -a /usr/lib/libreoffice/share ~/.config/libreoffice/4/user

  This is a fresh install of LibreOffice on a fresh install of Lubuntu.

  Other LibreOffice applications, such as Calc, work fine.

  I believe the same problem may have been reported at
  - https://askubuntu.com/questions/129383/libreoffice-not-opening
  - 
https://askubuntu.com/questions/697309/unable-to-open-libreoffice-writer?rq=1
  Nothing there helped me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-writer 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Jul 17 20:22:50 2017
  InstallationDate: Installed on 2017-07-05 (12 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714121] Re: libre office will not launch. I have used the fix broken install command every day.

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

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

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

Title:
  libre office will not launch. I have used the fix broken install
  command every day.

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  The software will not open/launch.

  ProblemType: Bug
  DistroRelease: Kali 2017.1
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Aug 30 20:35:49 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-23 (160 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

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

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

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

Title:
  [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [35.781] X Protocol Version 11, Revision 0
  [35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [35.783] Current Operating System: Linux bdcomputerclub 
4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [35.787] Build Date: 22 February 2018  08:04:42PM
  [35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [35.789] Current version of pixman: 0.34.0
  [35.792]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [35.792] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
  [35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [35.803] (==) No Layout section.  Using the first Screen section.
  [35.803] (==) No screen section available. Using defaults.
  [35.803] (**) |-->Screen "Default Screen Section" (0)
  [35.803] (**) |   |-->Monitor ""
  [35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
  [35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [35.804] (==) Automatically adding devices
  [35.804] (==) Automatically enabling devices
  [35.804] (==) Automatically adding GPU devices
  [35.804] (==) Automatically binding GPU devices
  [35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [35.809]  Entry deleted from font path.
  [35.822] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
  [35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [35.822] (**) Extension "Composite" is disabled
  [35.822] (II) The server relies on udev to provide the list of input 
devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [35.822] (II) Loader magic: 0x55cfd2964020
  [35.822] (II) Module ABI versions:
  [35.822]  X.Org ANSI C Emulation: 0.4
  [35.822]  X.Org Video Driver: 23.0
  [35.822]  X.Org XInput driver : 24.1
  [35.822]  X.Org Server Extension : 10.0
  [35.824] (++) using VT number 1

  [35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 
paused 0
  [35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 
0xd340/1048576
  [35.833] (II) LoadModule: "glx"
  [

[Desktop-packages] [Bug 1753203] Re: unable to access audio disc in nautilus

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

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

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

Title:
  unable to access audio disc in nautilus

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Recently upgraded from Ubuntu 17.10 to Ubuntu 18.04 Bionic Beaver(development 
branch).
  Message recipient disconnected from message bus without replying. I can open 
the audio cd in VLC but when I try in Rhythmbox, I get the same message as 
Nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  3 23:37:36 2018
  InstallationDate: Installed on 2017-04-20 (318 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-03-02 (1 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

2018-05-07 Thread Kai-Heng Feng

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

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

Title:
  Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

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

Bug description:
  how to reproduce:

  dd the iso to an usb drive and boot from it.
  List all wifi devices in live-mode and connect to one of it. Use the web for 
some minutes. Open up the wifi on the top right again and list the available 
networks - it dont show any others any more. Just the one you are connected to.

  How to overcome the bug: put the computer into airplane mode and go
  away from airplane mode again. Or: disconnect the usb wifi device and
  connect it again.

  Does this bug exist also on installed 18.04 and updated to last (apt update, 
apt upgrade, apt dist-upgrade)?
  Yes

  What wifi device is been used:
  ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
  ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected
  ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  usbcore: registered new interface driver rt2800usb
  ...
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 
'rt2870.bin'
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - 
version: 0.36

  uname -a
  Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

2018-05-07 Thread Jan Alexander

I can confirm the same issue on 18.04 using Gigabyte AERO 15x v8 with
Nvidia GTX 1070 MaxQ. The `prime-select intel` method leaves the card
powered on, even though the vgaswitcheroo/switch indicates it's off -
the system power draw is ~ 20W.

After installing bbswitch and turning the card off that way (had to mask
off the nvidia-fallback to prevent manual loading of the nouveau
module), the power draw drops to ~ 10W so the card is indeed powered off
in that case.

There is something broken in nouveau driver for my system as it is
unable to power down the card using the vgaswitcheroo method, when
running with nouveau.runpm=0.

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

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

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

[Desktop-packages] [Bug 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.

See also bug 1767312.

** Summary changed:

- Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then 
crashes on AMD/radeon graphics
+ [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, 
then crashes.

** No longer affects: totem (Ubuntu)

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black
  screen, then crashes.

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUNDS

  Just for totem:  sudo apt remove gstreamer1.0-vaapi

  Or to workaround in all players:  sudo apt remove mesa-va-drivers

  
  ORIGINAL DESCRIPTION

  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

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

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

[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

** Summary changed:

- [radeon] totem wrong color on h264 videos
+ [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

** Description changed:

  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6
  
  WORKAROUND:
  sudo apt remove mesa-va-drivers
+ 
+ See also bug 1720820.

** Description changed:

  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6
  
  WORKAROUND:
+ sudo apt remove gstreamer1.0-vaapi
+ or
  sudo apt remove mesa-va-drivers
  
  See also bug 1720820.

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

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

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

[Desktop-packages] [Bug 1769409] Re: Support for global menu

2018-05-07 Thread Lester Carballo Pérez

Dimitrij Mijoski you are already welcome.

Daniel van Vugt, you are also welcome. There are bugs like this:
https://bugs.launchpad.net/ubuntu/+source/jayatana/+bug/1769689 where is
easy to be fixed and will really improve the user perception about the
global menu. See a video of the difference:
https://www.youtube.com/watch?v=rIIMLlAeXTw

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

Title:
  Support for global menu

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The move to Gnome from Unity was ok except for two major features that
  got lost and those are global menus and pixel saving when maximized.

  Are there any chances of official support in future releases?

  Gnome extension for global menus exists https://github.com/lestcape
  /Gnome-Global-AppMenu and that may be used as a starting point. The
  Ubuntu team already did similar move by including the plugin dash-to-
  dock.

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

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

[Desktop-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

Yes, that is mentioned in https://trello.com/c/i3JvebJ9

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

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

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

[Desktop-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

Yes, that is mentioned in https://trello.com/c/i3JvebJ9

Although you then face the problem of upsetting people who prefer doing
two-finger taps :)

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

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

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

[Desktop-packages] [Bug 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed

Sounds like a crash is occurring, and we have indeed encountered a few
reports like this.

To proceed with finding out which crash this is, please:

1. Apply the workaround from bug 994921.

2. Reproduce the crash.

3. Look in /var/crash for crash files and run:
   ubuntu-bug /var/crash/YOURFILE.crash

4. Tell us here the ID of the new bug created.

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

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

Title:
  Logged out when unplugging external monitors with screen locked and
  lid closed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 18.04 (Bionic) 64-bit on a System76 Galaga UltraPro
  laptop. At work, I plug two displays into my laptop, one DisplayPort
  and one HDMI.

  If, while both displays are plugged in and the laptop lid is closed
  and the laptop's built-in display is therefore disabled, I:

  1. lock my screen;
  2. unplug both displays at about the same time;
  3. wait about ten seconds; and then
  4. open my laptop lid,

  I find that I have been logged out.

  If I immediately log back in to the built-in display, a couple seconds
  after I log in, the screen locks. If I then immediately log out and
  log back in again, the screen does _not_ lock.

  It seems that this weird lock-right-after-login behavior is related to
  the fact that I get logged out as described above. It seems that the
  shell remembers that it is supposed to be locked despite the crash /
  logout, such that when I log back in, it realizes that it's supposed
  to be locked and locks itself.

  Note that I am filing this bug as instructed in
  https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/105:
  "BTW, we have fixed many gnome-shell bugs with these symptoms recently
  in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
  problems."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 14:26:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-09 (635 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (10 days ago)

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

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

[Desktop-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

2018-05-07 Thread Misaki

Would it be possible to make 'area' mode the default if the touchpad
doesn't support multi-finger input?

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

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

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

[Desktop-packages] [Bug 1769372] Re: Prompt the user when the power button is pressed

Also, the bug applies to real machines too. So I removed mention of VMs.

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

Title:
  Prompt the user when the power button is pressed

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS as VirtualBox guest
  2. Login to session
  3. Press ACPI Power button/key

  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  Note 1: Problem exists with both VirtualBox 5.1.36 and 5.2.10 (guest
  additions and extpack are installed and have corresponding versions).
  Ubuntu 16.04.4 LTS amd64 is a host.

  Note 2: Problem exists if use QEMU-KVM (sudo kvm -m 1536 -drive
  file=/dev/sdc,format=raw) too. Sending system_powerdown from
   shutdowns system without prompt.

  Workaround/fix (1)

  gsettings set org.gnome.settings-daemon.plugins.power power-button-
  action interactive

  Workaround/fix (2)

  Settings >
  Power >
  Suspend & Power Button >
  When the Power Button is pressed = Power Off (actually does prompt the user)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-settings-daemon
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/1769372/+subscriptions

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

[Desktop-packages] [Bug 1769372] Re: Prompt the user when the power button is pressed on VirtualBox or QEMU-KVM guest

Please read: https://gitlab.gnome.org/GNOME/gnome-control-
center/merge_requests/39

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => In Progress

** Summary changed:

- Prompt the user when the power button is pressed on VirtualBox or QEMU-KVM 
guest
+ Prompt the user when the power button is pressed

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

Title:
  Prompt the user when the power button is pressed

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS as VirtualBox guest
  2. Login to session
  3. Press ACPI Power button/key

  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  Note 1: Problem exists with both VirtualBox 5.1.36 and 5.2.10 (guest
  additions and extpack are installed and have corresponding versions).
  Ubuntu 16.04.4 LTS amd64 is a host.

  Note 2: Problem exists if use QEMU-KVM (sudo kvm -m 1536 -drive
  file=/dev/sdc,format=raw) too. Sending system_powerdown from
   shutdowns system without prompt.

  Workaround/fix (1)

  gsettings set org.gnome.settings-daemon.plugins.power power-button-
  action interactive

  Workaround/fix (2)

  Settings >
  Power >
  Suspend & Power Button >
  When the Power Button is pressed = Power Off (actually does prompt the user)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-settings-daemon
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/1769372/+subscriptions

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

[Desktop-packages] [Bug 1769771] [NEW] /usr/bin/baobab:11:gtk_tree_model_get_valist:gtk_tree_model_get:baobab_window_open_item:__lambda13_:_lambda13gtk_menu_item_activate

2018-05-07 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: xenial yakkety

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

Title:
  
/usr/bin/baobab:11:gtk_tree_model_get_valist:gtk_tree_model_get:baobab_window_open_item:__lambda13_:___lambda13__gtk_menu_item_activate

Status in baobab package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1769773] [NEW] /usr/lib/gnome-terminal/gnome-terminal-server:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

2018-05-07 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: artful bionic kylin-14.10 kylin-15.04 trusty vivid wily xenial yakkety 
zesty

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

Title:
  /usr/lib/gnome-terminal/gnome-terminal-
  
server:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

Status in gnome-terminal package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1769224] Re: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04)

2018-05-07 Thread Gunnar Hjalmarsson

Thanks for your report!

I think the info is stored; the problem is that GDM does not make use of
it. The issue is also discussed in bug #1725676, see e.g. comment #11.

I also found an upstream bug report.

** Bug watch added: GNOME Bug Tracker #776282
   https://bugzilla.gnome.org/show_bug.cgi?id=776282

** Also affects: gdm via
   https://bugzilla.gnome.org/show_bug.cgi?id=776282
   Importance: Unknown
   Status: Unknown

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

Title:
  keyboard layout on greeter is not stored per user (function lost from
  16.04 to 18.04)

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  New

Bug description:
  We are using two keyboard layouts in my family (dvorak-like and
  standard).

  With 16.04, upon selection of user on the greeter, the keyboard layout
  would default to the one of the user.

  With 18.04 fresh install, the above is lost. Instead, the last
  selected keyboard layout remains selected. Therefore it is necessary
  to check and maybe change the layout to be able to set the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 19:39:08 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-01T15:06:51.113672

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

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

[Desktop-packages] [Bug 1769640] Re: Update evolution to 3.28.2

This bug was fixed in the package evolution - 3.28.2-1

---
evolution (3.28.2-1) unstable; urgency=medium

  * New upstream release (LP: #1769640)
  * Bump e-d-s dependencies and build-dependencies to 3.28.2
  * Bump debhelper compat to 11
  * Drop patches applied in new release:
- 0004-EMailDisplay-Do-not-call-reload-when-nothing-is-load.patch
- 0005-Bug-793583-webkit_web_view_load_html-garbages-linked.patch
- 0006-Revert-message-composer-part-of-the-previous-commit.patch

 -- Jeremy Bicha   Mon, 07 May 2018 09:21:05 -0400

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

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

Title:
  Update evolution to 3.28.2

Status in evolution package in Ubuntu:
  Fix Released
Status in evolution source package in Bionic:
  Triaged

Bug description:
  Impact
  ==
  evolution has released a new stable bugfix release. (These will happen about 
once a month until 3.30 is released.)

  https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-28
  https://git.gnome.org/browse/evolution/log/?h=gnome-3-28

  Test Case
  =
  After installing this update, please restart your computer.

  Verify that evolution still works as well as it did before.

  Optionally, you can go through some of the fixed bugs to verify the
  bug and the fix.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  Ubuntu GNOME stopped including Evolution by default in 17.04.
  Upgraders may still have Evolution installed and it's a popular app.
  (It was demoted to universe before 16.04 LTS.)

  Other Info
  ==
  This update depends on evolution-data-server 3.28.2 (LP: #1769637)

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

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

[Desktop-packages] [Bug 1755064] Re: gnome-software crashed with signal 5 in g_wakeup_new → g_main_context_new → pk_client_resolve → gs_plugin_packagekit_resolve_packages_with_filter → gs_plugin_packa

I guess we can close this one. It has been fixed with gir1.2-snapd-1
1.39 as can also be seen from errors.ubuntu.com

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  gnome-software crashed with signal 5 in g_wakeup_new →
  g_main_context_new → pk_client_resolve →
  gs_plugin_packagekit_resolve_packages_with_filter →
  gs_plugin_packagekit_resolve_packages

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  Error on the error tracker:
  https://errors.ubuntu.com/problem/b159edc6392f7b608f60a42e1b7a792ba894b828

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.27.92-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 11 19:11:26 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-02-17 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.27.92-0ubuntu2
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   pk_client_resolve () at /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
   () at 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so
   gs_plugin_refine () at 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so
  Title: gnome-software crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-07 Thread Steven Tryon

Addendum to #124

/etc/udev/rules.d/79-udev-epson.rules shows
ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", 
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777"

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-07 Thread Steven Tryon

Same with 18.04 and Epson V500 with current iScan installed. 
Worked as installed with 16.04 and with workarounds with 17.10.

stryon@gimli:~$ scanimage -L
device `epkowa:interpreter:002:013' is a Epson Perfection V500 flatbed scanner
Note: Scanner light turns blinking red.

stryon@gimli:~$ sudo lsusb | grep Epson
Bus 002 Device 013: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500]

Copied /usr/lib/sane$/* to /usr/lib/x86_64-linux-gnu/sane
Commented out epson lines in /etc/sane.d/dll.conf and added epkowa
epkowa.conf has usb line enabled.

On starting xsane, xsane says "Scanning for devices" then scanner light turns 
blinking red.
"Acquire preview" pops up error window: Failed to start scanner: Invalid 
argument.

Similar results with iscan plugin for Gimp.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769637] Re: Update evolution-data-server to 3.28.2

This bug was fixed in the package evolution-data-server - 3.28.2-1

---
evolution-data-server (3.28.2-1) unstable; urgency=medium

  * New upstream release (LP: #1769637)

 -- Jeremy Bicha   Mon, 07 May 2018 08:21:46 -0400

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update evolution-data-server to 3.28.2

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Bionic:
  Triaged

Bug description:
  Impact
  ==
  evolution-data-server (e-d-s) has released a new stable bugfix release.
  (These will happen about once every month until 3.30 is released in Septebmer)

  Updating e-d-s is required to update evolution to 3.28.2 (LP: #)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-28
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-28

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

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

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

[Desktop-packages] [Bug 1769761] [NEW] Sometimes session doesn't start after success login (gnome, 18.04)

2018-05-07 Thread Sergei

Public bug reported:

This happens sometimes (~70% to happen) after I upgrdaded my ubuntu to 18.04. 
After entering user & password I see only blank purple screen without anything. 
I was trying to wait for 30 minutes, but it seemed like nothing was happening. 
This problem affects gnome-session and ubuntu-session for me. 
I've also found that I'm not the only person who is affected.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May  8 01:51:42 2018
InstallationDate: Installed on 2017-11-11 (177 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2018-03-02T21:56:59.591943

** Affects: gdm3 (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 gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1769761

Title:
  Sometimes session doesn't start after success login (gnome, 18.04)

Status in gdm3 package in Ubuntu:
  New

Bug description:
  This happens sometimes (~70% to happen) after I upgrdaded my ubuntu to 18.04. 
After entering user & password I see only blank purple screen without anything. 
I was trying to wait for 30 minutes, but it seemed like nothing was happening. 
This problem affects gnome-session and ubuntu-session for me. 
  I've also found that I'm not the only person who is affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 01:51:42 2018
  InstallationDate: Installed on 2017-11-11 (177 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-03-02T21:56:59.591943

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

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

[Desktop-packages] [Bug 1769757] [NEW] Can't edit Microsoft .docx/ .doc within Libreoffice

2018-05-07 Thread Jörn-Ingo Weigert

Public bug reported:

OS: Ubuntu 18.04 Bionic Beaver 
(Description:   Ubuntu 18.04 LTS Release:   18.04)
dm: LightDM Destop Manager
Sessiontype: Guest-Session

Libreoffice-Version (About):
Version: 6.0.3.2
Build-ID: 1:6.0.3-0ubuntu1
CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group

libreoffice:
  Installiert:   (keine)
  Installationskandidat: 1:6.0.3-0ubuntu1
  Versionstabelle:
 1:6.0.3-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

We are using the guest-session of ldm for an restricted session for
postpaid-modus.

After recent OS upgrade to 18.04, some guests experienced issues, that either 
Nautilus mounts their USB-Stick in read-only mode, as also and that is for what 
this bug report is for,
That if they open Microsoft documents (type of .docx / .doc), those documents 
are opened correctly
but Libreoffice (swriter) reject any input without any error message.

Those documents were NOT secured by any password, as guests are
claiming.

Weirder, if I copy the content of the document into, f.e. abiword, the
program still reject any change or input.

This behavior does not apply when the user creat a blank new document,
but if he try to open a microsoft documen, he is again not able to edit
the content.

This is a major issue for us, as we have already update all our three PC
to 18.04, so we have no alternative. And the customers are
unsatisfied...

Hope you can help out here.

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

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

Title:
  Can't edit Microsoft .docx/ .doc within Libreoffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 18.04 Bionic Beaver 
  (Description: Ubuntu 18.04 LTS Release:   18.04)
  dm: LightDM Destop Manager
  Sessiontype: Guest-Session

  Libreoffice-Version (About):
  Version: 6.0.3.2
  Build-ID: 1:6.0.3-0ubuntu1
  CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
  Gebietsschema: de-DE (de_DE.UTF-8); Calc: group

  libreoffice:
Installiert:   (keine)
Installationskandidat: 1:6.0.3-0ubuntu1
Versionstabelle:
   1:6.0.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  We are using the guest-session of ldm for an restricted session for
  postpaid-modus.

  After recent OS upgrade to 18.04, some guests experienced issues, that either 
Nautilus mounts their USB-Stick in read-only mode, as also and that is for what 
this bug report is for,
  That if they open Microsoft documents (type of .docx / .doc), those documents 
are opened correctly
  but Libreoffice (swriter) reject any input without any error message.

  Those documents were NOT secured by any password, as guests are
  claiming.

  Weirder, if I copy the content of the document into, f.e. abiword, the
  program still reject any change or input.

  This behavior does not apply when the user creat a blank new document,
  but if he try to open a microsoft documen, he is again not able to
  edit the content.

  This is a major issue for us, as we have already update all our three
  PC to 18.04, so we have no alternative. And the customers are
  unsatisfied...

  Hope you can help out here.

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

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

[Desktop-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

2018-05-07 Thread josvanr

now it would be nice to have a way of finding out when it does/doesn't
work..

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

Title:
  xdg-open *.desktop opens text editor

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

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

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

[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

2018-05-07 Thread Andrea

For each time I make a search, I use type ahead 99 times to navigate
directories. In my opinion type ahead search is indispensable for using
Nautilus productively.

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

Title:
Restore interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
Won't Fix

Bug description:
Nautilus dropped the popular type-ahead search feature years ago.
Ubuntu has been carrying a patch to revert that change. See bug
1164016 for the original LP bug and patch proposal.

Nautilus is now under very active development. During the 3.22 cycle,
that patch needed to be rebased. I tried to do it and what I came up
with caused a crash (it didn't really crash for me, but ricotz and
some others experienced it) and the first letter typed activated type-
ahead search but the first letter was dropped. In other words, you
would need to type "ddow" to activate the Downloads folder instead of
just "dow" like in previous releases. (LP: #1635988)

I did that rebase in October 2016 and no one has stepped up then to
improve the patch.

The Nautilus maintainer csoriano has said that the slots and views
changed significantly during 3.22 and will likely be refactored more
in the future.

If there's no one available to maintain the patch, unfortunately,
we'll eventually have to drop the patch to not be stuck on an ancient
version of Nautilus.

I am proposing that we do this at the start of the 17.10 development
cycle. This gives 6 months for a developer to step up and try to fix
the patch and 12 months before 18.04 LTS.

Other Items
===
- For better performance with the built-in search, we need to reconsider
avoiding tracker in Unity (LP: #176)

- There is an option in Preferences for users to disable searching in
subfolders. I don't think we want to do that by default but maybe it
can help some people.

The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with
this patch now disabled.

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

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

2018-05-07 Thread Jeremy Bicha

Egmont, by the way, that mutter patch is in Debian also since mutter is
currently in sync between Debian and Ubuntu.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend

** Branch linked: lp:~azzar1/gnome-shell/fix-1768786

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

Title:
  Screen is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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

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

2018-05-07 Thread Egmont Koblinger

@guido Nope, that one is irrelevant (that icon title is something
completely different, it's a legacy concept: the title of the window
whenever it's iconified; plus the change is in gnome-terminal's current
development series which won't appear in Bionic).

Anyway, I managed to locate the bug, see my previous comment. Now it's
Ubuntu's turn to apply the fix.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1702351] Re: [snap] "User installation could not be completed"

2018-05-07 Thread modolo

Olivier,


The only messages on the console were the two lines Gtk-Message *

$ snap run libreoffice
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"

Follow the output:
$ cat 
$HOME/snap/libreoffice/current/.config/libreoffice/4/user/config/javasettings_Linux_X86_64.xml


http://openoffice.org/2004/java/framework/1.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>







Thanks,
Marcelo Módolo

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

Title:
  [snap] "User installation could not be completed"

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

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

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

I'm confused. Are my URL & yours the same?

Anyway, it seems that Ubuntu has not fixed it.

Terminal seems to work OK, so far; but, it certainly is an eyesore.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-07 Thread Bernadette Addison

Is there any way possible to gain early access to the "FIX RELEASED"
files???

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

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

2018-05-07 Thread Egmont Koblinger

@guido Oh, I guess I found it, I guess you meant this:

https://gitlab.gnome.org/GNOME/mutter/merge_requests/62

I made a comment over there. This patch is buggy, this is the one that
breaks my previous fix.

The patch is shipped by Ubuntu, named theme-use-gtk_render_icon_suface-
to-paint-button-icon.patch (intended to fix LP #1764558) inside
mutter_3.28.1-1ubuntu1.debian.tar.xz. Ubuntu should drop (or fix) this
broken patch to fix this problem.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend

This is actually a different bug due to the
ubuntu_lock_on_suspend.patch. Reopening.

** This bug is no longer a duplicate of bug 1532508
   Screen contents revealed briefly on resume, before even unlocking

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

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

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

Title:
  Screen is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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

[Desktop-packages] [Bug 1164016] Re: restore type-ahead find

2018-05-07 Thread Ljiljan Veselinovic

Why don't we have both options? Why removing something that we like
(find folder/file with a letter) and insisting on something else
(search)? I am trying to get used to this new behavior for almost a
week, but it is just slowing me down.

This could be implemented as simple as this:

## keypress event

switch (option_search_or_locate ) {
  case 1:  locate_folder (char_pressed); break;
  case 2:  search (char_pressed); break;
}

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Desktop-packages] [Bug 1702351] Re: [snap] "User installation could not be completed"

That looks correct.

If you run libreoffice from a terminal again ("snap run libreoffice"),
is the traceback printed again?

Can you share the output of the following command?

cat
$HOME/snap/libreoffice/current/.config/libreoffice/4/user/config/javasettings_Linux_X86_64.xml

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

Title:
  [snap] "User installation could not be completed"

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

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

-- 
Mailing list: https://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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

I can not find it; wish I had saved it.

On Mon, May 7, 2018 at 12:27 PM, Egmont Koblinger 
wrote:

> > There is a patch on gitHub for this about 3 days ago.
>
> Where exactly?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1748785).
> https://bugs.launchpad.net/bugs/1718238
>
> Title:
>   Giant terminal icon is blocking out the Terminal window buttons
>
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
> Status in ubuntu-themes package in Ubuntu:
>   Invalid
>
> Bug description:
>   Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: light-themes 16.10+17.10.20170918-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
>   Uname: Linux 4.12.0-13-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Sep 19 12:47:51 2017
>   InstallationDate: Installed on 2017-09-19 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170917)
>   PackageArchitecture: all
>   SourcePackage: ubuntu-themes
>   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/1718238/+subscriptions
>

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

-- 
Mailing list: https://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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

Wait. Try this from Christian Persch. Commit from 5 days ago.

https://github.com/GNOME/gnome-
terminal/commit/887c8128d7c528660afa53fad9ae46e72ca7297c


On Mon, May 7, 2018 at 12:27 PM, Egmont Koblinger 
wrote:

> > There is a patch on gitHub for this about 3 days ago.
>
> Where exactly?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1748785).
> https://bugs.launchpad.net/bugs/1718238
>
> Title:
>   Giant terminal icon is blocking out the Terminal window buttons
>
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
> Status in ubuntu-themes package in Ubuntu:
>   Invalid
>
> Bug description:
>   Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: light-themes 16.10+17.10.20170918-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
>   Uname: Linux 4.12.0-13-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Sep 19 12:47:51 2017
>   InstallationDate: Installed on 2017-09-19 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170917)
>   PackageArchitecture: all
>   SourcePackage: ubuntu-themes
>   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/1718238/+subscriptions
>

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1723080] Re: Caldav Issues with evolution 3.26

2018-05-07 Thread Kirk Wolff

I have the same experience on my evolution. I am using synology caldav
server (latest) and this hasn't been working for me for some time
(around a year or more). I have been running the latest ubuntu, and
presently I'm on 18.04. The attached log is from evolution v3.28.1-2
calendar-factory in debug-all mode.

** Attachment added: "Failure creating caledar object output from command
"CALDAV_DEBUG=all /usr/lib/evolution/evolution-calendar-factory""

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1723080/+attachment/5135617/+files/evolution_bug_1723080.log

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

Title:
Caldav Issues with evolution 3.26

Status in evolution package in Ubuntu:
New

Bug description:
I noticed a series of issues with caldav when switching to Ubuntu
17.10. Everthing works fine with Ubuntu GNOME 17.04.

Error message during ics import:
"Cannot receive calendar objects: Failed to put data: HTTP error code 201
(Created): The server responded with an HTML page, which can mean there’s an
error on the server or with the client request."
The import successfully finished regardless. It's still a nuisance.

Attempts to pick a date (calendar entry and tasks) are followed by the
message:
"Evolution want to inhibit shortcuts.
You can restore shortcuts by pressing Shift-Ctrl-Escape"

Creating new tasks: Same error message as for ics import. Tasks are
only stored when date *and* time are specified. Error message needs to
be ignored and window to be close with 'discard changes'.

Update of calender appointments (external): just does not work

Could not test handling of confirmations of meeting invites, yet

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

[Desktop-packages] [Bug 1723080] Re: Caldav Issues with evolution 3.26

2018-05-07 Thread Kirk Wolff

Quick note, the attachment above yields an error message from evolution
that reads:

Cannot create calendar object: Failed to put data: HTTP error code 201
(Created): The server responded with an HTML page, which can mean
there’s an error on the server or with the client request. The used URI
was:
https://synology.wolffelectronicdesign.com:5006/calendars/Kirk/8fd98e334f3a02482f68b77a2cabf68f1efa4e24.ics

The new event does not show up in the calendar until I force a refresh
of the caldav account from evolution. Note, if I attempt to modify a
calendar entry, and press 'save', I do not get an error.

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

Title:
Caldav Issues with evolution 3.26

Status in evolution package in Ubuntu:
New

Bug description:
I noticed a series of issues with caldav when switching to Ubuntu
17.10. Everthing works fine with Ubuntu GNOME 17.04.

Attempts to pick a date (calendar entry and tasks) are followed by the
message:
"Evolution want to inhibit shortcuts.
You can restore shortcuts by pressing Shift-Ctrl-Escape"

Creating new tasks: Same error message as for ics import. Tasks are
only stored when date *and* time are specified. Error message needs to
be ignored and window to be close with 'discard changes'.

Update of calender appointments (external): just does not work

Could not test handling of confirmations of meeting invites, yet

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

[Desktop-packages] [Bug 1769735] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

2018-05-07 Thread 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 hicolor-icon-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1769735

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  No se cual es el error, solo salio el msj de erorr y lo reporto

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May  6 16:55:18 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-05-08 (1460 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1769735/+subscriptions

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

[Desktop-packages] [Bug 1769736] Re: [snap] Custom app menu entries do not work

The code that creates the menu is in function ensure_dbus_setup() in
vcl/unx/gtk3/gtk3gtkframe.cxx.

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

Title:
  [snap] Custom app menu entries do not work

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When launching e.g. libreoffice.writer, the application exposes a
  custom menu in the top panel with entries to create a new document,
  open the preferences, display the help and about dialog, and exit the
  application. See attached screenshot. None of these entries have any
  effect (not even the "Quit" one).

  $ snap info libreoffice
  snap-id:   CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
  tracking:  candidate
  refreshed: 2018-05-02T15:58:07+02:00
  installed:   6.0.4.1 (61) 479MB -
  channels: 
stable:6.0.3.2 (59) 479MB -
candidate: 6.0.4.1 (61) 479MB -
beta:  ↑  
edge:  ↑  

  $ snap info core
  type:  core
  snap-id:   99T7MUlRhtI3U0QFgl5mXXESAiSwt776
  tracking:  stable
  refreshed: 2018-04-29T20:29:48+02:00
  installed:   16-2.32.6(4571) 90MB core
  channels:
stable:16-2.32.6(4571) 90MB -
candidate: 16-2.32.6(4571) 90MB -
beta:  16-2.32.6(4571) 90MB -
edge:  16-2.32.6+git710.8eefd85 (4619) 91MB -

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

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

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

[Desktop-packages] [Bug 1702351] Re: [snap] "User installation could not be completed"

2018-05-07 Thread modolo

Hi Olivier!

/snap/libreoffice/current/usr/lib/jvm/java-8-openjdk-*/jre/bin/java -version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=lcd -Dswing.aatext=true 
-Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel 
-Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel 
-Dawt.useSystemAAFontSettings=lcd -Dswing.aatext=true 
-Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel 
-Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel 
openjdk version "1.8.0_162"
OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12)
OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)

Thanks,
Marcelo Módolo

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

Title:
  [snap] "User installation could not be completed"

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

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1769735] [NEW] package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

2018-05-07 Thread Andres Mingarro

Public bug reported:

No se cual es el error, solo salio el msj de erorr y lo reporto

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: hicolor-icon-theme 0.17-2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sun May  6 16:55:18 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2014-05-08 (1460 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  No se cual es el error, solo salio el msj de erorr y lo reporto

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May  6 16:55:18 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-05-08 (1460 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1769735/+subscriptions

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

[Desktop-packages] [Bug 1769736] [NEW] [snap] Custom app menu entries do not work

Public bug reported:

When launching e.g. libreoffice.writer, the application exposes a custom
menu in the top panel with entries to create a new document, open the
preferences, display the help and about dialog, and exit the
application. See attached screenshot. None of these entries have any
effect (not even the "Quit" one).

$ snap info libreoffice
snap-id:   CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
tracking:  candidate
refreshed: 2018-05-02T15:58:07+02:00
installed:   6.0.4.1 (61) 479MB -
channels: 
  stable:6.0.3.2 (59) 479MB -
  candidate: 6.0.4.1 (61) 479MB -
  beta:  ↑  
  edge:  ↑  

$ snap info core
type:  core
snap-id:   99T7MUlRhtI3U0QFgl5mXXESAiSwt776
tracking:  stable
refreshed: 2018-04-29T20:29:48+02:00
installed:   16-2.32.6(4571) 90MB core
channels:
  stable:16-2.32.6(4571) 90MB -
  candidate: 16-2.32.6(4571) 90MB -
  beta:  16-2.32.6(4571) 90MB -
  edge:  16-2.32.6+git710.8eefd85 (4619) 91MB -

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

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


** Tags: snap

** Attachment added: "lo-app-menu.png"
   
https://bugs.launchpad.net/bugs/1769736/+attachment/5135609/+files/lo-app-menu.png

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

Title:
  [snap] Custom app menu entries do not work

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When launching e.g. libreoffice.writer, the application exposes a
  custom menu in the top panel with entries to create a new document,
  open the preferences, display the help and about dialog, and exit the
  application. See attached screenshot. None of these entries have any
  effect (not even the "Quit" one).

  $ snap info libreoffice
  snap-id:   CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
  tracking:  candidate
  refreshed: 2018-05-02T15:58:07+02:00
  installed:   6.0.4.1 (61) 479MB -
  channels: 
stable:6.0.3.2 (59) 479MB -
candidate: 6.0.4.1 (61) 479MB -
beta:  ↑  
edge:  ↑  

  $ snap info core
  type:  core
  snap-id:   99T7MUlRhtI3U0QFgl5mXXESAiSwt776
  tracking:  stable
  refreshed: 2018-04-29T20:29:48+02:00
  installed:   16-2.32.6(4571) 90MB core
  channels:
stable:16-2.32.6(4571) 90MB -
candidate: 16-2.32.6(4571) 90MB -
beta:  16-2.32.6(4571) 90MB -
edge:  16-2.32.6+git710.8eefd85 (4619) 91MB -

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

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

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

[Desktop-packages] [Bug 1768199] Re: Chromium freezes

Could you please install chrome (https://www.google.com/chrome/) and see
if the problem happens there too? Thanks!

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

Title:
  Chromium freezes

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After I updated to Ubuntu 18.04 I noticed that chromium interactions
  (scroll for example) and mouse pointer itself started to freeze for
  hundreds of milliseconds (0.1s - 0.2s).

  So, I was constantly scrolling (in order to reproduce the bug) while
  running perf top, and it pointed to this function:

  sudo perf top -t 1892 -d 5 --call-graph fp

    Children  Self  Shared Object   Symbol

  -   80,55% 0,00%  libc-2.27.so[.] __GI___ioctl
     - 76,84% __GI___ioctl
  71,67% _nv029804rm
    - 1,12% _nv020749rm
   - 1,03% os_release_spinlock
    0,97% _raw_spin_unlock_irqrestore

  -   71,69%71,67%  [kernel][k] _nv029804rm
   71,58% 0x18012a
  __GI___ioctl
  _nv029804rm

  -   16,75% 0,00%  [unknown]   [k] 0x0018012a
   0x18012a
     - __GI___ioctl
  15,25% _nv029804rm

  -8,67% 0,25%  libc-2.27.so[.] syscall
     - 5,45% syscall
  1,89% syscall_return_via_sysret
    - 1,05% entry_SYSCALL_64_after_hwframe
   - 1,22% do_syscall_64

  top command also showed that this process was eating one core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  1 10:38:19 2018
  Desktop-Session:
   'plasma'
   
'/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-12-16 (136 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  InstalledPlugins:

  Load-Avg-1min: 1.64
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e3723f86-9a4d-4166-960b-88262212fcc6 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (28 days ago)
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0408
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0408:bd08/31/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Thanks for the info Tomáš. Is temporarily switching to the proprietary
driver an option, to test whether this is indeed a problem with nouveau?

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

2018-05-07 Thread Bernadette Addison

Same issue here with official 18.04 LTS release.  I have installed HPLIP
3.18.4,  but I get the error message, No System Tray Detected on this
system: Unable to start, exiting.  What's worse is that the HP Officejet
printer will not print anything.  It just keeps sending all print jobs
to "pause".

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1702351] Re: [snap] "User installation could not be completed"

Thanks for the feedback Marcelo.
The python traceback ("AttributeError: 'NoneType' object has no attribute 
'group'") is unexpected, may I ask you to share the output of the following 
command:

/snap/libreoffice/current/usr/lib/jvm/java-8-openjdk-*/jre/bin/java
-version

Thanks!

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

Title:
  [snap] "User installation could not be completed"

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

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1769727] [NEW] Black Screen on Wake

2018-05-07 Thread chas

Public bug reported:

Mate 18.04 (64bit)
MacbookAir 1,1
Intel i915

Blackscreen after every resume. All other features work. Just no
backlight.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon May  7 13:05:50 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [106b:00a2]
   Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [106b:00a2]
InstallationDate: Installed on 2018-05-06 (1 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
MachineType: Apple Inc. MacBookAir1,1
ProcEnviron:
 LANGUAGE=en_CA
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA11.88Z.00BB.B03.0803171226
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C8CC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C8CC8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA11.88Z.00BB.B03.0803171226:bd03/17/08:svnAppleInc.:pnMacBookAir1,1:pvr1.0:rvnAppleInc.:rnMac-F42C8CC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C8CC8:
dmi.product.family: MacBook
dmi.product.name: MacBookAir1,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Black Screen on Wake

Status in xorg package in Ubuntu:
  New

Bug description:
  Mate 18.04 (64bit)
  MacbookAir 1,1
  Intel i915

  Blackscreen after every resume. All other features work. Just no
  backlight.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon May  7 13:05:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [106b:00a2]
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [106b:00a2]
  InstallationDate: Installed on 2018-05-06 (1 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Apple Inc. MacBookAir1,1
  ProcEnviron:
   LANGUAGE=en_CA
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA11.88Z.00BB.B03.0803171226
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42C8CC8
  dmi.board.vendor: Apple

[Desktop-packages] [Bug 1769727] Re: Black Screen on Wake

2018-05-07 Thread chas

see also:
https://bugs.launchpad.net/ubuntu-mate/+bug/1769726

older references:
https://bugs.launchpad.net/ubuntu-mate/+bug/1688716/+activity

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

Title:
  Black Screen on Wake

Status in xorg package in Ubuntu:
  New

Bug description:
  Mate 18.04 (64bit)
  MacbookAir 1,1
  Intel i915

  Blackscreen after every resume. All other features work. Just no
  backlight.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon May  7 13:05:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [106b:00a2]
 Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [106b:00a2]
  InstallationDate: Installed on 2018-05-06 (1 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Apple Inc. MacBookAir1,1
  ProcEnviron:
   LANGUAGE=en_CA
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA11.88Z.00BB.B03.0803171226
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42C8CC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42C8CC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA11.88Z.00BB.B03.0803171226:bd03/17/08:svnAppleInc.:pnMacBookAir1,1:pvr1.0:rvnAppleInc.:rnMac-F42C8CC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C8CC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBookAir1,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2018-05-07 Thread Egmont Koblinger

> There is a patch on gitHub for this about 3 days ago.

Where exactly?

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1164016] Re: restore type-ahead find

2018-05-07 Thread Ljiljan Veselinovic

In Ubuntu 18.04 this problem is now present again :-( it is really
annoying...

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

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

2018 May 7. Obscuring icon remains. Did fresh install last night with
all updates. There is a patch on gitHub for this about 3 days ago. Has
it been incorporated by Ubuntu? Does it fix the issue?

** Attachment added: "Screenshot of terminal with obscuring icon."
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1718238/+attachment/5135575/+files/Screenshot_2018-05-07_11-32-04.png

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Desktop-packages] [Bug 1705188] Re: GIMP color picker does not work in Wayland

2018-05-07 Thread corrado venturini

Still same problem with Gimp 2.10 in Ubuntu Cosmic 18.10

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

Title:
  GIMP color picker does not work in Wayland

Status in The Gimp:
  Confirmed
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  GIMP color picker does not work in Wayland, it returns just black.
  It seems a common problem for 'pick' function in Wayland:  
https://bugs.launchpad.net/ubuntu/+source/gpick/+bug/1704808

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

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

[Desktop-packages] [Bug 1766799] Re: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)

2018-05-07 Thread MBWD

Running Ubuntu 18.04 in a GNOME Xorg session, I get the same error when
attempting to launch 'gnome-control-center':

`ERROR:../shell/cc-panel-list.c:926:cc_panel_list_set_active_panel: assertion 
failed: (data != NULL)
Aborted (core dumped)`

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

Title:
  gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 →
  cc_panel_list_set_active_panel → assertion failed → (data != NULL)

Status in gnome-control-center package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1769720] [NEW] Logged out when unplugging external monitors with screen locked and lid closed

2018-05-07 Thread Jonathan Kamens

Public bug reported:

I am using Ubuntu 18.04 (Bionic) 64-bit on a System76 Galaga UltraPro
laptop. At work, I plug two displays into my laptop, one DisplayPort and
one HDMI.

If, while both displays are plugged in and the laptop lid is closed and
the laptop's built-in display is therefore disabled, I:

1. lock my screen;
2. unplug both displays at about the same time;
3. wait about ten seconds; and then
4. open my laptop lid,

I find that I have been logged out.

If I immediately log back in to the built-in display, a couple seconds
after I log in, the screen locks. If I then immediately log out and log
back in again, the screen does _not_ lock.

It seems that this weird lock-right-after-login behavior is related to
the fact that I get logged out as described above. It seems that the
shell remembers that it is supposed to be locked despite the crash /
logout, such that when I log back in, it realizes that it's supposed to
be locked and locks itself.

Note that I am filing this bug as instructed in
https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/105: "BTW,
we have fixed many gnome-shell bugs with these symptoms recently in
Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
problems."

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May  7 14:26:22 2018
DisplayManager: gdm3
InstallationDate: Installed on 2016-08-09 (635 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-04-27 (10 days ago)

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


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

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

Title:
  Logged out when unplugging external monitors with screen locked and
  lid closed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 18.04 (Bionic) 64-bit on a System76 Galaga UltraPro
  laptop. At work, I plug two displays into my laptop, one DisplayPort
  and one HDMI.

  If, while both displays are plugged in and the laptop lid is closed
  and the laptop's built-in display is therefore disabled, I:

  1. lock my screen;
  2. unplug both displays at about the same time;
  3. wait about ten seconds; and then
  4. open my laptop lid,

  I find that I have been logged out.

  If I immediately log back in to the built-in display, a couple seconds
  after I log in, the screen locks. If I then immediately log out and
  log back in again, the screen does _not_ lock.

  It seems that this weird lock-right-after-login behavior is related to
  the fact that I get logged out as described above. It seems that the
  shell remembers that it is supposed to be locked despite the crash /
  logout, such that when I log back in, it realizes that it's supposed
  to be locked and locks itself.

  Note that I am filing this bug as instructed in
  https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/105:
  "BTW, we have fixed many gnome-shell bugs with these symptoms recently
  in Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
  problems."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 14:26:22 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-09 (635 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (10 days ago)

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

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

[Desktop-packages] [Bug 1769500] Re: will not update

2018-05-07 Thread Leonidas S. Barbosa

** Information type changed from Private Security to Public

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

Title:
  will not update

Status in xorg package in Ubuntu:
  New

Bug description:
  will not update. Gives error msg public key 8BAF9A6F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May  6 15:07:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] [1002:9804] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6250] [103c:3577]
  InstallationDate: Installed on 2017-11-26 (161 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=ed27f603-858e-45f5-9ba1-0b1789b36c0f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.48
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.4A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068C11000320491620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  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
  xserver.bootTime: Sat May  5 13:58:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1766799] Re: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)

2018-05-07 Thread Pat Suwalski

I have this error occurring when I run the regular GNOME session.

In Ubuntu session, control panel works. In GNOME session, settings does
not launch. Launching "gnome-control-center" from terminal provides the
core dump message initially reported.

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

Title:
  gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 →
  cc_panel_list_set_active_panel → assertion failed → (data != NULL)

Status in gnome-control-center package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1769213] Re: /usr/bin/gnome-control-center:11:gtk_style_context_clear_property_cache:gtk_style_context_finalize:g_object_unref:gtk_widget_finalize:g_object_unref

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

** This bug has been marked a duplicate of bug 1759468
   gnome-control-center (11) gtk_style_context_clear_property_cache → 
gtk_css_widget_node_update_style → gtk_css_node_ensure_style → 
gtk_css_node_ensure_style → gtk_css_node_validate_internal

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

Title:
  /usr/bin/gnome-control-
  
center:11:gtk_style_context_clear_property_cache:gtk_style_context_finalize:g_object_unref:gtk_widget_finalize:g_object_unref

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

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

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

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

[Desktop-packages] [Bug 1759282] Re: randomly become unable to open new Nautilus windows

2018-05-07 Thread teo1978

Importance low? You must really be retarded.

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

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

Title:
  randomly become unable to open new Nautilus windows

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  At random times after having the system running for a few hours this
  starts happening:

  - I don't have any Nautilus window open (I previously dad and at some point 
closed all of them)
  - I click on Nautilus' launcher icon
  - it kind of blinks for like 30 seconds (by the way, that's barely 
noticeable, that sucks on its own)

  and then nothing happens, no Nautilus window opens up, no error
  message shows up (that's another thing that is wrong on its own, you
  should ALWAYS get an error message when something fails) and the
  Launcher icon finally stops blinking.

  I retry a few times, same result.

  So I open a terminal and try to launch Nautilus from there, so at
  least I get the fucking error messages:

  $ nautilus

  (nautilus:18764): GLib-GIO-CRITICAL **:
  g_dbus_interface_skeleton_unexport: assertion
  'interface_->priv->connections != NULL' failed

  (nautilus:18764): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: 
assertion 'interface_->priv->connections != NULL' failed
  Could not register the application: Timeout was reached

  (nautilus:18764): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:18764): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:18764): GLib-GObject-CRITICAL **: g_signal_connect_object:
  assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed


  For fuck's sake please switch to some other file manager, Nautilus is
  pathetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 27 16:03:32 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1197x691+309+248'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1627 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-05-07 Thread Артем

And more. Different output of the command: cat
/sys/kernel/debug/vgaswitcheroo/switch

nouveau driver:
0:IGD:+:Pwr::00:02.0
1:DIS: :DynOff::01:00.0

nvidia 390.48, after prime-select intel:
0:IGD:+:Pwr::00:02.0
1:DIS: :Off::01:00.0

You can see the different status of the discrete card. When "DunOff" it
really disconnected from the power supply, and in case of "Off" it
continues to consume energy.

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

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

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

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

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

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

[Desktop-packages] [Bug 1769695] [NEW] Freeze of Surface for 2 Minutes

2018-05-07 Thread David Georg Reichelt

Public bug reported:

I am using a fresh installed Ubuntu 18.04 on an RX 480 and an i5 7600.
3.28.0-0ubuntu1 is running. Normaly, everything runs fine, but lately
when I had some windows open (eclipse, Texmaker, Terminal, Firefox with
Youtube and other windows) the system suddenly was nearly frozen, I
could move the mouse and change active windows by ctrl+tab but not use
the keyboard e.g. for typing into windows or make any actions with the
mouse (e.g. open menues, click on menues, ..).

When I changed the session by Ctrl+Alt+F3 and then killed firefox,
everything worked again. I do not know whether this is a Firefox, a gdm
or a graphics driver issue. Since a program should not be able to make
the desktop crash at all, I suppose its not Firefox and so I post it
here.

/var/log/syslog around the time contains the following (even if it
contains some device removed code, I did not do anything with the cables
and am sure that there isn't a hardware defect with mouse and keyboard):

May  7 17:27:40 reichelt-desktop nautilus[3278]: Called "net usershare info" 
but it failed: Kindprozess »net« konnte nicht ausgeführt werden (No such file 
or directory)
May  7 17:27:53 reichelt-desktop java[11096]: gtk_widget_size_allocate(): 
attempt to allocate widget with width 12 and height -12
May  7 17:27:53 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkScrollbar
May  7 17:27:53 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:27:53 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:27:53 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x4402269 (Run Config)
May  7 17:27:54 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:28:15 reichelt-desktop java[11096]: message repeated 2 times: [ 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton]
May  7 17:28:18 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x44002d3 (dissworksp)
May  7 17:28:18 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x4403e58 (Open Resou)
May  7 17:28:20 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x44002d3 (dissworksp)
May  7 17:28:22 reichelt-desktop java[11096]: gtk_widget_size_allocate(): 
attempt to allocate widget with width 12 and height -12
May  7 17:28:22 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkScrollbar
May  7 17:28:22 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:28:22 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:28:22 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x4404745 (Run Config)
May  7 17:28:23 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:28:25 reichelt-desktop java[11096]: message repeated 2 times: [ 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton]
May  7 17:28:26 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x4405147 (Confirm La)
May  7 17:28:27 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x4404745 (Run Config)
May  7 17:28:27 reichelt-desktop java[11096]: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkRadioButton
May  7 17:29:31 reichelt-desktop java[11096]: message repeated 5 times: [ 
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkRadioButton]
May  7 17:29:34 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x44002d3 (dissworksp)
May  7 17:29:35 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x4406400 (Open Type )
May  7 17:29:38 reichelt-desktop org.gnome.Shell.desktop[2203]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x44002d3 (dissworksp)
May  7 17:29:40 reichelt-desktop java[11096]: gtk_widget_size_allocate(): 
attempt to allocate widget with width 12 and height -12
May  7 17:29:40 reichelt-desktop java[11096]:

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

2018-05-07 Thread Francesco Fumanti

I am experiencing the same problem on bionic.

My system is an upgrade from artful.

The NFS shares are mounted at: 
/media/sharename 

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

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

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

Title:
  Mounted Volume ICON not displayed on desktop

Status in nautilus package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

2018-05-07 Thread Brian Murray

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

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

Title:
  Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  how to reproduce:

  dd the iso to an usb drive and boot from it.
  List all wifi devices in live-mode and connect to one of it. Use the web for 
some minutes. Open up the wifi on the top right again and list the available 
networks - it dont show any others any more. Just the one you are connected to.

  How to overcome the bug: put the computer into airplane mode and go
  away from airplane mode again. Or: disconnect the usb wifi device and
  connect it again.

  Does this bug exist also on installed 18.04 and updated to last (apt update, 
apt upgrade, apt dist-upgrade)?
  Yes

  What wifi device is been used:
  ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
  ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected
  ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  usbcore: registered new interface driver rt2800usb
  ...
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 
'rt2870.bin'
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - 
version: 0.36

  uname -a
  Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1769480] [NEW] Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

You have been subscribed to a public bug:

how to reproduce:

dd the iso to an usb drive and boot from it.
List all wifi devices in live-mode and connect to one of it. Use the web for 
some minutes. Open up the wifi on the top right again and list the available 
networks - it dont show any others any more. Just the one you are connected to.

How to overcome the bug: put the computer into airplane mode and go away
from airplane mode again. Or: disconnect the usb wifi device and connect
it again.

Does this bug exist also on installed 18.04 and updated to last (apt update, 
apt upgrade, apt dist-upgrade)?
Yes

What wifi device is been used:
ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
usbcore: registered new interface driver rt2800usb
...
ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 
'rt2870.bin'
ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 
0.36

uname -a
Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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


** Tags: bot-comment
-- 
Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
https://bugs.launchpad.net/bugs/1769480
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager 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 1754199] Re: Mounted Volume ICON not displayed on desktop

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

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

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

Title:
  Mounted Volume ICON not displayed on desktop

Status in nautilus package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1750352] Re: gnome-shell freeze on key press while high CPU load

2018-05-07 Thread monkeydri

sorry for need updating this bug report, I had switched back to xorg
because of too many bugs in wayland. Now running bionic 18.04 which use
xorg by default. Can't say it is a bad decision, it feels like 17.10 was
for beta testing whereas not advertised as such.

After testing over a month, this gnome-shell issue on wayland was
tailored to clipboard-indicator use. It did not appear without this
extension. But this is clearly is gnome-shell issue (it should not crash
so easily and freeze the entire system).

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

Title:
  gnome-shell freeze on key press  while high CPU load

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  This bug happens randomly (once an hour), on keyboard input in
  different apps, ex Firefox address bar, Alfred launcher or Gnome
  Overview.

  I could not find steps to reproduce (tried reducing keyboard interval
  and repeated keypress following STRs from #1731420 but it did not
  freeze, though CPU use increased).

  System is completely frozen, cannot switch to TTY, but music continues
  to play. Sometimes it logs out but most of the time I have to force
  reboot by long pressing the shutdown key.

  syslog show message : "Key repeat discarded, Wayland compositor
  doesn't seem to be processing events fast enough!" multiple times.

  Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693

  Ubuntu 17.10 with Gnome session on wayland.
  Gnome-Shell 3.26.2-0ubuntu0.1
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: lightdm
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-11-28 (83 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo 
wireshark www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

2018-05-07 Thread dino99

also concerned  https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=898115#12

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

Title:
  Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

Status in fonts-liberation package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in fonts-liberation package in Debian:
  New
Status in fonts-liberation2 package in Debian:
  New

Bug description:
  Ubuntu/Xubuntu 18.04 package includes fonts "Liberation Sans" (etc
  "Liberation") with sligtly shrinked font metrics. This issue leads to
  all office documents typed in Liberation Sans fonts have corrupted
  formatting in Ubuntu 18.04 (but these documents correctly opened in
  other OS's, for example Ubuntu 17.10). Documents with corrupted
  formatting can not print properly: all paragraphs are shifted up,
  embedded tables in text - splitted on page breaks. Document
  circulation in system based on Ubuntu 18.04 operating systems
  temporarily paralized, because Liberation fonts are basic fonts for
  open-source document circulation.

  In attachment I have type a example office document with 2 pages and
  enumerated strings. On normal ordinary conditions this document have
  54 strings on first page and 54 string on second page. But if this
  document open in Ubuntu 18.04, it's found than 5 strings from second
  page moves to first page. Compare font versions embedded with Ubuntu
  packages we can see that versions are different (sudo apr search
  fonts-liberation* command):

  Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3
  Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5

  I have create a bug 117411 "Font metrics slightly changed after update
  OS to Ubuntu 18.04", see
  https://bugs.documentfoundation.org/show_bug.cgi?id=117411, but I
  think that this bug concerns a Ubuntu/Xubuntu 18.04 package.

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

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

[Desktop-packages] [Bug 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

2018-05-07 Thread dino99

Possibly fixed  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898116#10
Please sync asap

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

Title:
  Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

Status in fonts-liberation package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in fonts-liberation package in Debian:
  New
Status in fonts-liberation2 package in Debian:
  New

Bug description:
  Ubuntu/Xubuntu 18.04 package includes fonts "Liberation Sans" (etc
  "Liberation") with sligtly shrinked font metrics. This issue leads to
  all office documents typed in Liberation Sans fonts have corrupted
  formatting in Ubuntu 18.04 (but these documents correctly opened in
  other OS's, for example Ubuntu 17.10). Documents with corrupted
  formatting can not print properly: all paragraphs are shifted up,
  embedded tables in text - splitted on page breaks. Document
  circulation in system based on Ubuntu 18.04 operating systems
  temporarily paralized, because Liberation fonts are basic fonts for
  open-source document circulation.

  In attachment I have type a example office document with 2 pages and
  enumerated strings. On normal ordinary conditions this document have
  54 strings on first page and 54 string on second page. But if this
  document open in Ubuntu 18.04, it's found than 5 strings from second
  page moves to first page. Compare font versions embedded with Ubuntu
  packages we can see that versions are different (sudo apr search
  fonts-liberation* command):

  Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3
  Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5

  I have create a bug 117411 "Font metrics slightly changed after update
  OS to Ubuntu 18.04", see
  https://bugs.documentfoundation.org/show_bug.cgi?id=117411, but I
  think that this bug concerns a Ubuntu/Xubuntu 18.04 package.

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

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

[Desktop-packages] [Bug 1769684] [NEW] audio crashes on start up and volume slider does not control volume output levels (Can only be muted or at max volume)

2018-05-07 Thread Christopher Leong

Public bug reported:

using alsa-mixer master volume changes with audio slider but output
volume does not change but can still be muted.

- changing PCM values directly changes output volume still works
- This problem does not occur when headphones are plugged in even after start up

Description:Ubuntu 16.04.4 LTS
Release:16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neo2345 F pulseaudio
  neo3794 F alsamixer
CurrentDesktop: Unity
Date: Mon May  7 22:53:40 2018
InstallationDate: Installed on 2018-05-04 (3 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550VE.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550VE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.304:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX550VE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-05T00:06:39.133243

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  audio crashes on start up and volume slider does not control volume
  output levels (Can only be muted or at max volume)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  using alsa-mixer master volume changes with audio slider but output
  volume does not change but can still be muted.

  - changing PCM values directly changes output volume still works
  - This problem does not occur when headphones are plugged in even after start 
up

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neo2345 F pulseaudio
neo3794 F alsamixer
  CurrentDesktop: Unity
  Date: Mon May  7 22:53:40 2018
  InstallationDate: Installed on 2018-05-04 (3 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.304:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-05T00:06:39.133243

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

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

[Desktop-packages] [Bug 1702351] Re: [snap] "User installation could not be completed"

2018-05-07 Thread modolo

Hi!

Working without errors!

sudo snap install libreoffice
libreoffice 6.0.3.2 from 'canonical' installed

sudo snap list
Name VersionRev   Tracking  Developer   Notes
cointop  e0fc5b337stablemiguelmota  -
core 16-2.32.6  4571  stablecanonical   core
libreoffice  6.0.3.259stablecanonical   -
tizonia  0.14.0 155   stabletizonia -

snap run libreoffice
Traceback (most recent call last):
  File "/snap/libreoffice/59/javasettings.py", line 41, in 
java_output).group("version")
AttributeError: 'NoneType' object has no attribute 'group'
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"

Thanks,
Marcelo Módolo

** Attachment added: "nsswitch.conf"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702351/+attachment/5135493/+files/nsswitch.conf

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

Title:
  [snap] "User installation could not be completed"

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

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-07 Thread Bernadette Addison

Back to where I started with a non-bootable machine, after modifying
xorg.conf listed in post #121.  I will go aheada purge these nvidia
drivers again, and try #123 to see if that works.  This is a crazy
mess!!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

2018-05-07 Thread Tomáš Myšík

$ glxinfo | grep OpenGL
OpenGL vendor string: nouveau
OpenGL renderer string: NV117
OpenGL core profile version string: 4.3 (Core Profile) Mesa 18.0.0-rc5
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.0-rc5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.0-rc5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

2018-05-07 Thread Tomáš Myšík

Unfortunately, it did not help. Starting in safe mode gives me the same
error. Adding OpenGL values to the configuration file (they were not
present there) did not help either :/

What comes to my mind - I have nVidia graphic card but using the OS
driver, not the closed-sourced one. Could this be the cause? Or, maybe I
am missing some "library" (vdpau or vaapi or whatever...)?

Thanks a lot!

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c