date:20190326

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

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

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

Title:
  gnome-shell filling up syslog with thousands/millions of entries with
  stack traces ending in osdWindow.js (lines 206/207 in bionic, lines
  223/224 in cosmic)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  I'm seeing a several gigs (more than 70GB) a day of
  org.gnome.Shell.desktop log entries.

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  [Test Case]

  With 2 monitors connected, simply lock the screen and leave it locked
  for a while. The error messages will be logged into syslog until all
  the empty space is filled up.

  More info:
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243

  [Regression Potential]

  Low. The fix (https://gitlab.gnome.org/GNOME/gnome-
  shell/merge_requests/243) is a minor correction to window destroy
  logic, written by the main Gnome Shell maintainer.

  [Original Description]

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90),

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

The above commit was just an optional optimization (that I personally
pushed Carlos to revive and land). It doesn't fix anything in particular
so if you need to revert it to get over the line then I think that's OK.

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

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

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

** Tags removed: rls-bb-notfixing

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [ Fix ]

  See below for the changes from upstream that fix this, which we're
  uploading to disco-proposed now.

  [ QA ]

  Under the GNOME Micro Release Exception, you can believe this is
  fixed.

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

  It might be a good idea to test an nvidia machine, but it doesn't need
  explicit verification.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  cogl_texture_get_height(texture=0x0) from
  clutter_offscreen_effect_real_paint_target() from
  clutter_offscreen_effect_paint_texture() from
  clutter_offscreen_effect_paint() from clutter_actor_continue_paint()

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

Bug description:
  [ Impact ]

  Gnome shell crashes on cogl_texture_get_height

  [ Test case ]

  No clear reproducer is know for such issue, crashes should be
  monitored in e.u.c checking that this is not happening anymore for the
  version in proposed.

  [ Regression potential ]

  Low, the proposed fix is part of the current stable branch upstream
  and not changed in further revisions.

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/e5b2dcb04552882a76f1daa6b9f18ba864269d26 
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/mutter/+bug/1795774/+subscriptions

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

[Desktop-packages] [Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt

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

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

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

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

Bug description:
  [ Impact ]

  Gnome shell crashes on double free

  Problem is occurring if dual monitor is used. Second monitor is
  repeatingly blank and activated again. At the bottom it probably
  contains the upper part of the first monitor. I had the same problem
  at 18.04 when using gdm3 without wayland during logon.

  [ Test case ]

  - Run gnome-shell with multimonitor
  - No flashing should happen on gdm initialization

  Also we should monitor crashes in e.u.c

  [ Regression potential ]

  Low, the proposed fix is part of the current stable branch upstream
  and not changed in further revisions.

  --

  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic i686
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: i386
  AssertionMessage: double free or corruption (fasttop)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 21:02:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_signal_restore_set (set=0xbfcd5e9c) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
   __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
   __GI_abort () at abort.c:79
   __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption 
(fasttop)") at malloc.c:5350
  Title: gnome-shell assert failure: double free or corruption (fasttop)
  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/mutter/+bug/1790525/+subscriptions

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

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

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

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

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

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  [ Impact ]

  Keyboard Layout indicator don't display current layout (empty selected
  drop down box)

  [ Test case ]

  1. Boot
  2. Suspend or lock the screen
  3. Log again with your user
  4. The keyboard indicator should display current layout

  [ Regression Potential ]

  Really low, we properly pass a null value instead of an undefined one,
  without breaking JS.

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  [ Workarounds ]

  - Switch with keyboard (Super+space) or mouse. BUT if you then logout
  on the login screen *when you press the first character* of the
  password the shown selected keyboard layout resets.

  - Restart Gnome Shell (Alt+F2 r):
  https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

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

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

[Desktop-packages] [Bug 1348596] Re: Nautilus shows full dvd as blank

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

Title:
  Nautilus shows full dvd as blank

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Package version: 1:3.10.1-0ubuntu9.3

  *-cdrom
  description: DVD writer
   product: DVD-RW  DVR-215D
   vendor: PIONEER
   physical id: 0.0.0
   bus info: scsi@1:0.0.0
   logical name: /dev/cdrom
   logical name: /dev/sr0
   version: 1.13
   capabilities: removable audio cd-r cd-rw dvd dvd-r
   configuration: ansiversion=5 status=nodisc

  *-cdrom
   description: DVD writer
   product: DVD-RW  DVR-215D
   vendor: PIONEER
   physical id: 0.0.0
   bus info: scsi@2:0.0.0
   logical name: /dev/sr1
   version: 1.13
   capabilities: removable audio cd-r cd-rw dvd dvd-r
   configuration: ansiversion=5 status=nodisc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 25 13:14:26 2014
  GsettingsChanges: 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 2014-07-23 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  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/1348596/+subscriptions

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

[Desktop-packages] [Bug 1348587] Re: [wishlist]Nautilus>behaviour .run

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

Title:
  [wishlist]Nautilus>behaviour .run

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Package version:1:3.10.1-0ubuntu9.3

  Run executable text files when they are opened should be selected by
  default

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 25 13:05:42 2014
  GsettingsChanges: 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 2014-07-23 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  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/1348587/+subscriptions

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

[Desktop-packages] [Bug 1286442] Re: Inserting an empty CD-R or DVD(+/-)R always results in a "Could not mount" dialog popping up

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

Title:
  Inserting an empty CD-R or DVD(+/-)R always results in a "Could not
  mount" dialog popping up

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Inserting an empty CD-R or DVD(+/-)R often results in a "Could not
  mount" dialog popping up on top of the "what do you want to do with
  this thing you've inserted?" one.

  This has been happening for a few releases, and on multiple machines.
  With both USB and SATA DVD writers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  1 06:20:54 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-06-02 (271 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2013-12-05 (85 days ago)

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

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

[Desktop-packages] [Bug 1341361] Re: Nautilus fails to copy audio files to Dell Android tablet.

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

Title:
  Nautilus fails to copy audio files to Dell Android tablet.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Most files seem to copy, but when copying a bunch of mp3 files from
  Sansa device to Dell device, it completely freezes and greys out. I
  tried this twice.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.2
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sun Jul 13 15:58:45 2014
  EcryptfsInUse: Yes
  GsettingsChanges:
   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', 'owner', 'group', 'permissions', 'mime_type', 'where', 
'date_accessed']"
  InstallationDate: Installed on 2013-11-23 (232 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (85 days ago)

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

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

[Desktop-packages] [Bug 1306319] Re: Nautilus file transfer hangs while transferring TO a share

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

Title:
  Nautilus file transfer hangs while transferring TO a share

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Similar bugs seem to be reported but none seem to match since 2012.

  If I choose files on a local machine and paste them to a location on a
  server (smb, mounted via fstab/cifs), nautilus will transfer
  approximately half the files then stop.  I am using wifi.  Cannot
  cancel job.  However; if I open another file manager, and cut and
  pasteremaining files  from there (smacefm, dolphin), the file transfer
  dialog in nautilus will end appropriately.

  I have had this issue since 13.04 on all my machines with different
  architectures.  It remains unresolved in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  Uname: Linux 3.14.0-031400-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 10 21:18:31 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 'where', 
'mime_type', 'octal_permissions', 'owner', 'permissions']"
  ProcEnviron:
   LANGUAGE=en_US
   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)

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

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

[Desktop-packages] [Bug 1347645] Re: Nautilus frames provide incorrect accessibility info for menus

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

Title:
  Nautilus frames provide incorrect accessibility info for menus

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  The Nautilus frames exposes incorrect a11y info for menus.

  To reproduce:
  1. Open any folder in the Nautilus.
  2. Install (if not installed) Accerciser Accessibility Explorer.
  3. Browse the accessibility info for opened folder frame.

  Physically (by default) the menu items are located in the global menu.
  But according to the exposed accessible tree the menu items parent has
  unknown role and negative coordinates [-2147483648; -2147483648] and
  zero sizes, the screen coordinates of menu items  are wrong (it is
  placed near the top left corner of the folder frame).

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

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

[Desktop-packages] [Bug 1273498] Re: cant load digital camera to 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/1273498

Title:
  cant load digital camera to computer

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  cant load my fuji finepix 3300 camera to computer can you tell me why

  ProblemType: Bug
  Architecture: lpia
  Date: Tue Jan 28 01:05:59 2014
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/nautilus
  NonfreeKernelModules: wl
  Package: nautilus 1:2.22.5.1-0ubuntu1netbook1
  PackageArchitecture: lpia
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.24-29-lpia i686
  UnreportableReason: This is not a genuine Ubuntu package

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

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

[Desktop-packages] [Bug 1463863] Re: SAMBA connections cause nautilus gui to hang for a long time (~5 mins)

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

Title:
  SAMBA connections cause nautilus gui to hang for a long time (~5 mins)

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  If I open a SAMBA connection and lose wifi, when I re-connect and
  attempt to re-open the SAMBA connection, the nautilus gui freezes.

  If I then kill the nautilus process and start it again, it takes a
  long time to load the gui, and the SAMBA connections are not able to
  re-open. There is no "loading" icon in the lower right hand corner of
  the screen.

  After I run:
  pkill gvfsd-smb

  I am able to re-open the SAMBA connections as normal.

  Nautilus does not report any error messages that I can see when it
  freezes.

  I am running:

  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  nautilus:
Installed: 1:3.10.1-0ubuntu9.8
Candidate: 1:3.10.1-0ubuntu9.8
Version table:
   *** 1:3.10.1-0ubuntu9.8 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

[Desktop-packages] [Bug 1318816] Re: Limited data copy speeds USB hardisk

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

Title:
  Limited data copy speeds USB hardisk

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When trying to copy data via nautilus to my 1TB WDC WD10TPVT-00U4RT1
  (01.01A01) hard disk using Ubuntu 14.04 64bit data copy speeds are
  limited with huge delays inbetween copies. I smart tested the disk
  fully on both Ubuntu 14.04 Windows 7 and with the Western digital tool
  it appears ok.

  For example If i select a 23GB folder with a few files and copy it can
  start copying get to 777mb and freeze for periods of more than an hour
  before trying to start again. There appears to be disk activity in
  periodic phases and only short amounts of data is transfered.

  The application System load indicator application seems to show disk
  I/O wait times gradually increase to 75% and above

  Copying to the same hard disk under Windows 7 and Ubuntu 12.04.4 64bit
  transfers normally and at a much higher speed

  Please let me know if I can provied any other logs

  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  nautilus:
Installed: 1:3.10.1-0ubuntu9
Candidate: 1:3.10.1-0ubuntu9
Version table:
   *** 1:3.10.1-0ubuntu9 0
  500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 12 21:28:55 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: 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 2014-04-18 (24 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  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/1318816/+subscriptions

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

[Desktop-packages] [Bug 1329399] Re: menu key problem

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

Title:
  menu key problem

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When the Menu Key is pressed (on the keyboard) it opens a context menu/app, 
when i press it again (without closing the first context menu) it generates 
another context menu, and doesnt delete the first one. It does NOT replace the 
first context menu, when creating another one.
  That happens only in the desktop and nautilus
  ---
  diegos@diegos-NCL60:~$ LANG= lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  diegos@diegos-NCL60:~$ LANG= uname -a
  Linux diegos-NCL60 3.15.0-031500-generic #201406081435 SMP Sun Jun 8 18:36:00 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  diegos@diegos-NCL60:~$ LANG= apt-cache policy compiz
  compiz:
Installed: 1:0.9.11+14.04.20140423-0ubuntu1
Candidate: 1:0.9.11+14.04.20140423-0ubuntu1
Version table:
   *** 1:0.9.11+14.04.20140423-0ubuntu1 0
  500 http://ar.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  Uname: Linux 3.15.0-031500-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  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
  CurrentDesktop: Unity
  Date: Thu Jun 12 14:11:05 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: COMPAL Electronics Inc Device [14c0:0051]
  InstallationDate: Installed on 2014-06-08 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Compal NCL60/61
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-031500-generic 
root=UUID=843fed2d-20bf-4567-9be7-980658ef4e68 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NCL60/61
  dmi.board.vendor: Compal
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd11/10/2011:svnCompal:pnNCL60/61:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
  dmi.product.name: NCL60/61
  dmi.product.version: F01
  dmi.sys.vendor: Compal
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jun 12 11:56:34 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1439 
   vendor BOE
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1274042] Re: nautilus pop-up window stop responding after install 'libpam-smbpass'

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

Title:
  nautilus pop-up window stop responding after install 'libpam-smbpass'

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I was trying to share a folder on a Windows network without using a
  terminal on ubuntu GNOME 13.10 amd64 so I've

  -selected the folder that I wanted to share
  -did right-click on it
  -selected 'sharing-options'
    (then a pop-up window appeard asking to install 'libpam-smbpass')
  -clicked 'install'

  The package were installed correctly, but the  window stop
  responding(I'll attach a screenshot of the problem)

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

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

[Desktop-packages] [Bug 1310535] Re: The “Safely remove” option for USB disks in nautilus is not working any more in 14.04.

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

Title:
  The “Safely remove” option for USB disks in nautilus is not working
  any more in 14.04.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I tried to safely remove a USB external hard disk, but the system will 
automatically remount it again and again...
  This bug is in the both versions of Unity and Gnome 14.04 version. I didn't 
test other versions.

  I found other people have the same issue:
  http://ubuntuforums.org/showthread.php?t=2218520=12995811#post12995811

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

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

[Desktop-packages] [Bug 1320742] Re: Freeze when selecting all in Bluetooth Camera.

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

Title:
  Freeze when selecting all in Bluetooth Camera.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When connected to Android phone, browsing DCIM/camera via bluetooth,
  it freezes when selecting all.

  Maybe Bluetooth is crashing with a large number of files?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.1
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 18 20:55:11 2014
  EcryptfsInUse: Yes
  GsettingsChanges:
   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', 'owner', 'group', 'permissions', 'mime_type', 'where', 
'date_accessed']"
  InstallationDate: Installed on 2013-11-23 (176 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (29 days ago)

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

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

[Desktop-packages] [Bug 1513729] Re: Can't rename files correctly in Nautilus using alt-gr for special keys

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

Title:
  Can't rename files correctly in Nautilus using alt-gr for special keys

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have the Swedish keyboard installed and I cannot use any of these
  symbols when renaming files in Nautilus @£$€{[]}. To create the
  symbols I am required to push the Alt-gr button but since the last few
  Ubuntu releases pressing Alt-gr behaves like a cancel button and
  returns renaming prompt back to non-edit mode.  Has been like this for
  a long time now.

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

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

[Desktop-packages] [Bug 1763969] Re: nautilus crashed with SIGSEGV in _int_malloc()

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 14 18:28:18 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f8e59f8c20e <_int_malloc+3902>: cmp
%rcx,0x28(%rdx)
   PC (0x7f8e59f8c20e) ok
   source "%rcx" ok
   destination "0x28(%rdx)" (0x0022) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f8e5a2e2c40 , 
bytes=bytes@entry=2080) at malloc.c:4028
   _int_memalign (av=0x7f8e5a2e2c40 , alignment=1024, 
bytes=) at malloc.c:4694
   _mid_memalign (address=, bytes=1008, alignment=) at malloc.c:3314
   __posix_memalign (memptr=0x7ffd5be7cdb0, alignment=, 
size=1008) at malloc.c:5369
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1718566] Re: Private folder appears on desktop.

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

Title:
  Private folder appears on desktop.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  To replicate:
  1: Set up encryptfs to mount automatically on $HOME/Private
  2: Log in using any desktop environment which uses Nautilus to manage the 
desktop icons.

  Expected results:
  My private folder should not appear on the desktop unless I explicitly link 
it.

  Actual results:
  My private folder is displayed as an icon on the desktop, and if I open my 
home directory in Nautilus there is a disk emblem on my private folder. Both of 
these are regressions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-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: Thu Sep 21 14:25:54 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-15 (36 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-09-14 (6 days ago)

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

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

[Desktop-packages] [Bug 1714797] Re: Pressing eject button in Gnome Files displays message that internal DVD-ROM drive can be removed

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

Title:
  Pressing eject button in Gnome Files displays message that internal
  DVD-ROM drive can be removed

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Pressing the eject button (in the Gnome Files user interface, not the
  physical button on the drive) for an internal SATA DVD-ROM drive
  causes a message to appear that the drive can be removed. After this,
  the drive is no longer accessible from within Gnome Files until the
  computer is rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.25.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 12:19:52 2017
  InstallationDate: Installed on 2017-09-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  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)

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

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

[Desktop-packages] [Bug 1680118] Re: Login for network share is not storable as Anonymous

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

Title:
  Login for network share is not storable as Anonymous

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have some networks shares in our office which are not secured with
  passwords. Unfortunately nautilus is prompting every time I want to
  connect to these shares. When I enter a username and password I can
  store these credentials in my keyring, if I want to connect as
  Anonymous I can not do so and Nautilus prompts again for the login
  next time it wants to mount the share. Storing my choice also as
  Anonymous would be a nice feature. I add a screenshot for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: fxmc_usb gxsd prl_fs_freeze prl_fs prl_eth prl_tg
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  5 11:25:14 2017
  InstallationDate: Installed on 2016-10-23 (163 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/1680118/+subscriptions

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

[Desktop-packages] [Bug 1722028] Re: nautilus dead when renaming folder after creating 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/1722028

Title:
  nautilus dead when renaming folder after creating folder

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Hello!

  This record is for bug evidence in ubuntu 17.04 nautilus 3.20.4
  Please check this bug.
  Bug occur when renaming folder in korean after creating folder!
  May be unicode bug...

  https://youtu.be/G_FcGdn20eE

  My computer using ubuntu 17.04
  i5-6200u
  ram 4gb

  cybertr...@nate.com
  17.10.08

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

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

[Desktop-packages] [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

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

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

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

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

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

[Desktop-packages] [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

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

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

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

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

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

[Desktop-packages] [Bug 1819298] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  I tried to apply this driver and it provoked the bug

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Sun Mar 10 01:46:53 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu2_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1
  InstallationDate: Installed on 2018-07-12 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1
  UpgradeStatus: Upgraded to cosmic on 2019-03-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1819298/+subscriptions

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

[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic

2019-03-26 Thread Valentin Crone

Same problem, was not reliable on 14.04 but work with a bad integration.
Integration is better on 18.04 but very very slow, and crash when opening 
folder with many files (like music or dcim folder).
Unusable actually...

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

Title:
  MTP not working/very slow on Bionic

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

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821705] Re: nvidia-340 340.107-0ubuntu0~gpu16.04.1: nvidia-340 kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1573508, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- nvidia-340 340.107-0ubuntu0~gpu16.04.1: nvidia-340 kernel module failed to 
build
+ nvidia-340 340.107-0ubuntu0~gpu16.04.1: nvidia-340 kernel module failed to 
build [error: too many arguments to function ‘get_user_pages’]

** This bug has been marked a duplicate of bug 1573508
   SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too 
many arguments to function ‘get_user_pages’]

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

Title:
  nvidia-340 340.107-0ubuntu0~gpu16.04.1: nvidia-340 kernel module
  failed to build [error: too many arguments to function
  ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  happened after apt upgrade
  I'm on 32bit system, VAIO laptop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.107-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  340.107  Thu May 24 21:04:34 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.4.0-143-generic
  Date: Tue Mar 19 11:36:24 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-45-generic, i686: installed
   bbswitch, 0.8, 4.15.0-46-generic, i686: installed
   bbswitch, 0.8, 4.4.0-143-generic, i686: installed
   nvidia-340, 340.107, 4.15.0-46-generic, i686: installed
  DuplicateSignature: 
dkms:nvidia-340:340.107-0ubuntu0~gpu16.04.1:/var/lib/dkms/nvidia-340/340.107/build/nv-linux.h:2100:9:
 error: too many arguments to function ‘get_user_pages’
  GraphicsCard:
   NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation G86M [GeForce 8400M GS] [104d:9008]
  InstallationDate: Installed on 2018-02-14 (404 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: Sony Corporation VGN-SZ58GN
  PackageVersion: 340.107-0ubuntu0~gpu16.04.1
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=9251f137-f786-46dc-83e5-11dce9990285 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.107-0ubuntu0~gpu16.04.1: nvidia-340 kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/04/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0122S5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0122S5:bd04/04/2008:svnSonyCorporation:pnVGN-SZ58GN:pvrJ002S4R7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-SZ58GN
  dmi.product.version: J002S4R7
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

[Desktop-packages] [Bug 1821763] Re: Xorg freeze

Thanks for the bug report. Next time the problem happens, please:

1. Reboot.

2. Run:  journalctl -b-1 > prevboot.txt

3. Send us the file 'prevboot.txt'.

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

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

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  System froze completely, no mouse and keyboard, caps and num lock keys
  didn't even light up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 12:20:53 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:39c5]
  InstallationDate: Installed on 2019-03-06 (19 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:5a02 IMC Networks 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN41WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN41WW:bd07/23/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80YH
  dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ideapad 320-15IKB
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco) [needed for graphics support on Intel Core 2 Duo systems]

** Summary changed:

- intel video driver not installed by default in ubuntu 19.04 (Disco)
+ intel video driver not installed by default in ubuntu 19.04 (Disco) [needed 
for graphics support on Intel Core 2 Duo systems]

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

Title:
  intel video driver not installed by default in ubuntu 19.04 (Disco)
  [needed for graphics support on Intel Core 2 Duo systems]

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed 
GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then 
updated grub. Restarted the computer and on booting the ISO no login screen 
appeared. However,after pressing alt + ctrl + F2, logging in at command 
prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and 
unity" I was able to get to the desktop by running the command 'sudo service 
lightdm start'.  Command 'startx and X" gave xorg error saying server could not 
be connected. Command "sudo service gdm(3) start' went back to command prompt 
($).  
   This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing 
intel video driver and running startx command i was able to get to the desktop.
  Whether, "xserver-xorg-video-intel" package is not being installed by default 
in ubuntu or support for "intel core2duo processor" has been withdrawn.

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8

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

Oh. On second thoughts I think you might have made a mistake.

I think more likely the fix came from the reintroduction of the Intel
Xorg driver:

  Install: libxcb-randr0:amd64 (1.13.1-2, automatic), xserver-xorg-
video-intel:amd64 (2:2.99.917+git20180925-2, automatic)

which is needed by older GPUs, possibly like:

  Intel(R) Core(TM)2 Duo CPU T5870  @ 2.00GHz

That would make this a duplicate of bug 1819943.

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

** Summary changed:

- lightdm login screen never appears when using kernel 5.0.0-7, but works with 
kernel 5.0.0-8
+ lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870

** Changed in: xorg (Ubuntu)
   Status: Fix Committed => New

** This bug has been marked a duplicate of bug 1819943
   intel video driver not installed by default in ubuntu 19.04 (Disco)

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

Title:
  lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Could you please try some older kernels (like 4.18) to see if the
problem is caused by the new kernel in Ubuntu 19.04?

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

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

** Package changed: ubuntu => linux (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/1821641

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my
  hardware. Thanks!

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

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

[Desktop-packages] [Bug 1821609] [NEW] lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8

You have been subscribed to a public bug:

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


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

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

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


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

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

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

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

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

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

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: Fix Committed


** Tags: amd64 apport-bug disco freeze has-workaround regression reproducible 
ubuntu
-- 
lightdm login screen never appears when using kernel 5.0.0-7, but works with 
kernel 5.0.0-8
https://bugs.launchpad.net/bugs/1821609
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

Thanks for figuring that out.

Kernel 5.0.0-8 is in disco-proposed right now, so we call that Fix
Committed (but not yet released).

** No longer affects: kwallet-pam (Ubuntu)

** Summary changed:

- Xorg freeze - fails to start or stay going screen blanks-grub  seems involved
+ lightdm login screen never appears when using kernel 5.0.0.7, but works with 
kernel 5.0.0.8

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

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

** Summary changed:

- lightdm login screen never appears when using kernel 5.0.0.7, but works with 
kernel 5.0.0.8
+ lightdm login screen never appears when using kernel 5.0.0-7, but works with 
kernel 5.0.0-8

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

Title:
  lightdm login screen never appears when using kernel 5.0.0-7, but
  works with kernel 5.0.0-8

Status in linux package in Ubuntu:
  Fix Committed

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "ERROR Atomic update failure on pipe A"

In theory logging into "Ubuntu on Wayland" should avoid the problem.

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

Title:
  Frequent system freezing with i915 error "*ERROR* Atomic update
  failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.

2019-03-26 Thread and003

I started receiving this warning when I installed HPLIP on my computer,
and it appears to be preventing me from sending faxes. I also think it
caused me to receive the 'hp-uiscan is not supported for this device'.

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

Title:
  WARNING: Couldn't register with accessibility bus: Did not receive a
  reply.

Status in at-spi2-core package in Ubuntu:
  Fix Released
Status in at-spi2-core package in Debian:
  Fix Released

Bug description:
  The following warnings/errors appear after calling ubuntu-bug

  ** (apport-gtk:3020): WARNING **: 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.

  (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport-gtk 2.12.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 10:54:01 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (371 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+subscriptions

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

[Desktop-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)

** No longer affects: 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/1819943

Title:
  intel video driver not installed by default in ubuntu 19.04 (Disco)

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed 
GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then 
updated grub. Restarted the computer and on booting the ISO no login screen 
appeared. However,after pressing alt + ctrl + F2, logging in at command 
prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and 
unity" I was able to get to the desktop by running the command 'sudo service 
lightdm start'.  Command 'startx and X" gave xorg error saying server could not 
be connected. Command "sudo service gdm(3) start' went back to command prompt 
($).  
   This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing 
intel video driver and running startx command i was able to get to the desktop.
  Whether, "xserver-xorg-video-intel" package is not being installed by default 
in ubuntu or support for "intel core2duo processor" has been withdrawn.

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

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

[Desktop-packages] [Bug 1818766] Re: Update to 1.47

2019-03-26 Thread Robert Ancell

Currently blocked on new -tests packages being accepted.

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

Title:
  Update to 1.47

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Any new release has a risk of introducing bugs, this is mitigated by 
automatic regression tests.

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

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-03-26 Thread fossfreedom

Sure. In and around beta testing can compile/revert commits etc.

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

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

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1749590] Re: [snap] All open windows are grouped under one single icon in the dock

2019-03-26 Thread franciscoIR

I just want to add, in kubuntu plasma the problem does not exist. Each
libreoffice application (writer, impress, calc, draw) is associated with
its icon in the panel.

lsb_release -d
Description:Ubuntu 18.10

snap --version
snap2.37.4+18.10.1
snapd   2.37.4+18.10.1
series  16
ubuntu  18.10
kernel  4.18.0-16-generic

name:libreoffice
summary: LibreOffice is a powerful office suite including word processing and 
creation of spreadsheets,
  slideshows and databases
publisher: Canonical✓
contact:   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?field.tag=snap
license:   unset
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.filebug
  - libreoffice.impress
  - libreoffice
  - libreoffice.math
  - libreoffice.writer
snap-id:  CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
tracking: stable
refresh-date: 12 days ago, at 16:13 -03
channels:
  stable:6.2.1.2 2019-03-10 (106) 507MB -
  candidate: 6.2.2.2 2019-03-25 (110) 506MB -
  beta:  6.2.0.3 2019-01-31 (103) 505MB -
  edge:  ↑  
installed:   6.2.1.2(106) 507MB -


** Attachment added: "Screenshot_20190326_212843.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1749590/+attachment/5249588/+files/Screenshot_20190326_212843.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/1749590

Title:
  [snap] All open windows are grouped under one single icon in the dock

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  when i open libreoffice snap app, all applications (draw, impress, etc) open 
with the writer icon on the dock
  I have attached a image, i have open draw and impress but in the dock is only 
the writer icon.

  Ubuntu 17.10

  Extension's installed
  hide-activities
  pixel-saver
  places

  snap version
  snap2.30
  snapd   2.30
  series  16
  ubuntu  17.10
  kernel  4.13.0-32-generic

  snap info libreoffice
  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).
  snap-id: CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:candidate
  installed:   6.0.1.1 (49) 416MB -
  refreshed:   2018-02-13 18:40:21 -0300 -03
  channels: 
stable:5.4.4.2 (46) 415MB -
candidate: 6.0.1.1 (49) 416MB -
beta:  ↑  
edge:  ↑

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

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-03-26 Thread Treviño

@fossfreedom,

Mh, not sure we wanted to revert this on mutter tbh, but I see the
problem.

GNOME Shell had to apply something related to allow this change with
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/102 although
this seems to be something different.

Do you have any time to experiment something?

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

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

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-03-26 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821820

** Tags added: iso-testing

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

Title:
  Cannot boot or install - have to use nomodeset

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+subscriptions

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

[Desktop-packages] [Bug 1080120] Re: Ubuntu One Music webapp description is misleading

2019-03-26 Thread Adolfo Jayme

** Changed in: hundredpapercuts
   Status: New => Won't Fix

** Changed in: app-install-data-ubuntu (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

Title:
  Ubuntu One Music webapp description is misleading

Status in One Hundred Papercuts:
  Won't Fix
Status in app-install-data-ubuntu package in Ubuntu:
  Won't Fix
Status in webapps-applications package in Ubuntu:
  Won't Fix

Bug description:
  Similar to the Amazon webapp case, the script seems to be the official
  webapp integration for UbuntuOne Music Store, but the description says
  that it is a collection of example scripts.

  Proposal (english is not my first language, please recheck):

  "Your music, one click away. The Ubuntu One Music webapp not only
  helps you to quickly launch and access your music, but also nicely
  integrates into your desktop, adding features like notifications and
  badges."

  On all webapps could be nice to add a simple description. Below is a
  nice extract from an "I Love Ubuntu" article:

  "Ubuntu Web Apps are a new web-based technology, mainly combining the
  power and versatility of the web with the warmth and handiness of the
  Ubuntu desktop."

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

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

[Desktop-packages] [Bug 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04

2019-03-26 Thread Bharat

I am facing a similar issue in my HP Ubuntu 16.04 laptop... WiFi icon is
grayed out, it doesn't show the active connection (though it is actually
connected to my WiFi router!) and it shows other Wi-Fi networks.
Sometimes, the whole icon disappears and I get the small icon of network
(with the up-down arrows)!

As reported by others, I suspect that it is caused due to laptop going
to standby.

The "service network-manager restart" command worked for me!

Wish this bug could be fixed though!

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

Title:
  WiFi indicator icon disappears in Ubuntu 16.04

Status in indicator-applet package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  Can someone confirm an occasionally missing WiFi indicator tray icon?

  Sometimes it happens that the icon is not displayed although the WiFi
  connection is working.

  Please see also the attached screenshot.

  Warmly,

  ~Robert

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

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

[Desktop-packages] [Bug 1821820] [NEW] Cannot boot or install - have to use nomodeset

2019-03-26 Thread fossfreedom

Public bug reported:

On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
Budgie.

This is different behaviour from 18.04 and 18.10 where it booted and
installed just fine without nomodeset.

Without nomodeset, grub/efi disappears, and after a while a solid rather
than blinking cursor on a black screen is seen.  It does not boot into a
live session, nor displays the ubiquity window

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Tue Mar 26 23:40:49 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
InstallationDate: Installed on 2019-03-26 (0 days ago)
InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 02/15/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.1F
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80BF
dmi.board.vendor: HP
dmi.board.version: 95.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: N9S73EA#ABU
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  Cannot boot or install - have to use nomodeset

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp.

[Desktop-packages] [Bug 1056001] Re: u1 music store webapp not correctly matched to icon in the launcher

2019-03-26 Thread Adolfo Jayme

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

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

Title:
  u1 music store webapp not correctly matched to icon in the launcher

Status in webapps-applications package in Ubuntu:
  Won't Fix

Bug description:
  With today’s batch of updates for quantal, two new icons appeared in my 
launcher (ubuntu one music store, and amazon).
  When I clicked on the ubuntu one music store icon, 
https://one.ubuntu.com/music-store/ opened up in a new tab in my browser, but 
instead of associating it to the existing icon in the launcher (the one I 
clicked), a new tile appeared, fully grey, and when hovered with the mouse the 
tooltip says "UbuntuOneMusicStore".

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-webapps-common 2.4.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  CheckboxSubmission: 2c7995ffdf051a6d0adf7ab2c7be5ba9
  CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
  Date: Tue Sep 25 09:30:53 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  PackageArchitecture: all
  SourcePackage: webapps-applications
  UpgradeStatus: Upgraded to quantal on 2012-08-30 (25 days ago)

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

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

[Desktop-packages] [Bug 1079932] Re: Make it possible to remove Amazon webapp without removing all webapps

2019-03-26 Thread Adolfo Jayme

This bug is obsolete. The Amazon adware now lives in a separate package
called ubuntu-web-launchers, which is easily uninstallable at last. And
since Ubuntu Phone is no longer a thing, webapps-applications has been
abandoned.

** Changed in: webapps-applications
   Status: Confirmed => Invalid

** Changed in: webapps-applications (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Make it possible to remove Amazon webapp without removing all webapps

Status in WebApps: Applications Data:
  Invalid
Status in webapps-applications package in Ubuntu:
  Invalid

Bug description:
  I removed the Amazon package as soon as I installed the new Ubuntu
  version (with webapps). With a recent update it came back. But here is
  my main problem: I cannot remove the amazon integration without
  removing all web apps.

  It's great that Amazon is supported, it's ok that it comes
  preinstalled, but it is not ok if amazon is fused with the core
  system. I think this is serious enough to be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-applications/+bug/1079932/+subscriptions

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-03-26 Thread uecm

@VanVan

Just updated to kernel 5.0 and the sound on my model ( Asus Q325UAR / dual boot 
) does NOT work. 
How/where can I submit a report so that the model is included in the list for 
the fix?

As far as I am aware the Q325UAR hardware is exactly the same as UX391UA
but the model was targeted at a different retailer.

Thanks!

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1821814] [NEW] Todoist extension missing in Ubuntu 19.04

2019-03-26 Thread Thea Barnes

Public bug reported:

The gnome-todo package previously supported Todoist as a source, however
on upgrading to 19.04 beta, the Todoist online account option is
missing, and the extension for gnome-todo appears to be missing as well.

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

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

Title:
  Todoist extension missing in Ubuntu 19.04

Status in gnome-todo package in Ubuntu:
  New

Bug description:
  The gnome-todo package previously supported Todoist as a source,
  however on upgrading to 19.04 beta, the Todoist online account option
  is missing, and the extension for gnome-todo appears to be missing as
  well.

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

2019-03-26 Thread Derk Willem te Bokkel

okay did the same thing to my sda7  partition install the 5.0.0.8 kernel works 
lightdm is stable etc.
but boot with the 5.0.0.7 kernel fails as per before .. so choice of kernel or 
it's corresponding initrd is the problem ..here a kernal upgrade fixes the 
issues

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

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

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

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

2019-03-26 Thread Gunnar Hjalmarsson

I can confirm that the problem with LO crashes seems to be gone (also on
bionic).

However, I have a problem with making OSK show up (not using a touch
screen). In LibreOffice Writer it shows up after a mouse click in the
text entry area, but I fail to enable OSK in gedit, gnome-terminal and
Firefox.

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

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

Status in im-config package in Ubuntu:
  Confirmed

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

  Expected result:
  The OSK appears

  Actual results:
  The OSK does not appear.

  ---

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

  

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

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

2019-03-26 Thread Derk Willem te Bokkel

okay did something unusual .. i copyed my apt sources and trust files from the 
working version sda1
to the copy on sda6 the added a series of new proposed updates including a new 
kernel version
on reboot the updated sda6 worked as expected:

this was the upgrade package list: including a few earlier xorg/video
driver upgrades from previous update for reference too!


Install: libxcb-randr0:amd64 (1.13.1-2, automatic), 
xserver-xorg-video-intel:amd64 (2:2.99.917+git20180925-2, automatic), 
libxvmc1:amd64 (2:1.0.10-1, automatic), mesa-vulkan-drivers:amd64 
(19.0.0-1ubuntu1, automatic)
Upgrade: xserver-xorg-input-all:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), 
xserver-xorg:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), 
xserver-xorg-video-all:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), xorg:amd64 
(1:7.7+19ubuntu11, 1:7.7+19ubuntu12), x11-common:amd64 (1:7.7+19ubuntu11, 
1:7.7+19ubuntu12)
End-Date: 2019-03-26  16:17:46

updated sources.list sources.d etc.


Start-Date: 2019-03-26  17:16:25
Commandline: apt upgrade
Requested-By: derk (1000)
Install: libpath-tiny-perl:amd64 (0.108-1, automatic), 
linux-headers-5.0.0-8:amd64 (5.0.0-8.9, automatic), 
linux-headers-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), libxpresent1:amd64 
(1.0.0-2, automatic), linux-image-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), 
linux-modules-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), 
libunicode-utf8-perl:amd64 (0.62-1, automatic), 
linux-modules-extra-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), 
libcapture-tiny-perl:amd64 (0.48-1, automatic)
Upgrade: libpython3.7-minimal:amd64 (3.7.2-3, 3.7.3-1), perl-base:amd64 
(5.28.1-4, 5.28.1-5), fuse:amd64 (2.9.8-1ubuntu1, 2.9.9-1ubuntu1), 
linux-headers-generic:amd64 (5.0.0.7.8, 5.0.0.8.9), linux-libc-dev:amd64 
(5.0.0-7.8, 5.0.0-8.9), libcairo-gobject2:amd64 (1.16.0-3, 1.16.0-4), 
linux-image-generic:amd64 (5.0.0.7.8, 5.0.0.8.9), rtkit:amd64 (0.11-6, 0.12-4), 
libsqlite3-0:amd64 (3.27.2-1, 3.27.2-2), python3-gi-cairo:amd64 (3.30.4-1, 
3.32.0-1), perl-modules-5.28:amd64 (5.28.1-4, 5.28.1-5), libpython3.7:amd64 
(3.7.2-3, 3.7.3-1), python3.7:amd64 (3.7.2-3, 3.7.3-1), gdb:amd64 
(8.2.90-0ubuntu1, 8.2.90.20190311-0ubuntu1), python3:amd64 (3.7.2-1, 3.7.3-1), 
libnm0:amd64 (1.15.2-0ubuntu2, 1.16.0-0ubuntu1), network-manager:amd64 
(1.15.2-0ubuntu2, 1.16.0-0ubuntu1), xfwm4:amd64 (4.12.5-1ubuntu1, 
4.13.1-3~19.04), libpython3.7-stdlib:amd64 (3.7.2-3, 3.7.3-1), 
libapparmor1:amd64 (2.12-4ubuntu10, 2.13.2-9ubuntu2), python3.7-minimal:amd64 
(3.7.2-3, 3.7.3-1), libperl5.28:amd64 (5.28.1-4, 5.28.1-5), 
python3-minimal:amd64 (3.7.2-1, 3.7.3-1), libpython3-stdlib:amd64 (3.7.2-1, 
3.7.3-1), libfuse2:amd64 (2.9.8-1ubuntu1, 2.9.9-1ubuntu1), lintian:amd64 
(2.6.0, 2.11.0), libwebkit2gtk-4.0-37:amd64 (2.23.91-1, 2.24.0-1), 
python3-gi:amd64 (3.30.4-1, 3.32.0-1), gir1.2-webkit2-4.0:amd64 (2.23.91-1, 
2.24.0-1), perl:amd64 (5.28.1-4, 5.28.1-5), rsync:amd64 (3.1.3-5, 3.1.3-6), 
apparmor:amd64 (2.12-4ubuntu10, 2.13.2-9ubuntu2), gdbserver:amd64 
(8.2.90-0ubuntu1, 8.2.90.20190311-0ubuntu1), libcairo2:amd64 (1.16.0-3, 
1.16.0-4), python3-gdbm:amd64 (3.7.2-3ubuntu1, 3.7.3-1ubuntu1), 
libjavascriptcoregtk-4.0-18:amd64 (2.23.91-1, 2.24.0-1), linux-generic:amd64 
(5.0.0.7.8, 5.0.0.8.9), gir1.2-javascriptcoregtk-4.0:amd64 (2.23.91-1, 2.24.0-1)
End-Date: 2019-03-26  17:18:12

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

2019-03-26 Thread Lucas Partridge

I don't think this is exactly the same as
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1762256 because when I try installing the tree of
dependencies I get slightly different errors...

$ sudo apt install colord
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
colord : Depends: libsane1 (>= 1.0.24) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

$ sudo apt install libsane1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
libsane1 : Depends: libsane-common (= 1.0.27-1~experimental3ubuntu2) but
1.0.27+git20180317-xenial0 is to be installed
Recommends: sane-utils (>= 1.0.27-1~experimental3ubuntu2)
E: Unable to correct problems, you have held broken packages.

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

Title:
gnome-control-center won't install: Depends: colord (>= 0.1.30)

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

Bug description:
This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1762256.

I noticed Settings has gone missing from my ubuntu 18.04. When I click
on the spanner icon under the power icon in the top right nothing
appears to happen. Attempting to install it fails with:

$ sudo apt install gnome-control-center
[sudo] password for lucas:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

This may have come about as a side-effect of trying to install simple-
scan. I raised a question about that at
https://askubuntu.com/q/1108407/103266 but it never got fixed. I
couldn't resolve the error "Unable to correct problems, you have held
broken packages". Any suggestions welcome, please.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 21:15:46 2019
InstallationDate: Installed on 2017-09-03 (569 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821809] [NEW] gnome-control-center won't install: Depends: colord (>= 0.1.30)

2019-03-26 Thread Lucas Partridge

Public bug reported:

This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1762256.

I noticed Settings has gone missing from my ubuntu 18.04. When I click
on the spanner icon under the power icon in the top right nothing
appears to happen. Attempting to install it fails with:

$ sudo apt install gnome-control-center
[sudo] password for lucas: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

This may have come about as a side-effect of trying to install simple-
scan. I raised a question about that at
https://askubuntu.com/q/1108407/103266 but it never got fixed. I
couldn't resolve the error "Unable to correct problems, you have held
broken packages". Any suggestions welcome, please.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 21:15:46 2019
InstallationDate: Installed on 2017-09-03 (569 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gnome-control-center won't install: Depends: colord (>= 0.1.30)

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

Bug description:
  This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/1762256.

  I noticed Settings has gone missing from my ubuntu 18.04. When I click
  on the spanner icon under the power icon in the top right nothing
  appears to happen. Attempting to install it fails with:

  $ sudo apt install gnome-control-center
  [sudo] password for lucas: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   gnome-control-center : Depends: colord (>= 0.1.30)
  E: Unable to correct problems, you have held broken packages.

  This may have come about as a side-effect of trying to install simple-
  scan. I raised a question about that at
  https://askubuntu.com/q/1108407/103266 but it never got fixed. I
  couldn't resolve the error "Unable to correct problems, you have held
  broken packages". Any suggestions welcome, please.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 21:15:46 2019
  InstallationDate: Installed on 2017-09-03 (569 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

2019-03-26 Thread Derk Willem te Bokkel

okay determined all my installs of xubuntu including the one that works
no matter what the others are doing ..

do not have kwallet installed ..

and the three /etc/pam.d lightdm? configs are all the same .. the
missing modules are just ignored .. I tried commenting them out but this
does not influence the screen behaviour

the versions of lightdm are the same on all the instances:
1.28.0-0ubuntu1

libpam-systemd is the same as well: 240-6ubuntu3

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

Title:
  Xorg freeze - fails to start or stay going screen blanks-grub  seems
  involved

Status in kwallet-pam package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1821768] Re: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed

2019-03-26 Thread Amr Ibrahim

Yes, the screenshots are similar.

** Package changed: ubuntu-themes (Ubuntu) => openjdk-lts (Ubuntu)

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

Title:
  Java-gtk3 theming has many artefacts after updating to openjdk-11 in
  bionic-proposed

Status in openjdk-lts package in Ubuntu:
  New

Bug description:
  Openjdk-11 is now in bionic-proposed, and apparently it has switched
  to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in
  Bionic. I can see a lot of theming artefacts in scilab (default look)
  and jabref (after switching to gtk look) from bionic-proposed.

  Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance
  on Bionic:

  A. For java-gtk2:
  1. Don't update to openjdk-11 in bionic-proposed
  2. Install jabref 3.8.2+ds-3
  3. Change the look in Preferences to Gtk
  4. Notice that the app is properly themed

  B. For java-gtk3:
  5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed
  6. Change the look in Preferences to Gtk
  5. Notice that the theming has many artefacts compared to the previous version

  The same steps can be followed to compare scilab before and after.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20181005-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 16:17:52 2019
  InstallationDate: Installed on 2018-11-29 (116 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/openjdk-lts/+bug/1821768/+subscriptions

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

[Desktop-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "ERROR Atomic update failure on pipe A"

2019-03-26 Thread Federico_dv

Same problem here, brand new install 18.10 in a new laptop, i cant pass
the login, freezes all and the logs  keeps raising

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

Title:
  Frequent system freezing with i915 error "*ERROR* Atomic update
  failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1738164] Missing SRU information

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  [snap] U2F doesn't work with yubikey

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

Bug description:
  (initially reported by Daniel at https://forum.snapcraft.io/t/call-
  for-testing-chromium-62-0-3202-62/2569/50)

« U2F (Universal 2nd Factor) isn’t working when signing into my
  gmail account trying to use my yubikey. This is a USB device which
  IIRC chromium needs bidirectional communication with. »

  This requires investigation, but the yubikey I have is too old and
  doesn't support U2F.

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

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-: nvidia- kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

2019-03-26 Thread Brendan Boerner

A buddy asked me to add that he's also unable to build - Trusty
(14.04.5).

...
ld -r -o 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset/nv-modeset-interface.o
 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset/nvidia-modeset-linux.o
  LD [M]  /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset.o
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:
 In function ‘nvidia_drm_lock_user_pages’:
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5:
 warning: passing argument 6 of ‘get_user_pages’ makes pointer from integer 
without a cast [enabled by default]
 pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force,
 ^
In file included from include/linux/scatterlist.h:7:0,
 from include/linux/dma-mapping.h:10,
 from include/drm/drmP.h:37,
 from 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32,
 from 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27:
include/linux/mm.h:1222:6: note: expected ‘struct page **’ but argument is of 
type ‘int’
 long get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
  ^
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5:
 warning: passing argument 7 of ‘get_user_pages’ from incompatible pointer type 
[enabled by default]
 pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force,
 ^
In file included from include/linux/scatterlist.h:7:0,
 from include/linux/dma-mapping.h:10,
 from include/drm/drmP.h:37,
 from 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32,
 from 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27:
include/linux/mm.h:1222:6: note: expected ‘struct vm_area_struct **’ but 
argument is of type ‘struct page **’
 long get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
  ^
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5:
 error: too many arguments to function ‘get_user_pages’
 pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force,
 ^
In file included from include/linux/scatterlist.h:7:0,
 from include/linux/dma-mapping.h:10,
 from include/drm/drmP.h:37,
 from 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32,
 from 
/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27:
include/linux/mm.h:1222:6: note: declared here
 long get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
  ^
make[2]: *** 
[/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.o]
 Error 1
make[2]: Target `__build' not remade because of errors.
make[1]: *** [_module_/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel] Error 2
make[1]: Target `modules' not remade because of errors.
make[1]: Leaving directory `/usr/src/linux-headers-4.4.0-143-generic'
make: *** [modules] Error 2
ERROR: The nvidia kernel module was not created.
ERROR: Installation has failed.  Please see the file 
'/var/log/nvidia-installer.log' for details.  You may find suggestions on 
fixing installation problems in the README available on the Linux driver 
download page at www.nvidia.com.


** Attachment added: "nvidia-installer log file for -143 kernel"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+attachment/5249523/+files/nvidia-installer.log

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3)

[Desktop-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)

This bug was fixed in the package xorg - 1:7.7+19ubuntu12

---
xorg (1:7.7+19ubuntu12) disco; urgency=medium

  * control: Restore -intel to x-x-video-all Recommends, glamor needs
OpenGL 2.1 which i915_dri.so doesn't support. (LP: #1819943)
  * control: Add mesa-vulkan-drivers back to xserver-xorg recommends.

 -- Timo Aaltonen   Tue, 26 Mar 2019 17:46:22 +0200

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

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

Title:
  intel video driver not installed by default in ubuntu 19.04 (Disco)

Status in xorg package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed 
GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then 
updated grub. Restarted the computer and on booting the ISO no login screen 
appeared. However,after pressing alt + ctrl + F2, logging in at command 
prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and 
unity" I was able to get to the desktop by running the command 'sudo service 
lightdm start'.  Command 'startx and X" gave xorg error saying server could not 
be connected. Command "sudo service gdm(3) start' went back to command prompt 
($).  
   This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing 
intel video driver and running startx command i was able to get to the desktop.
  Whether, "xserver-xorg-video-intel" package is not being installed by default 
in ubuntu or support for "intel core2duo processor" has been withdrawn.

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

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

[Desktop-packages] [Bug 1819193] Re: Document search does not work

2019-03-26 Thread Mordi

Related to this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-
documents/+bug/1592705

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

Title:
  Document search does not work

Status in gnome-documents package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Description: Ubuntu 18.04.2 LTS
  2. 3.28.3-0ubuntu0.18.04.4
  3. I expect to be able to search document by content from the gnome shell 
("Type to search..."). The option is enabled from settings.
  4. Nothing happens. No documents are retrieved. 

  I get the following error message in logs repeatedly:

  "Wrong number of result metas returned by search provider
  org.gnome.Documents.desktop: expected 5 but got 0"

  gnome-documents also gives this:
  "JS ERROR: GLib.Error g-invoke-error-quark: Could not locate 
gd_filename_strip_extension: (null)"

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

-- 
Mailing list: https://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 1804280] Re: intermittent periods of packet loss and high latency

2019-03-26 Thread Dan Candeto

This could be the same issue as those other two.  Similar hardware is 
involved.  I haven't had time to test changing those settings on the NIC.

On 2019-03-21 6:41 a.m., Kai-Heng Feng wrote:
> Is this same as LP: #1785171 and #1802691?
>

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

Title:
  intermittent periods of packet loss and high latency

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

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2053 F pulseaudio
   /dev/snd/pcmC1D0c:   dan2053 F...m pulseaudio
   /dev/snd/controlC1:  dan2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (712 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 
100
  MachineType: Dell Inc. Precision Tower 3420
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:

[Desktop-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

2019-03-26 Thread Rondo5000

I have been experiencing identical issues since around mid-January or so
(though my latency sometimes reaches 3000/4000+ ms during these times).
I am running a freshly installed and fully updated version of Ubuntu
18.04 Desktop.  For the first couple of months after installing 18.04 I
had none of these issues whatsoever, they seemed to materialize during a
period when I was doing a lot of heavy software development which used a
great deal of system resources (multiple VMs). Originally the
workstation was wired directly to my router, but even after purchasing a
wireless USB adapter I am still experiencing the issue.

I typically use remote viewing software to work on the affected
workstation (from another laptop in my home), and once I begin to notice
moderate sluggishness in the response time of the system I can typically
run "sudo systemctl restart network-manager" and I will usually not
begin to experience the issue again until several hours later,
typically.  If I go too long without running that command the full 10-15
minute period of extreme latency will set in.  It doesn't return fully
to "normal" response times after that high period, but it is far lower
than the most extreme patches.

I hesitate to say that the issue is similar to other bug reports because
of the "dropping of the connection" aspects of those.  The connection
never fully dies in this case, but just experiences periods of latency
related unusability.

Any logs or further info available upon request.

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

Title:
  intermittent periods of packet loss and high latency

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

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USER

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread Till Kamppeter

Thanks, nice collection of crashes, but no NetworkManager.

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread El jinete sin cabeza

** Attachment added: "$ ll /var/crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810316/+attachment/5249520/+files/ll_var-crash.txt

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

Hello Matthias, or anyone else affected,

Accepted libunistring into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libunistring/0.9.9-0ubuntu2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libunistring (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  Incomplete
Status in libunistring source package in Bionic:
  Fix Committed
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 18.10.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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

[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

The regression potential here in the description is incorrect "We are
simply backporting the workaround we applied in Ubuntu 18.10." The fix
in Ubuntu 18.10 for both packages was to add "--no-as-needed" to the
build options which you now indicate is a worse solution. Please also
upload the better fix to the cosmic SRU queue.

** Changed in: libidn (Ubuntu Bionic)
   Status: In Progress => Incomplete

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  Incomplete
Status in libunistring source package in Bionic:
  Fix Committed
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 18.10.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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

[Desktop-packages] [Bug 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2

Sorry, I wouldn't consider it verified unless I stepped through the test
case in the description.  I'll be sure to specifically list those
details.

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

Title:
  SRU xdg-desktop-portal-gtk 1.0.2

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal-gtk source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal-gtk upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in 
xdg-desktop-portal-gtk 1.0.  We're SRU'ing 1.0.2 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and 
xenial, so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
   
   Also requires xdg-desktop-portal 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal also from proposed.  Verify the file
  selection lets you select a file and open local opens test.txt in a
  text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however the version in bionic had limited 
functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic 
and disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+subscriptions

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

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread Till Kamppeter

To anyone who has observed this problem:

Please check the contents of your /var/crash/ directory.

Is there a file with the ".crash" extension and NetworkManager or
networkmanager in its name and the day when you observed the problem as
file date?

In this case also NetworkManager has crashed.

Then please call "apport-bug" with this file as command line argument:

apport-bug /var/crash/...

This will generate a new bug report with more info about your crash of
NetworkManager. Add a link to this bug report here.

Or tell here for the case that you do not get a crash file related to
NetworkManager.


** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3

I've stepped through the test case listed in the description on both
xenial and bionic with the following package versions:

xenial:
  xdg-desktop-portal-gtk=1.0.2-0ubuntu0.0
  xdg-desktop-portal=1.0.3-0ubuntu0.0
bionic:
  xdg-desktop-portal-gtk=1.0.2-0ubuntu1.1
  xdg-desktop-portal=1.0.3-0ubuntu0.2

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

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

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

[Desktop-packages] [Bug 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2

I've stepped through the test case listed in the description on both
xenial and bionic with the following package versions:

xenial:
  xdg-desktop-portal-gtk=1.0.2-0ubuntu0.0
  xdg-desktop-portal=1.0.3-0ubuntu0.0
bionic:
  xdg-desktop-portal-gtk=1.0.2-0ubuntu1.1
  xdg-desktop-portal=1.0.3-0ubuntu0.2

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

** Changed in: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

Title:
  SRU xdg-desktop-portal-gtk 1.0.2

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal-gtk source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal-gtk upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in 
xdg-desktop-portal-gtk 1.0.  We're SRU'ing 1.0.2 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and 
xenial, so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
   
   Also requires xdg-desktop-portal 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal also from proposed.  Verify the file
  selection lets you select a file and open local opens test.txt in a
  text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however the version in bionic had limited 
functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic 
and disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+subscriptions

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

[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3

I've verified this on both xenial and bionic and confirmed the
autopackage tests are passing now.

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

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

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

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

[Desktop-packages] [Bug 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2

Ken - rather than just flipping the tags from v-needed to v-done could
you please provide some verification details? I'm hoping for something
along the lines of I followed the test case in the description with
these package versions and these were the results.

** Changed in: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Status: Fix Committed => Incomplete

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

Title:
  SRU xdg-desktop-portal-gtk 1.0.2

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  Fix Committed
Status in xdg-desktop-portal-gtk source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal-gtk upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in 
xdg-desktop-portal-gtk 1.0.  We're SRU'ing 1.0.2 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and 
xenial, so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
   
   Also requires xdg-desktop-portal 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal also from proposed.  Verify the file
  selection lets you select a file and open local opens test.txt in a
  text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however the version in bionic had limited 
functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic 
and disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+subscriptions

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

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread Bug Watch Updater

** Changed in: network-manager
   Status: Unknown => New

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time

2019-03-26 Thread Maciej Jesionowski

Hi. It's probably me, but I can't find this proposed package. apt list
--upgradeable lists only libxkbcommon0/bionic-proposed, but I can't
install even that with apt install libxkbcommon0/bionic-proposed. It
says the release 'bionic-proposed' doesn't exist for this package. The
package libxkbcommon-dev is not visible at all.

Anyway, the problem isn't as severe for me now as it seems libgl1-mesa-
dev no longer depends on libxkbcommon-dev (in 18.04 at least) which was
what I really wanted to get installed.

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

Title:
  Unable to install i386 and amd64 arch at the same time

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

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

  $ sudo apt-get install libxkbcommon-dev:*
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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

[Desktop-packages] [Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions

2019-03-26 Thread Treviño

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Triaged

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [FFe] Distro patch GNOME hi-dpi support for x11 sessions

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The first part of our work on better handling of HI-DPI screens got merged 
upstream in 3.32, but it's for wayland only
  
https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/

  Since our default session in Ubuntu is based on xorg we would like to
  distro patch the x11 equivalent for Disco so our users can benefit
  from the feature.

  Updates packages are up for testing in that ppa
  https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling

  The main change is
  
https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz

  The ppa also includes a bugfix and a settings change to allow easy
  configuration.

  Note that the feature is behind an experimental gsettings key and the code 
has no impact on the rendering for users who don't enable it, which means it 
shouldn't be too risk. It's available as a opt-in for those who want to test it.
  From our testing it works fine and we feel like it's ready to be included. We 
do plan to get that work merged upstream in the next cycle so it should not be 
an Ubuntu delta to carry over forever.

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

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

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-03-26 Thread Amr Ibrahim

Bug #1821768 Java-gtk3 theming has many artefacts after updating to
openjdk-11 in bionic-proposed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in geogebra package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in libjogl2-java package in Ubuntu:
  New
Status in libpdfbox-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mongo-java-driver package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openhft-chronicle-threads package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox-hwe package in Ubuntu:
  New
Status in activemq source package in Bionic:
  Fix Committed
Status in afterburner.fx source package in Bionic:
  Fix Committed
Status in annotation-indexer source package in Bionic:
  Fix Committed
Status in apache-directory-server source package in Bionic:
  Fix Committed
Status in aspectj source package in Bionic:
  Fix Committed
Status in aspectj-maven-plugin source package in Bionic:
  Fix Committed
Status in batik source package in Bionic:
  Fix Committed
Status in bindex source package in Bionic:
  Fix Committed
Status in bridge-method-injector source package in Bionic:
  Fix Committed
Status in carrotsearch-hppc source package in Bionic:
  Fix Committed
Status in clojure source package in Bionic:
  Fix Committed
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in commons-httpclient source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in ecj source package in Bionic:
  Fix Committed
Status in eclipselink source package in Bionic:
  Fix Committed
Status in elki source package in Bionic:
  Fix Committed
Status in figtree source package in Bionic:
  Fix Committed
Status in fontawesomefx source package in Bionic:
  Fix Committed
Status in geogebra source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gluegen2 source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in hikaricp source package in Bionic:
  Fix Committed
Status in hsqldb source package in Bionic:
  Fix Committed
Status in hsqldb1.8.0 source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in jabref source package in Bionic:
  Fix Committed
Status in jackson-core source package in Bionic:
  Fix Committed
Status in jackson-databind source package in Bionic:
  Fix Committed
Status in jackson-dataformat-xml source package in Bionic:
  Fix Committed
Status in jackson-module-jaxb-annotations source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javafxsvg source package in Bionic:
  Fix Committed
Status in javamail source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jboss-classfilewriter source package in Bionic:
  Fix Committed
Status in jboss-jdeparser2 source package in Bionic:
  Fix Committed
Status in jboss-modules source package in Bionic:
  Fix Committed
Status in jcommander source package in Bionic:
  Fix Committed
Status in jersey1 source package in Bionic:
  Fix Committed
Status in jftp source package in Bionic:
  Fix Committed
Status in jhove source package in Bionic:
  Fix Committed
Status in jmdns source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jruby-openssl source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jts source package in Bionic:
  Fix Committed
Status in junit4 source package in Bionic:
  Fix Committed
Status in jxgrabkey source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libapache-poi-java source package in Bionic:
  Fix Committed
Status in libbtm-java source package in Bionic:
  Fix

[Desktop-packages] [Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions

2019-03-26 Thread Treviño

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

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

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

Title:
  [FFe] Distro patch GNOME hi-dpi support for x11 sessions

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The first part of our work on better handling of HI-DPI screens got merged 
upstream in 3.32, but it's for wayland only
  
https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/

  Since our default session in Ubuntu is based on xorg we would like to
  distro patch the x11 equivalent for Disco so our users can benefit
  from the feature.

  Updates packages are up for testing in that ppa
  https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling

  The main change is
  
https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz

  The ppa also includes a bugfix and a settings change to allow easy
  configuration.

  Note that the feature is behind an experimental gsettings key and the code 
has no impact on the rendering for users who don't enable it, which means it 
shouldn't be too risk. It's available as a opt-in for those who want to test it.
  From our testing it works fine and we feel like it's ready to be included. We 
do plan to get that work merged upstream in the next cycle so it should not be 
an Ubuntu delta to carry over forever.

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

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

[Desktop-packages] [Bug 1821768] [NEW] Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed

2019-03-26 Thread Amr Ibrahim

Public bug reported:

Openjdk-11 is now in bionic-proposed, and apparently it has switched to
gtk3. The gtk3-java theming in Ambiance theme is very incomplete in
Bionic. I can see a lot of theming artefacts in scilab (default look)
and jabref (after switching to gtk look) from bionic-proposed.

Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance on
Bionic:

A. For java-gtk2:
1. Don't update to openjdk-11 in bionic-proposed
2. Install jabref 3.8.2+ds-3
3. Change the look in Preferences to Gtk
4. Notice that the app is properly themed

B. For java-gtk3:
5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed
6. Change the look in Preferences to Gtk
5. Notice that the theming has many artefacts compared to the previous version

The same steps can be followed to compare scilab before and after.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20181005-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 16:17:52 2019
InstallationDate: Installed on 2018-11-29 (116 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Java-gtk3 theming has many artefacts after updating to openjdk-11 in
  bionic-proposed

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Openjdk-11 is now in bionic-proposed, and apparently it has switched
  to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in
  Bionic. I can see a lot of theming artefacts in scilab (default look)
  and jabref (after switching to gtk look) from bionic-proposed.

  Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance
  on Bionic:

  A. For java-gtk2:
  1. Don't update to openjdk-11 in bionic-proposed
  2. Install jabref 3.8.2+ds-3
  3. Change the look in Preferences to Gtk
  4. Notice that the app is properly themed

  B. For java-gtk3:
  5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed
  6. Change the look in Preferences to Gtk
  5. Notice that the theming has many artefacts compared to the previous version

  The same steps can be followed to compare scilab before and after.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20181005-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 16:17:52 2019
  InstallationDate: Installed on 2018-11-29 (116 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/ubuntu-themes/+bug/1821768/+subscriptions

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

[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’]

2019-03-26 Thread Jeff

Seth thank you for the work you have done and are doing on this.  Andy
of post 13, thank you for the walk through on your web site.   I was
about to patch and install for my Geforce 7900 GS on Mint 19.1 using the
4.15.xxx kernel using Andy's guide, successfully.

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

Title:
  nvidia-graphics-drivers fail to build [error: implicit declaration of
  function ‘init_timer’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions

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

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread El jinete sin cabeza

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

** Description changed:

  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 
(moved of freedesktop to GNOME)
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
  
  ---
  
  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.
  
  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.
  
  [Potential Regression]
  I think it's not a potential regression.
  
  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1821765] Re: snap: Missing icon in indicator

** Attachment added: "Menu when clicked"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1821765/+attachment/5249502/+files/Screenshot%20from%202019-03-26%2010-52-38.png

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

Title:
  [snap] Missing icon in indicator

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium is adding an appindicator, which has a missing icon when
  running from the snap.  I've confirmed with the deb that it shows the
  chromium icon there.  I'm not sure what setting makes it display the
  appindicator, I've had it there for years so must be some setting I
  have that is being synced.

  The only extensions I have installer are:

* The Great Suspender
* Google Drive
* Google Calendar

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

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

[Desktop-packages] [Bug 1821765] Re: [snap] Missing icon in indicator

2019-03-26 Thread Olivier Tilloy

** Summary changed:

- snap: Missing icon in indicator
+ [snap] Missing icon in indicator

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

Title:
  [snap] Missing icon in indicator

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium is adding an appindicator, which has a missing icon when
  running from the snap.  I've confirmed with the deb that it shows the
  chromium icon there.  I'm not sure what setting makes it display the
  appindicator, I've had it there for years so must be some setting I
  have that is being synced.

  The only extensions I have installer are:

* The Great Suspender
* Google Drive
* Google Calendar

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

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

[Desktop-packages] [Bug 1821763] [NEW] Xorg freeze

2019-03-26 Thread Gus

Public bug reported:

System froze completely, no mouse and keyboard, caps and num lock keys
didn't even light up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 12:20:53 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:39c5]
InstallationDate: Installed on 2019-03-06 (19 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 13d3:5a02 IMC Networks 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80YH
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 4WCN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN41WW:bd07/23/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
dmi.product.family: ideapad 320-15IKB
dmi.product.name: 80YH
dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ideapad 320-15IKB
dmi.product.version: Lenovo ideapad 320-15IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze ubuntu wayland-session

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  System froze completely, no mouse and keyboard, caps and num lock keys
  didn't even light up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 12:20:53 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:39c5]
  InstallationDate: Installed on 2019-03-06 (19 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:5a02 IMC Networks 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN41WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO

[Desktop-packages] [Bug 1821765] [NEW] [snap] Missing icon in indicator

Public bug reported:

Chromium is adding an appindicator, which has a missing icon when
running from the snap.  I've confirmed with the deb that it shows the
chromium icon there.  I'm not sure what setting makes it display the
appindicator, I've had it there for years so must be some setting I have
that is being synced.

The only extensions I have installer are:

  * The Great Suspender
  * Google Drive
  * Google Calendar

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
 Status: New


** Tags: snap

** Attachment added: "Missing Icon"
   
https://bugs.launchpad.net/bugs/1821765/+attachment/5249501/+files/indicator.png

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

Title:
  [snap] Missing icon in indicator

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium is adding an appindicator, which has a missing icon when
  running from the snap.  I've confirmed with the deb that it shows the
  chromium icon there.  I'm not sure what setting makes it display the
  appindicator, I've had it there for years so must be some setting I
  have that is being synced.

  The only extensions I have installer are:

* The Great Suspender
* Google Drive
* Google Calendar

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

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

[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2019-03-26 Thread Eduard Bardají Puig

The solution by @robertjjoynt did *not* work for me.

Also, is there a way to revert changes produced by @robertjjoynt? Not
that it's any different now, but don't want to mess around with settings
if it doesn't fix the issue.

OS: Ubuntu 18.04
System: HP Elitebook 830 G5

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Desktop-packages] [Bug 1819193] Re: Document search does not work

2019-03-26 Thread Mordi

This is apparently an upstream bug: https://gitlab.gnome.org/GNOME
/gnome-documents/issues/12

It seems that this has been fixed in 3.30. If so, is there any chance
that the fix is backported to the 18.04?


** Bug watch added: gitlab.gnome.org/GNOME/gnome-documents/issues #12
   https://gitlab.gnome.org/GNOME/gnome-documents/issues/12

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

Title:
  Document search does not work

Status in gnome-documents package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Description: Ubuntu 18.04.2 LTS
  2. 3.28.3-0ubuntu0.18.04.4
  3. I expect to be able to search document by content from the gnome shell 
("Type to search..."). The option is enabled from settings.
  4. Nothing happens. No documents are retrieved. 

  I get the following error message in logs repeatedly:

  "Wrong number of result metas returned by search provider
  org.gnome.Documents.desktop: expected 5 but got 0"

  gnome-documents also gives this:
  "JS ERROR: GLib.Error g-invoke-error-quark: Could not locate 
gd_filename_strip_extension: (null)"

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

-- 
Mailing list: https://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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-03-26 Thread Matthias Klose

On 25.03.19 19:42, Amr Ibrahim wrote:
> Apparently Java 11 has switched to gtk3. The gtk3-java theming in
> Ambiance theme is very incomplete in Bionic. I can see a lot of theming
> artefacts in scilab (default look) and jabref (after switching to gtk
> look).
> 
> Could it be switched back to gtk2 in Bionic?

@Amr, please see the announcement mail (file new bug reports and subscribe
openjdk-11-transition)

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in geogebra package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in libjogl2-java package in Ubuntu:
  New
Status in libpdfbox-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mongo-java-driver package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openhft-chronicle-threads package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox-hwe package in Ubuntu:
  New
Status in activemq source package in Bionic:
  Fix Committed
Status in afterburner.fx source package in Bionic:
  Fix Committed
Status in annotation-indexer source package in Bionic:
  Fix Committed
Status in apache-directory-server source package in Bionic:
  Fix Committed
Status in aspectj source package in Bionic:
  Fix Committed
Status in aspectj-maven-plugin source package in Bionic:
  Fix Committed
Status in batik source package in Bionic:
  Fix Committed
Status in bindex source package in Bionic:
  Fix Committed
Status in bridge-method-injector source package in Bionic:
  Fix Committed
Status in carrotsearch-hppc source package in Bionic:
  Fix Committed
Status in clojure source package in Bionic:
  Fix Committed
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in commons-httpclient source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in ecj source package in Bionic:
  Fix Committed
Status in eclipselink source package in Bionic:
  Fix Committed
Status in elki source package in Bionic:
  Fix Committed
Status in figtree source package in Bionic:
  Fix Committed
Status in fontawesomefx source package in Bionic:
  Fix Committed
Status in geogebra source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gluegen2 source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in hikaricp source package in Bionic:
  Fix Committed
Status in hsqldb source package in Bionic:
  Fix Committed
Status in hsqldb1.8.0 source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in jabref source package in Bionic:
  Fix Committed
Status in jackson-core source package in Bionic:
  Fix Committed
Status in jackson-databind source package in Bionic:
  Fix Committed
Status in jackson-dataformat-xml source package in Bionic:
  Fix Committed
Status in jackson-module-jaxb-annotations source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javafxsvg source package in Bionic:
  Fix Committed
Status in javamail source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jboss-classfilewriter source package in Bionic:
  Fix Committed
Status in jboss-jdeparser2 source package in Bionic:
  Fix Committed
Status in jboss-modules source package in Bionic:
  Fix Committed
Status in jcommander source package in Bionic:
  Fix Committed
Status in jersey1 source package in Bionic:
  Fix Committed
Status in jftp source package in Bionic:
  Fix Committed
Status in jhove source package in Bionic:
  Fix Committed
Status in jmdns source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jruby-openssl source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jts source package in Bionic:
  Fix Committed

[Desktop-packages] [Bug 1759278] Re: hp-doctor: UnboundLocalError: local variable 'l' referenced before assignment

2019-03-26 Thread alain ivars

I have the same problem as Stdedos (stdedos)

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

Title:
  hp-doctor: UnboundLocalError: local variable 'l' referenced before
  assignment

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  hp-doctor is trying to parse the Python version. Probably other tools
  are too.

  On Python 2, sys.version is "2.7.14+", whos parts cannot be parsed as an 
integer.
  On Python 3, sys.version is "3.6.5rc1", whos parts cannot be parsed as an 
integer.

  Neither of these will work.

  
  % hp-doctor
  Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in 
  check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
  python_ver = xint((sys.version).split(' ')[0])  #find the 
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
  return l
  UnboundLocalError: local variable 'l' referenced before assignment

  
  (Note that my printer will only print "Unsupported Personality: UNKNOWN". 
This is probably an unrelated problem.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: hplip 3.17.10+repack0-5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 14:49:56 2018
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb 
kernel.sysrq=1
  SourcePackage: hplip
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (35 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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

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

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

[Desktop-packages] [Bug 1759278] Re: hp-doctor: UnboundLocalError: local variable 'l' referenced before assignment

2019-03-26 Thread alain ivars

My OS is:
$lsb_release -a 
  
14:39:55
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

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

Title:
  hp-doctor: UnboundLocalError: local variable 'l' referenced before
  assignment

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  hp-doctor is trying to parse the Python version. Probably other tools
  are too.

  On Python 2, sys.version is "2.7.14+", whos parts cannot be parsed as an 
integer.
  On Python 3, sys.version is "3.6.5rc1", whos parts cannot be parsed as an 
integer.

  Neither of these will work.

  
  % hp-doctor
  Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in 
  check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
  python_ver = xint((sys.version).split(' ')[0])  #find the 
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
  return l
  UnboundLocalError: local variable 'l' referenced before assignment

  
  (Note that my printer will only print "Unsupported Personality: UNKNOWN". 
This is probably an unrelated problem.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: hplip 3.17.10+repack0-5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 14:49:56 2018
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb 
kernel.sysrq=1
  SourcePackage: hplip
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (35 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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

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

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

[Desktop-packages] [Bug 1819925] Re: Opening applications's detail fail for snaps

** Tags removed: rls-dd-incoming

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

Title:
  Opening applications's detail fail for snaps

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

Bug description:
  Using 1:3.32.0.1-1ubuntu3 in disco

  - install the vlc snap
  - go to the settings -> applications view
  - select vlc and use the menu in the headerbar to see the application details

  It calls gnome-software, but then displays a page about vlc_vlc not
  being found, it looks like the ID used in invalid

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

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

[Desktop-packages] [Bug 1821415] Automatically added comment

Added to Trello: https://trello.com/c/sTIx3fol/288-bug1821415-pkexec-
fails-in-a-non-graphical-environment

** Tags removed: desktop-trello-import

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

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

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

[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

Marking as notfixing for release.  This doesn't mean that it won't get
worked on, and Andrea might have an idea what's going on here, but we
won't block release on this bug.


** Tags removed: rls-dd-incoming
** Tags added: rls-dd-notfixing

** Tags added: desktop-trello-import

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

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

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

[Desktop-packages] [Bug 1740869] Re: is not responding window is constantly showing when debugging a program