[Desktop-packages] [Bug 1768390] Re: BadMatch error in X_GLXSwapBuffers running OpenGL apps with nvidia-driver-390

2018-05-30 Thread Rocko
** Also affects: libglvnd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  BadMatch error in X_GLXSwapBuffers running OpenGL apps with nvidia-
  driver-390

Status in libglvnd package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  With bumblebee installed with modified library paths for the libglvnd
  setup used by nvidia-graphics-drivers-390 (see
  https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243), 3D
  apps run fine in wine, but I get an error calling X_GLXSwapBuffers
  error running OpenGL apps, eg:

  $ optirun glxheads
  glxheads: exercise multiple GLX connections (any key = exit)
  Usage:
glxheads xdisplayname ...
  Example:
glxheads :0 mars:0 venus:1
  Name: :1
Display: 0x55b464525ce0
Window:  0x2c2
Context: 0x55b46468a208
GL_VERSION:  4.6.0 NVIDIA 390.48
GL_VENDOR:   NVIDIA Corporation
GL_RENDERER: GeForce GTX 1050/PCIe/SSE2
  X Error of failed request:  BadMatch (invalid parameter attributes)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  11 (X_GLXSwapBuffers)
Serial number of failed request:  37
Current serial number in output stream:  38
  primus: warning: dropping a frame to avoid deadlock
  primus: warning: timeout waiting for display worker
  terminate called without an active exception

  This might be an issue with libglvnd rather than with the nvidia
  driver.

  Other users report the same issue, eg see comment #6 on the
  aforementioned bug and https://github.com/Bumblebee-
  Project/Bumblebee/issues/951 (comment by MrDeepPurple).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu3
  Uname: Linux 4.17.0-041700rc3-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 10:47:34 2018
  InstallationDate: Installed on 2017-08-16 (258 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (165 days ago)

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

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


[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-05-30 Thread Rocko
I had this problem, too. journalctl -b|grep glamor showed this:

/usr/lib/gdm3/gdm-x-session[2205]: (EE) modeset(0): glamor
initialization failed

which is why gnome-shell was falling back to llvmpipe. However, there
was some funny business going on with my libGL installation, because ldd
/usr/bin/glxinfo showed:

libGL.so.1 => /usr/local/lib/libGL.so.1 (0x7fe67e633000)
libGLX.so.0 => /usr/local/lib/libGLX.so.0 (0x7fe67dccd000)
libGLdispatch.so.0 => /usr/local/lib/libGLdispatch.so.0 
(0x7fe67da16000)

meaning I must have manually built and installed versions of libGL/X at
some point. I deleted the libGL/X libraries and the xorg folder from
/usr/local/lib and after a reboot I now have intel mesa graphics again.

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

2018-05-30 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Fix Released

** Changed in: gnome-shell
   Importance: Unknown => Critical

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1773497] Re: libreoffice fails when launched with no_new_privs

2018-05-30 Thread Olivier Tilloy
Thanks!

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

Title:
  libreoffice fails when launched with no_new_privs

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  If you exec libreoffice with no_new_privs (e.g. by running it under
  rr, https://rr-project.org/), the launch fails. It tries to exec
  /usr/lib/libreoffice/program/javaldx, but the exec returns EPERM
  because AppArmor has libreoffice in the libreoffice-oopslash profile,
  while /usr/lib/libreoffice/program/javaldx is unconfined, and
  transitioning to unconfined is not allowed with no_new_privs *even
  though the libreoffice-oopslash profile is only in complain mode*.
  (See profile_onexec in security/apparmor/domain.c... not clear whether
  enforcing this in complain mode is an AppArmor bug or not.)

  Maybe this could be fixed by putting
  /usr/lib/libreoffice/program/javaldx in the same confinement profile
  as libreoffice-oopslash?

  Ubuntu 18.04 LTS, libreoffice 6.0.3-0ubuntu1

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

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


[Desktop-packages] [Bug 1760450] Re: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so

2018-05-30 Thread Sosha
@Daniel

i use nvidia-driver-396.

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

Title:
  [nvidia] Xorg crashed with signal 7 in _dl_fixup() from
  _dl_runtime_resolve_xsavec() called from nvidia_drv.so

Status in xorg-server package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  after login session(suspend mode)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  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-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 20:34:29 2018
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2017-09-02 (211 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   _dl_fixup (l=0x559c10faa5a0, reloc_arg=) at 
../elf/dl-runtime.c:84
   _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
   ?? () from /usr/lib/xorg/modules/libwfb.so
   wfbComposite () from /usr/lib/xorg/modules/libwfb.so
   ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
  Title: Xorg crashed with signal 7 in _dl_fixup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions)

2018-05-30 Thread Daniel van Vugt
** Summary changed:

- Middle-click titlebar actions (like maximizing vertically) don't work (for 
all apps in Wayland sessions, and some apps in Xorg sessions)
+ Middle-click titlebar actions (like maximizing vertically) don't work (for 
all apps in Wayland sessions, and CSD apps in Xorg sessions)

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  (for all apps in Wayland sessions, and CSD apps in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 204480] Re: Window position is not remembered between starts

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => In Progress

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

Title:
  Window position is not remembered between starts

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox-3.0

  Firefox forgets the location of the main window each time I close it
  down and start it back up. I have investigated this, and it turns out
  that Firefox rewrites parts of the localstore.rdf file in my profile,
  and thus changes the screenX="499" setting to screenX="0" as can be
  seen in the below diff.

  Steps to reproduct:
  1) Start firefox and move the main window until it touches the right edge of 
the screen.
  2) Shut down firefox.
  3) Start Firefox again

  Result: Firefox is positioned on the very left side of the screen.
  Expected result: Firefox should be started in the position I left it.

  Below is a diff that shows what changes are done by Firefox to my
  localstore.rdf file between step 2 and 3:

  --- localstore.rdf_correct  2008-03-21 03:45:28.0 +0100
  +++ localstore.rdf_wrong2008-03-21 03:48:25.0 +0100
  @@ -1,21 +1,17 @@
   
   http://home.netscape.com/NC-rdf#";
xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
  +  
  +
  +
  +
  +  
 
  +   screenX="0" />
 
  -  
  -  
  -
  -
  -
  -  
   

  This problem has been observed in all Ubuntu releases that I can
  remember. Info about my Ubuntu installation and Firefox installation:

  Description:Ubuntu hardy (development branch)
  Release:8.04

  firefox:
Installed: 3.0~b4+nobinonly-0ubuntu1
Candidate: 3.0~b4+nobinonly-0ubuntu1
Version table:
   *** 3.0~b4+nobinonly-0ubuntu1 0
  500 http://se.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: i386
  Date: Fri Mar 21 03:46:38 2008
  DistroRelease: Ubuntu 8.04
  Package: firefox 3.0~b4+nobinonly-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.24-12-generic i686

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

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


[Desktop-packages] [Bug 175904] Re: Firefox window moves to current workspace

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Firefox window moves to current workspace

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in kdebase package in Ubuntu:
  Fix Released
Status in meta-gnome2 package in Ubuntu:
  Invalid
Status in metacity package in Ubuntu:
  Fix Released
Status in ubufox package in Ubuntu:
  Invalid
Status in firefox-3.0 package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: firefox-3.0

  
  FYI: I upgraded to Hardy to be able to point people at bugs, if needed. So I 
am aware of the pre-alpha status of Hardy.

  When Firefox-3.0 is set as the default browser for Gnome (System,
  Preferences, Preferred Applications) all applications use the correct
  browser. However, I have my workspaces nicely arranged, and my browser
  is in workspace 2.

  When clicking a link (to open it) in gnome-terminal or Evolution, the
  Firefox-3.0 window moves to the workspace where I clicked the link.
  But I don't want the window to move, I want to move to the workspace
  where I left the window.

  IMHO, this is a bug.

  Thanks!

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

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


[Desktop-packages] [Bug 121734] Re: orig.tar.gz has binary-only files

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  orig.tar.gz has binary-only files

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-3.0 package in Ubuntu:
  Fix Released
Status in lightning-sunbird package in Ubuntu:
  Fix Released
Status in midbrowser package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  The orig.tar.gz's of Mozilla products have some binary-only files
  (Windows DLLs and MacOS) without accompanying source code. Thus they
  do not fulfill the 'preferred form of modification' requirements of
  GPL/MPL. They either need to be removed, accompanied by source, or
  distributed under another license (such as BSD).

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

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


[Desktop-packages] [Bug 151216] Re: "Unresponsive script" note doesn't indicate which tab / page

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  "Unresponsive script" note doesn't indicate which tab / page

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  When using multiple tabs and multiple browser windows, there is no way
  (that I am aware of) to find out which tab causes the "Unresponsive
  script" dialog to appear.  How can I decide whether to "stop or go"
  when I don't know which page contains the offending script?

  You can find a screen shot e.g. at
  http://launchpadlibrarian.net/8559601/Warning%3A%20Unresponsive%20script.png
  so I'm not attaching another one.

  To my uneducated self, it would seem like a good fix if the dialog's
  title and/or the description could contain the URL of the page
  containing the problematic JavaScript.  (Still, with 16 browser
  windows and an estimated total of 200 tabs, a challenge to find it.)

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

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


[Desktop-packages] [Bug 136985] Re: layerX/layerY wrong when mouse is over scrollbar

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => New

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

Title:
  layerX/layerY wrong when mouse is over scrollbar

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

Bug description:
  Binary package hint: firefox

  When you have a DIV with scrollbars (overflow:scroll or overflow:auto)
  and connect a mouse handler like "onmousemove" to the div then
  event.layerX must contain the X mouse position relative to the upper
  left corner of the DIV. But this doesn't work in Firefox when the
  mouse is over the scrollbar. Firefox "wraps" the mouse position so it
  begins with X=0 at the left edge of the scrollbar. This is bad because
  in this way Javascript cannot determine if the mouse is over the
  scrollbar or if the mouse is on the left side of the DIV. Here is a
  demo:

  http://www.ailis.de/~k/permdata/20070903/scrollbar.html

  Move the mouse over the div and then move it to the right over the
  scrollbar and watch the displayed X coordinate wrapping from 186 to 1.
  Other browsers behave correctly. Tested it in IE, Safari, Konqueror
  and Opera. In my opinion the mouse events should not fire at all when
  the mouse pointer is over the scrollbar but my opinion is not
  important. So I think this should be fixed so Firefox behaves like all
  other browsers and don't "wrap" the mouse position.

  I also tested the current Firefox Nightly Build and the problem is
  still present there.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep  3 13:26:05 2007
  DistroRelease: Ubuntu 7.04
  Package: firefox 2.0.0.6+1-0ubuntu1
  PackageArchitecture: i386
  SourcePackage: firefox
  Uname: Linux vincent 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 
i686 GNU/Linux

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

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


[Desktop-packages] [Bug 52524] Re: Preferences > Cookies > Exceptions should default to the current site

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Preferences > Cookies > Exceptions should default to the current site

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

Bug description:
  I have my browser set not to allow cookies. This means that I often
  have to add the site that I am on to the list of exceptions in order
  to make the site work properly.

  I would find it very useful if, when I clicked Edit > Preferences >
  Cookies > Exceptions, the text box had the current URI in it
  (highlighted). It would be a matter of pressing a key (or delete) to
  remove the text, but would save a lot of time for any user wanting to
  set preferences for a site that they were already on.

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

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


[Desktop-packages] [Bug 271216] Re: Firefox prints one page only of long doc in a frame

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => In Progress

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

Title:
  Firefox prints one page only of long doc in a frame

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-firefox

  Firefox 3.01 printing: I have two frames, one containing a document that 
should take many pages to print. Firefox only prints one page, losing the rest. 
Typical site: http://www.cict.bhtafe.edu.au/subjects/ict321/bug.html
  It also prints one page for multi-frame documents from web access to M/S 
Exchange such as 
http://www.cict.bhtafe.edu.au/subjects/bug/MicrosoftOutlookWebAccess.html
  Another problem site is 
http://septemberfestival.com.au/index.php?option=com_content&task=view&id=4&Itemid=4
 which prints three pages but still loses a lot of content

  Package is Ubuntu 8.10 alpha5, but problem has occurred in many other
  distros and earlier versions of firefox.

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

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


[Desktop-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and some apps in Xorg sessions)

2018-05-30 Thread Daniel van Vugt
** Summary changed:

- Middle-click titlebar actions (like maximizing vertically) don't work in 
Wayland sessions
+ Middle-click titlebar actions (like maximizing vertically) don't work (for 
all apps in Wayland sessions, and some apps in Xorg sessions)

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  (for all apps in Wayland sessions, and some apps in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Daniel van Vugt
Given that the same code has now been released in 18.10
(3.28.2-1ubuntu1), we should treat it as a new bug and maybe not
complicate the discussion here.

Can someone please log a bug against 18.10?

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Jehandan Jeyaseelan
Hi,

In addition to my post #96 above, I downgraded gdm3 back to the release
version - 3.28.0-0ubuntu1 and am able to confirm that switching users
works perfectly between two users for me.

Therefore sounds like the fix for gdm3 - 3.28.2-0ubuntu1.1 - has
introduced further issues.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 113086] Re: The sync request protocol (_NET_WM_SYNC_REQUEST in the EWMH spec) is not supported in some GTK apps

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

** Changed in: wow-pro
   Status: Unknown => Confirmed

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

Title:
  The sync request protocol (_NET_WM_SYNC_REQUEST in the EWMH spec) is
  not supported in some GTK apps

Status in Mozilla Firefox:
  Confirmed
Status in wow pro:
  Confirmed
Status in Ubuntu:
  Invalid
Status in amarok package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Invalid
Status in mozilla-thunderbird package in Ubuntu:
  Invalid

Bug description:
  With Desktop Effects, I get black on some part of Firefox and Thunderbird 
windows.
  Some time is the menu bar, other time is the main window (in thunderbird it 
happens randomly on each part of it)
  It lasts few seconds, then it's ok.
  I think it's a refresh problem.

  P.S.: I got a black screen for 4-5 seconds even when I log in.

  Video Card: ATI IGP 340M on Compaq Presario 2136EA

  Firefox, Thunderbird, Evolution are the confirmed apps that dont
  support the protocol

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

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


[Desktop-packages] [Bug 1774307] Re: Losing drag and drop ability

2018-05-30 Thread Slavic Dragovtev
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
   1920x1080 60.10*+  60.0159.9759.9659.9340.06  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.9559.82  
   1280x1024 60.02  
   1440x900  59.89  
   1400x900  59.9659.88  
   1280x960  60.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

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

Title:
  Losing drag and drop ability

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

Bug description:
  Both in Wayland and traditional X sessions losing ability to drag and
  drop seemingly randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 18:12:09 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1774307] Re: Losing drag and drop ability

2018-05-30 Thread Daniel van Vugt
When the bug happens, please run 'xrandr' in a terminal and send us the
output to verify the session type.

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

Title:
  Losing drag and drop ability

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

Bug description:
  Both in Wayland and traditional X sessions losing ability to drag and
  drop seemingly randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 18:12:09 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1280039] Re: Message Preview shows white background with white letters

2018-05-30 Thread Christopher M. Penalver
I don't use 14.04, Evolution (instead I use Thunderbird), or Xubuntu.

** Changed in: evolution (Ubuntu)
   Status: Triaged => Invalid

** Changed in: evolution (Ubuntu)
Milestone: ubuntu-14.04-feature-freeze => None

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

Title:
  Message Preview shows white background with white letters

Status in evolution package in Ubuntu:
  Invalid

Bug description:
  1)  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  2) apt-cache policy evolution
  evolution:
Installed: 3.10.3-0ubuntu3
Candidate: 3.10.3-0ubuntu3
Version table:
   *** 3.10.3-0ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is the Evolution message preview pane
  does not show a white background with white letters.

  4) What happens instead is it does as per the attached picture.

  WORKAROUND: Use the gmail web interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb 13 06:01:19 2014
  InstallationDate: Installed on 2013-12-19 (55 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131219)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1335811] Re: Subsequent File Operations windows hang after canceling first one

2018-05-30 Thread Christopher M. Penalver
I don't use 14.04, or connect to nfs shares.

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

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

Title:
  Subsequent File Operations windows hang after canceling first one

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

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

  apt-cache policy gnome-session-fallback
  gnome-session-fallback:
Installed: 1:3.8.0-1ubuntu12
Candidate: 1:3.8.0-1ubuntu12
Version table:
   *** 1:3.8.0-1ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.8.0-1ubuntu11 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  3) What is expected to happen is when one initiates a nfs4 mounted
  file transfer from Ubuntu 14.04 using a nautilus window, and then
  cancels the transfer via clicking the button with a red circle with a
  white x in the File Operations window,  then initiates the same
  transfer, it begins with minimal delay.

  4) What happens instead is the new File Operations window opens but
  doesn't actually progress. As well, when one attempts to cancel this
  new File Operations window by clicking the cancel button, the button
  shows as if it is depressed, but doesn't actually cancel the transfer,
  and simply remains. Killing all the gvfs processes didn't recover the
  window, so it would appear to be a nautilus issue.

  The only WORKAROUND would be to restart, as restarting nautilus
  doesn't smoothly recover, causes all the desktop icons to disappear,
  and will no longer come up when initiated by a terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 30 05:21:37 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-06-21 (8 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/1335811/+subscriptions

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


[Desktop-packages] [Bug 1774307] Re: Losing drag and drop ability

2018-05-30 Thread Slavic Dragovtev
Restarted computer. Logged in ubuntu session. No ability to drag and
drop in Nautilus.

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

Title:
  Losing drag and drop ability

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

Bug description:
  Both in Wayland and traditional X sessions losing ability to drag and
  drop seemingly randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 18:12:09 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Jehandan Jeyaseelan
Hi,

Confirm that there are switching user issues.

I logged in as user A, then created a second user - user B. I clicked on
Switch User and logged in successfully as User B.

I then proceeded to switch to User A by clicking on Switch User then
clicking on User A and entering the password. Resulted in being unable
to log back into User A.

Therefore fix still has issues and I agree with others here that it
cannot be released.

I think the fix should not be released until all issues associated with
it are resolved. If another bug is causing the switch user problem then
both bugs should be fixed before the gdm3 update with fixes is released.

Login functionality is critical to an operating system and should be
working perfectly. Having multiple users created in an Ubuntu 18.04 LTS
install is a very likely scenario.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1217091] Re: getUserMedia doesn't work in Firefox/Unity in Ubuntu 13.10

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => In Progress

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

Title:
  getUserMedia doesn't work in Firefox/Unity in Ubuntu 13.10

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

Bug description:
  Firefox doesn't ask for permission to use my camera or microphone when
  calling getUserMedia. Instead, it just does nothing. None of the tests
  here work: http://mozilla.github.io/webrtc-landing/

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 23.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  BuildID: 20130807180628
  Channel: Unavailable
  Date: Mon Aug 26 22:35:55 2013
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.104  metric 
1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-3081eb08-2163-454d-b541-5572f2121104
  Plugins:
   Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
  PrefSources:
   prefs.js
   
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
   
[Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js
   
[Profile]/extensions/zoteroopenofficeintegrat...@zotero.org/defaults/preferences/zoteroOpenOfficeIntegration.js
  Profiles: Profile0 (Default) - LastVersion=23.0/20130807180628 (In use)
  RelatedPackageVersions:
   gnome-shell   3.8.4-0ubuntu1
   rhythmbox-mozilla 2.99.1-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-3081eb08-2163-454d-b541-5572f2121104
   bp-3ab5a053-9a78-4948-a5ca-a56372121010
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to saucy on 2013-06-17 (70 days ago)
  dmi.bios.date: 09/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785GM-E51 (MS-7596)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd09/28/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7596:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785GM-E51(MS-7596):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7596
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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


[Desktop-packages] [Bug 1335388] Re: Firefox does not play local flash files

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Firefox does not play local flash files

Status in Mozilla Firefox:
  Confirmed
Status in Linux Mint:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xubuntu 14.04 I cannot play local swf files int
  Firefox any more. Was OK in 13.10.

  I get the window "You have chosen to open: xxx.swf which is: Shockwave Flash 
file (yyyMB) from: /home/...
  What should Firefox do with this file?
  - Open with (Parole/Other...)
  - Save File
  Do this automatically...

  Reinstalling 14.04 completely (and installing flashplugin-installer) and 
creating a new user does not help.
  Of course this works well with flash embedded in html pages.

  In Firefox, there are 2 entries in the applications menu, one for"shockwave 
flash files" and the other for "SWF", as described in 
https://support.mozilla.org/en-US/questions/995797.
  I cannot link the action "Use shockwave flash (in Firefox)" to the type 
"shockwave flash files" as it is for "SWF file".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 30.0+build1-0ubuntu0.14.04.3
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  malaise2839 F pulseaudio
  BuildID: 20140608211132
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Jun 28 09:16:51 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-06-15 (12 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.0.254 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.5  metric 9
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}/defaults/preferences/prefs-dwhelper.js
  Profiles: Profile0 (Default) - LastVersion=30.0/20140608211132 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3259CGG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:svnLENOVO:pn3259CGG:pvrThinkPadEdgeE530:rvnLENOVO:rn3259CGG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3259CGG
  dmi.product.version: ThinkPad Edge E530
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1400226] Re: Keyboard Shortcuts doesn't display entire keyboard shortcut

2018-05-30 Thread Christopher M. Penalver
I don't use Trusty or Unity anymore. GNOME works for me.

** Changed in: unity-control-center (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Keyboard Shortcuts doesn't display entire keyboard shortcut

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy unity-control-center
  unity-control-center:
    Installed: 14.04.3+14.04.20140922-0ubuntu1
    Candidate: 14.04.3+14.04.20140922-0ubuntu1
    Version table:
   *** 14.04.3+14.04.20140922-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   14.04.3+14.04.20140410-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) What is expected to happen is when one clicks the Ubuntu icon in the 
taskbar > System Tools > Preferences > Keyboard > tab Shortcuts > Custom 
Shortcuts > button + > Name: gnome-system-monitor > Command: 
gnome-system-monitor > click button Apply > click Disabled > press on keyboard 
Ctrl+Shift+Escape and the entire keyboard shortcut is shown to the right as:
  Shift+Ctrl+Escape

  4) What happens instead is it only shows as per attached screenshot 
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1400226/+attachment/4275974/+files/screenshot.png
 :
  Shift+Ctrl+

  This is made more annoying as one cannot resize the window, or adjust
  the column sizes.

  WORKAROUND: Close and reopen this area.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  8 01:24:52 2014
  InstallationDate: Installed on 2014-06-21 (169 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

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

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


[Desktop-packages] [Bug 1774307] Re: Losing drag and drop ability

2018-05-30 Thread Daniel van Vugt
Please double-check the bug occurs in Xorg sessions. Bug 1733033 says
for another user the problem is specific to Wayland.

** Tags added: dnd

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

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

Title:
  Losing drag and drop ability

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

Bug description:
  Both in Wayland and traditional X sessions losing ability to drag and
  drop seemingly randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 18:12:09 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1774177] Re: Screen size is wrong on resume from suspend

2018-05-30 Thread Daniel van Vugt
The lock screen and login screen graphics are provided by the the gnome-
shell package.

I think the problem here may be that some instances may be running as a
different user (gdm), so your own personal settings won't apply to
those.


** Summary changed:

- Screen size is wrong on resume from suspend
+ Personal scaling settings not used on the unlock screen

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

** Tags added: hidpi

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

Title:
  Personal scaling settings not used on the unlock screen

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

Bug description:
  I run my screen on 100% scaling even though the ubuntu default for my
  2560x1440 screen is 200%. After resume from suspend it's common for
  GDM to display at 200% and only after switch back to 100%. Sometimes
  this extends to after unlock with the mouse cursor being double size
  but only when hovering over the gnome shell top bar. I tried taking a
  screenshot but running the screenshot app fixed it and the cursor was
  normal sized again.

  I've now submitted or subscribed to several gnome-shell and gdm3 bugs.
  The 18.04 transition from unity to gnome-shell was clearly a step back
  in terms of polish of the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 13:21:49 2018
  InstallationDate: Installed on 2016-10-27 (579 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169

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

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


[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal

2018-05-30 Thread Daniel van Vugt
Yeah, I know. I'm building a list of issues here:
https://trello.com/c/pe5mRmx7

Do you find the problem is better in Gnome Shell on Xorg, compared to
Gnome Shell on Wayland?

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

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

Title:
  High CPU usage by gnome-shell when only running gnome-terminal

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Even when doing nothing but displaying a terminal screen with top
  running gnome-shell uses 10% of a CPU. That seems excessive. I
  disabled all extensions to try and make the test fair. Enabling the
  system monitor extension increases the load to 13-14%. It seems that
  the gnome-shell screen painting is highly CPU consuming even if screen
  updates are infrequent (1 a second for all these cases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 11:38:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-27 (578 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago)

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

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


[Desktop-packages] [Bug 1774188] Re: unlocking the screen takes 5 seconds

2018-05-30 Thread Daniel van Vugt
Can you please attach output from 'journalctl -b' covering a time period
when the bug occurred?

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

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

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

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

Title:
  unlocking the  screen takes 5 seconds

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

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1070540] Re: Feature request: Disable tabs (tabbed browsing) altogether

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Feature request: Disable tabs (tabbed browsing) altogether

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

Bug description:
  Dear friends,

  I'd like to see the feature to disable tabs altogether.

  I like my window manager and I want it to handle all my different open
  apps, documents and sites. Offloading this job to a single app, which
  is what tabs are, is counter-productive for me.

  But Firefox doesn't have the feature to disable tabbed browsing.

  Thanks,
  Shahar

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

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


[Desktop-packages] [Bug 209607] Re: Open file with external application broken

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Open file with external application broken

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid
Status in firefox-3.0 package in Ubuntu:
  Fix Released

Bug description:
  System Kubuntu 8.04 beta, upgraded from 7.10 over the internet.
  When I click on i.e. a link to a PDF file in Firefox, I am offered a choice 
of "open with Firefox 3.0b4" (no other applications listed in the menu) or 
"save file" (the default choice).  When I drop down the "open with" menu, 
select "other..." and press "Cancel" in the dialogue box which appears, "open 
with Firefox 3.0b4" changes to "open with kpdf (default)".

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

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


[Desktop-packages] [Bug 73244] Re: Crash when closing firefox after "open with" and having still opened the file

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Crash when closing firefox after "open with" and having still opened
  the file

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

Bug description:
  1. Click on a .deb link
  2. Select "open with package installer"
  3. click install package after downloaded
  4. close firefox (because you don't need it anymore)
  5. Enter your password for sudo
  6. package manager crashes because the deb file was deleted in the moment you 
closed firefox

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

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


[Desktop-packages] [Bug 1773268] Re: locked out of system when upgrading to bionic from xenial

2018-05-30 Thread Daniel van Vugt
** Tags added: bionic

** Description changed:

  I was attempting to upgrade to bionic from xenial using do-release-
  upgrade but forgot to turn off screen locking. After an hour of
  inactivity, I ended up at the login screen but the keyboard won't allow
  me to enter keys in the login window and clicking the field results in a
  bizarre repeated "Failed to authenticate" message. See attached
  screenshot.
+ 
+ ---
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2010-04-12 (2970 days ago)
+ InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: lightdm 1.26.0-0ubuntu1
+ PackageArchitecture: amd64
+ ProcCpuinfoMinimal:
+  processor: 3
+  vendor_id: GenuineIntel
+  cpu family   : 6
+  model: 42
+  model name   : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
+  stepping : 7
+  microcode: 0x25
+  cpu MHz  : 1689.366
+  cache size   : 6144 KB
+  physical id  : 0
+  siblings : 4
+  core id  : 3
+  cpu cores: 4
+  apicid   : 6
+  initial apicid   : 6
+  fpu  : yes
+  fpu_exception: yes
+  cpuid level  : 13
+  wp   : yes
+  flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt 
dtherm ida arat pln pts
+  bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass
+  bogomips : 6219.77
+  clflush size : 64
+  cache_alignment  : 64
+  address sizes: 36 bits physical, 48 bits virtual
+  power management:
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-05-24 (5 days ago)
+ UserGroups: adm admin audio cdrom dialout lpadmin mythtv plugdev sambashare

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

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

Title:
  locked out of system when upgrading to bionic from xenial

Status in lightdm package in Ubuntu:
  New

Bug description:
  I was attempting to upgrade to bionic from xenial using do-release-
  upgrade but forgot to turn off screen locking. After an hour of
  inactivity, I ended up at the login screen but the keyboard won't
  allow me to enter keys in the login window and clicking the field
  results in a bizarre repeated "Failed to authenticate" message. See
  attached screenshot.

  ---
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2010-04-12 (2970 days ago)
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: lightdm 1.26.0-0ubuntu1
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 3
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 42
   model name   : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
   stepping : 7
   microcode: 0x25
   cpu MHz  : 1689.366
   cache size   : 6144 KB
   physical id  : 0
   siblings : 4
   core id  : 3
   cpu cores: 4
   apicid   : 6
   initial apicid   : 6
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt 
dtherm ida arat pln pts
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass
   bogomips : 6219.77
   clflush size : 64
   cache_alignment  : 64
   address sizes: 36 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (5 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin mythtv plugdev sambashare

To manage notifications about this bug go to:
https://bugs.l

[Desktop-packages] [Bug 1455938] Re: [HP OfficeJet 5610v] HPLIP notes print job completed but Job Queue notes "On Hold"

2018-05-30 Thread Christopher M. Penalver
The release is EOL, haven't reproduced in later releases.

** No longer affects: hplip (Ubuntu)

** Project changed: hplip => hplip (Ubuntu)

** Changed in: hplip (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [HP OfficeJet 5610v] HPLIP notes print job completed but Job Queue
  notes "On Hold"

Status in hplip package in Ubuntu:
  Invalid

Bug description:
  What is expected to happen is when one USB connects an HP OfficeJet 5610v to 
Ubuntu 15.04 server, adds the printer to the server via the hplip-gui package, 
modifies just the lines below:
  sudo nano /etc/samba/smb.conf
  [printers]
 comment = All Printers
 browseable = no
 path = /var/spool/samba
 printable = yes
 guest ok = yes
 read only = yes
 create mask = 0700

  Goes to with a web browser:
  http://localhost:631/admin/
  Check checkbox "Share printers connected to this system", and one may print 
from another Ubuntu 15.04 client via ipp.

  What happens instead is that the hplip-gui notes the print job
  completed, but the job queue notes a job held. The program doing the
  printing printing was both LibreOffice Writer and Evince. Hence, the
  software initiating the print job seems not at fault here.

  The printer prints fine if one connects the client directly via USB.

  Also this would be a regression as this all used to work with Trusty
  server and Trusty/Utopic clients.

  Following https://wiki.ubuntu.com/DebuggingPrintingProblems :

  ls -l /dev/usb/lp* /dev/bus/usb/*/*
  ls: cannot access /dev/usb/lp*: No such file or directory
  crw-rw-r--  1 root root  189,   0 May 17 08:10 /dev/bus/usb/001/001
  crw-rw+ 1 root saned 189,   1 May 17 10:07 /dev/bus/usb/001/002
  crw-rw-r--  1 root root  189, 128 May 17 08:10 /dev/bus/usb/002/001
  crw-rw-r--  1 root root  189, 129 May 17 08:10 /dev/bus/usb/002/002
  crw-rw-r--  1 root root  189, 256 May 17 08:10 /dev/bus/usb/003/001
  crw-rw-r--  1 root root  189, 257 May 17 08:10 /dev/bus/usb/003/002
  crw-rw-r--  1 root root  189, 384 May 17 08:10 /dev/bus/usb/004/001
  crw-rw-r--  1 root root  189, 385 May 17 08:10 /dev/bus/usb/004/002

  sudo usb_printerid /dev/usb/lp0
  Error: No such file or directory: can't open '/dev/usb/lp0'

  sudo usb_printerid /dev/usb/lp1 
  Error: No such file or directory: can't open '/dev/usb/lp1'

  hpinfo -i
  No command 'hpinfo' found, did you mean:
   Command 'lpinfo' from package 'cups-client' (main)
   Command 'hinfo' from package 'ganeti' (universe)
   Command 'hinfo' from package 'ganeti-htools' (universe)
   Command 'hp-info' from package 'hplip' (main)
   Command 'shpinfo' from package 'shapelib' (universe)
   Command 'pinfo' from package 'pinfo' (universe)
   Command 'epinfo' from package 'photopc' (universe)
  hpinfo: command not found
  moniker@pc:/var/crash$ hp-info -i

  HP Linux Imaging and Printing System (ver. 3.15.2)
  Device Information Utility ver. 5.2

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Using device: hp:/usb/Officejet_5600_series?serial=CN6ABD531H04B2

  
  hp:/usb/Officejet_5600_series?serial=CN6ABD531H04B2

  Device Parameters (dynamic data):
Parameter Value(s)  

  
--
agent1-ackFalse 

agent1-desc   Black cartridge   

agent1-dvc0 

agent1-health 0 

agent1-health-descGood/OK   

agent1-hp-ink False 

agent1-id 0 

agent1-kind   3 

agent1-known  False 

agent1-level  66

agent1-level-trigger  0 

agent1-sku56 (C6656A) /27 (C8727A)  

agent1-type   1 

agent1-virgin False 

back-end

[Desktop-packages] [Bug 1455938] [NEW] [HP OfficeJet 5610v] HPLIP notes print job completed but Job Queue notes "On Hold"

2018-05-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

What is expected to happen is when one USB connects an HP OfficeJet 5610v to 
Ubuntu 15.04 server, adds the printer to the server via the hplip-gui package, 
modifies just the lines below:
sudo nano /etc/samba/smb.conf
[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = yes
   read only = yes
   create mask = 0700

Goes to with a web browser:
http://localhost:631/admin/
Check checkbox "Share printers connected to this system", and one may print 
from another Ubuntu 15.04 client via ipp.

What happens instead is that the hplip-gui notes the print job
completed, but the job queue notes a job held. The program doing the
printing printing was both LibreOffice Writer and Evince. Hence, the
software initiating the print job seems not at fault here.

The printer prints fine if one connects the client directly via USB.

Also this would be a regression as this all used to work with Trusty
server and Trusty/Utopic clients.

Following https://wiki.ubuntu.com/DebuggingPrintingProblems :

ls -l /dev/usb/lp* /dev/bus/usb/*/*
ls: cannot access /dev/usb/lp*: No such file or directory
crw-rw-r--  1 root root  189,   0 May 17 08:10 /dev/bus/usb/001/001
crw-rw+ 1 root saned 189,   1 May 17 10:07 /dev/bus/usb/001/002
crw-rw-r--  1 root root  189, 128 May 17 08:10 /dev/bus/usb/002/001
crw-rw-r--  1 root root  189, 129 May 17 08:10 /dev/bus/usb/002/002
crw-rw-r--  1 root root  189, 256 May 17 08:10 /dev/bus/usb/003/001
crw-rw-r--  1 root root  189, 257 May 17 08:10 /dev/bus/usb/003/002
crw-rw-r--  1 root root  189, 384 May 17 08:10 /dev/bus/usb/004/001
crw-rw-r--  1 root root  189, 385 May 17 08:10 /dev/bus/usb/004/002

sudo usb_printerid /dev/usb/lp0
Error: No such file or directory: can't open '/dev/usb/lp0'

sudo usb_printerid /dev/usb/lp1 
Error: No such file or directory: can't open '/dev/usb/lp1'

hpinfo -i
No command 'hpinfo' found, did you mean:
 Command 'lpinfo' from package 'cups-client' (main)
 Command 'hinfo' from package 'ganeti' (universe)
 Command 'hinfo' from package 'ganeti-htools' (universe)
 Command 'hp-info' from package 'hplip' (main)
 Command 'shpinfo' from package 'shapelib' (universe)
 Command 'pinfo' from package 'pinfo' (universe)
 Command 'epinfo' from package 'photopc' (universe)
hpinfo: command not found
moniker@pc:/var/crash$ hp-info -i

HP Linux Imaging and Printing System (ver. 3.15.2)
Device Information Utility ver. 5.2

Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Using device: hp:/usb/Officejet_5600_series?serial=CN6ABD531H04B2


hp:/usb/Officejet_5600_series?serial=CN6ABD531H04B2

Device Parameters (dynamic data):
  Parameter Value(s)
  
    
--
  agent1-ackFalse   
  
  agent1-desc   Black cartridge 
  
  agent1-dvc0   
  
  agent1-health 0   
  
  agent1-health-descGood/OK 
  
  agent1-hp-ink False   
  
  agent1-id 0   
  
  agent1-kind   3   
  
  agent1-known  False   
  
  agent1-level  66  
  
  agent1-level-trigger  0   
  
  agent1-sku56 (C6656A) /27 (C8727A)
  
  agent1-type   1   
  
  agent1-virgin False   
  
  back-end  hp  
  
  cups-printers ['hpwifiprinter']   
  
  cups-uri  
hp:/usb/Officejet_5600_series?serial=CN6ABD531H04B2   
  dev-file  
  
  device-state  1   
  
  device-uri
hp:/usb/Officejet_5600_series?serial=CN6ABD531H04B2   
  deviceid  MFG:HP;MDL:Officejet 5600   
  
  

[Desktop-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => Confirmed

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

Title:
  [i915 SNB] Totem window is all black in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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


[Desktop-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [i915 SNB] Totem window is all black in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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


[Desktop-packages] [Bug 1770502] Re: Brasero hangs when burning cds

2018-05-30 Thread Mohammads
Same for burning "Audio CD"

I'm using bionic x64 on Asus_K43SD, After selecting files and pushing
burn button, brasero hangs on the 'starting to record' dialogue!

Note: There were no any problem on artful x64 for burning "Audio CD".

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

Title:
  Brasero hangs when burning cds

Status in brasero package in Ubuntu:
  New

Bug description:
  Brasero hangs at the "starting recording..." status box and the
  progress bar freezes. Nothing is written to the disc. I did not have
  this problem prior to upgrading to 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brasero 3.12.1-4ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 17:11:18 2018
  InstallationDate: Installed on 2018-04-28 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions

2018-05-30 Thread Daniel van Vugt
** Changed in: gstreamer-vaapi (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [i915 SNB] Totem window is all black in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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


[Desktop-packages] [Bug 1774307] [NEW] Losing drag and drop ability

2018-05-30 Thread Slavic Dragovtev
Public bug reported:

Both in Wayland and traditional X sessions losing ability to drag and
drop seemingly randomly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 18:12:09 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-04-27 (33 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "attempts at drag and dropping"
   
https://bugs.launchpad.net/bugs/1774307/+attachment/5146758/+files/Screencast%20from%2005-30-2018%2006%3A11%3A41%20PM.webm

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

Title:
  Losing drag and drop ability

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Both in Wayland and traditional X sessions losing ability to drag and
  drop seemingly randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 18:12:09 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1774304] [NEW] /usr/bin/unity-control-center:11:unity_own_setting_exists:menuvisibility_widget_refresh:g_cclosure_marshal_VOID__STRINGv:_g_closure_invoke_va:g_signal_emit_valis

2018-05-30 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: xenial

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

Title:
  /usr/bin/unity-control-
  
center:11:unity_own_setting_exists:menuvisibility_widget_refresh:g_cclosure_marshal_VOID__STRINGv:_g_closure_invoke_va:g_signal_emit_valist

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-control-center.  This problem was most recently seen with package version 
15.04.0+16.04.20171130-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/402ac0125ecbbfc7797067baf450877354154fd7 
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/unity-control-center/+bug/1774304/+subscriptions

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


[Desktop-packages] [Bug 1091453] Re: Firefox hangs while moving already downloaded part of the file to selected destination if it was just mounted on selection.

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => New

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

Title:
  Firefox hangs while moving already downloaded part of the file to
  selected destination if it was just mounted on selection.

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

Bug description:
  Steps to reproduce:
  0. Set 
browser.download.useDownloadDir = false
browser.download.lastDir = /media/unmounted/partition
  1. Unmount the partition.
  2. Start downloading a big file (several GiBs) from a server that gives 
several MiBs per second.
  3. Mount the partition in the file selection dialog and select a directory on 
it as destination.

  Then firefox freezes completely for some time. AFAIU it starts
  downloading somewhere ( /tmp ?) and then moves already downloaded part
  of the file to a new destination.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 17.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic-pae 3.2.33
  Uname: Linux 3.2.0-34-generic-pae i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  i  2786 F pulseaudio
   /dev/snd/controlC0:  i  2786 F pulseaudio
  BuildID: 20121129162756
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa20 irq 52'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,14627681,00100302'
 Controls  : 44
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Mon Dec 17 23:38:26 2012
  DefaultProfilePrefSources:
   prefs.js
   
[Profile]/extensions/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}/defaults/preferences/prefs-dwhelper.js
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   #auto lo
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.104  metric 
1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   lxcbr0no wireless extensions.
  MarkForUpload: True
  MostRecentCrashID: bp-b712e3bd-0b34-445d-80e3-685b62121215
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins:
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   Windows Media Player Plug-in 10 (compatible; Totem) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Totem 2.32.0) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=17.0.1/20121129162756
   Profile1 - LastVersion=8.0/2015184056 (Out of date)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-b712e3bd-0b34-445d-80e3-685b62121215
   bp-ef838a78-7d08-47b2-8d40-cca242121117
   bp-2a30c0ae-6941-44a7-bde1-deffe2111012
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-GD53 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0/2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0/2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/02/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD53(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
  dmi.product.name: MS-7681
  dmi.product.version: 1.0/2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1774295] [NEW] Computer becomes slow

2018-05-30 Thread Ivan Pedroso Barreto
Public bug reported:

After 20 - 30 min of use (heavy graphic usage - photos), the system
becomes very slow. Sometimes even in the right click of the mouse the
menu takes a long time to be shown. It disappears if the machine is
rebooted but after 20 - 30 min. it start over again.

PS - It is not a fresh install. I used the upgrade mode in software
update (using LTS 14.04 before). This problem starts after the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May 30 20:58:00 2018
DistUpgraded: 2018-05-05 18:18:09,353 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
InstallationDate: Installed on 2016-08-02 (666 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20059
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=3f7904bb-d4b1-4e96-9e2f-be3cfb99134b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-05 (25 days ago)
dmi.bios.date: 04/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 29CN23WW(V2.01)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnLENOVO:bvr29CN23WW(V2.01):bd04/07/2010:svnLENOVO:pn20059:pvrIdeapadZ460:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: 20059
dmi.product.version: Ideapad Z460
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat May  5 15:08:57 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 623 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Computer becomes slow

Status in xorg package in Ubuntu:
  New

Bug description:
  After 20 - 30 min of use (heavy graphic usage - photos), the system
  becomes very slow. Sometimes even in the right click of the mouse the
  menu takes a long time to be shown. It disappears if the machine is
  rebooted but after 20 - 30 min. it start over again.

  PS - It is not a fresh install. I used the upgrade mode in software
  update (using LTS 14.04 before). This problem starts after the
  upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 30 20:58:00 2018
  DistUpgraded: 2018-05-05 18:18:09,353 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

2018-05-30 Thread Dirk F
"So the fix could be what is proposed, or/and moving the packagekit hook
to the right place."

I'd say both.

I understand that, per
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/comments/8,
the PackageKit side of the issue would be fixed if Ubuntu shipped
version 0.8.14 or later, which has been true since Xenial as Andreas
observes in comment #10.

Regarding the pm-utils fix, the problems seem to be that no-one is
prepared to own and update pm-utils, and the systemd versions of Ubuntu
don't need pm-utils (in fact, could be seriously confused by it).
Consequently the fix should be implemented in Debian, as Christian says
in comment #7, where pm-utils has been recognised as orphaned and is
still being updated despite Debian using systemd.

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

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

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 55293] Re: No units for margin settings in printing properties

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  No units for margin settings in printing properties

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

Bug description:
  When you do File->Print...->Properties, there's an area labelled "Gap
  from edge of paper to margin". In it there are widgets for
  top/bottom/left/right margins which contain numerical values. However
  no units (mm/inches/etc.) are specified so you don't know what the
  values mean.

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

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


[Desktop-packages] [Bug 62802] Re: [-dev] include static libraries: libxpcomglue.a, libxpcomglue_s.a

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  [-dev] include static libraries: libxpcomglue.a, libxpcomglue_s.a

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Invalid
Status in xulrunner-1.9 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  The firefox (or -dev) package should contain the static libraries
  libxpcomglue.a and libxpcomglue_s.a. Those are necessary when you want
  to build a standalone component without depending on libxpcom /
  depending on nonfrozen API from xpcom.

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

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


[Desktop-packages] [Bug 114441] Re: Gecko Engine does not support the XHTML 1.1 ruby tag

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: In Progress => Fix Released

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

Title:
  Gecko Engine does not support the XHTML 1.1 ruby tag

Status in Epiphany Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: epiphany-browser

  Visit a website such as http://icculus.org/~mongoose/index-jp2.html --
  notice Ruby tags are ignored.  This works in IE and can work with a
  plugin in firefox ( http://piro.sakura.ne.jp/xul/_rubysupport.html.en
  ).  Ruby is part of the XHTML 1.1 standard.

  
  http://www.w3.org/TR/ruby/

  ProblemType: Bug
  Architecture: amd64
  Date: Sun May 13 11:42:29 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/epiphany
  Package: epiphany-browser 2.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/epiphany
  ProcCwd: /home/mongoose
  ProcEnviron:
   LANGUAGE=en_US:en
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  Uname: Linux namie 2.6.20-14-generic #2 SMP Thu Apr 12 22:25:02 UTC 2007 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/114441/+subscriptions

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


[Desktop-packages] [Bug 197781] Re: Firefox preferences - some categories do not work if clicked too fast

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Firefox preferences - some categories do not work if clicked too fast

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox

  I am using an up-to-date installation of hardy alpha 5 with firefox 3
  beta 3.

  What happens is the following: When I go to the preferences-window,
  some categories so not work. With categories I mean "Main", "Tabs",
  "Content" and so on. This means: Usually when I click on a category,
  the appropriate content is shown. However, when I click on categories
  that no not work, nothing happens (a.k.a the content from the category
  selected before is still showing). See attached screenshot, which
  shows the content of "Main", although "Security" is selected.

  After each restart of firefox, other categories are affected. Which
  ones seems to be quite random.

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

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


[Desktop-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-30 Thread Christopher M. Penalver
Mike L, to clarify, does this issue happen when using a wired USB mouse?

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

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  What happens when booting immediately from Windows to Ubuntu is that
  the mouse scrolls multiple lines at time. This problem doesn't happen
  when booting to and using Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  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.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1773497] Re: libreoffice fails when launched with no_new_privs

2018-05-30 Thread Roc-ocallahan
Filed https://bugs.documentfoundation.org/show_bug.cgi?id=117922

** Bug watch added: Document Foundation Bugzilla #117922
   https://bugs.documentfoundation.org/show_bug.cgi?id=117922

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

Title:
  libreoffice fails when launched with no_new_privs

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  If you exec libreoffice with no_new_privs (e.g. by running it under
  rr, https://rr-project.org/), the launch fails. It tries to exec
  /usr/lib/libreoffice/program/javaldx, but the exec returns EPERM
  because AppArmor has libreoffice in the libreoffice-oopslash profile,
  while /usr/lib/libreoffice/program/javaldx is unconfined, and
  transitioning to unconfined is not allowed with no_new_privs *even
  though the libreoffice-oopslash profile is only in complain mode*.
  (See profile_onexec in security/apparmor/domain.c... not clear whether
  enforcing this in complain mode is an AppArmor bug or not.)

  Maybe this could be fixed by putting
  /usr/lib/libreoffice/program/javaldx in the same confinement profile
  as libreoffice-oopslash?

  Ubuntu 18.04 LTS, libreoffice 6.0.3-0ubuntu1

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

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


[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV

2018-05-30 Thread Jamie Strandboge
I had some luck with this not pausing/blinking gnome-shell:

$ sudo udevadm control --reload-rules
$ sudo udevadm trigger --subsystem-nomatch=input
$ sudo udevadm trigger --property-match=ID_INPUT_JOYSTICK=1

Alan, perhaps you can upgrade to core from edge (since it does some
things with ID_INPUT_JOYSTICK) see if you can crash your system by
doing:

$ for i in `seq 1 100` ; do sudo udevadm control --reload-rules ; sudo
udevadm trigger ; done

If you can, please see if this doesn't crash it:

$ for i in `seq 1 100` ; do sudo udevadm control --reload-rules ; sudo
udevadm trigger --subsystem-nomatch=input ; sudo udevadm trigger
--property-match=ID_INPUT_JOYSTICK=1 ; done

If that works, I'll give some thought to updating the udev backend to
only call 'sudo udevadm trigger --subsystem-match=input' when absolutely
needed (eg, when install mir, X or wayland snaps).

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

Title:
  Xorg crashed with SIGSEGV

Status in snapd:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  Installed a snap, immediately after I installed it, the machine froze
  and then x crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 30 14:15:35 2018
  Disassembly: => 0x7f6b0008:   Cannot access memory at address 
0x7f6b0008
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541]
  InstallationDate: Installed on 2018-02-13 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook P65_P67RGRERA
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f6b0008:Cannot access memory at address 
0x7f6b0008
   PC (0x7f6b0008) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graph

[Desktop-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-30 Thread Christopher M. Penalver
** Summary changed:

- [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple 
lines at a time.
+ [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes 
mouse to scroll multiple lines at a time

** Description changed:

- In 16.04 and 18.04, the mouse scrolls multiple lines at time. Sometimes
- rebooting doesn't fix the issue. This problem doesn't happen in Windows
- 10.
+ What happens when booting immediately from Windows to Ubuntu is that the
+ mouse scrolls multiple lines at time. This problem doesn't happen when
+ booting to and using Windows 10.
  
  WORKAROUND: https://sourceforge.net/projects/resetmsmice/
+ 
+ WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
+ Windows.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  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.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  What happens when booting immediately from Windows to Ubuntu is that
  the mouse scrolls multiple lines at time. This problem doesn't happen
  when booting to and using Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PD

[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV

2018-05-30 Thread Jamie Strandboge
I noticed I could prevent gnome-shell from blinking/pausing if instead
of 'sudo udevadm control --reload-rules && sudo udevadm trigger' I
instead did 'sudo udevadm control --reload-rules && sudo udevadm trigger
--subsystem-nomatch=input'. I'm not sure there is much that snapd can do
with that information, but it might be a clue to make gnome-
shell/X11/nvidia to behave better.

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

Title:
  Xorg crashed with SIGSEGV

Status in snapd:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  Installed a snap, immediately after I installed it, the machine froze
  and then x crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 30 14:15:35 2018
  Disassembly: => 0x7f6b0008:   Cannot access memory at address 
0x7f6b0008
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541]
  InstallationDate: Installed on 2018-02-13 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook P65_P67RGRERA
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f6b0008:Cannot access memory at address 
0x7f6b0008
   PC (0x7f6b0008) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Mar 29 14:49:09 2018
  xserver.configfile: default
  xserver.err

[Desktop-packages] [Bug 1774281] [NEW] Username displays incorrectly on login screen

2018-05-30 Thread Matthew
Public bug reported:

Just did a clean install on a mid 2012 15" macbook pro. Every time that
I get to the login screen, my username appears as strange blocks and
shapes as pictured here:

https://drive.google.com/file/d/0B4DXnUg-
SK6WOG1ybjFTYnBWQ3B6eWVEelR6TmJWcHNJb2ZR/view?usp=sharing


18.04 LTS
xorg:
  Installed: 1:7.7+19ubuntu7
  Candidate: 1:7.7+19ubuntu7
  Version table:
 *** 1:7.7+19ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 15:10:15 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fb]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc]
MachineType: Apple Inc. MacBookPro9,1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-22-generic ro 
root=UUID=bcac24f1-47fa-44d8-ae55-e5dff5f77a7d 
initrd=boot\initrd.img-4.15.0-22-generic
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-4B7AC7E43945597E
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-4B7AC7E43945597E
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "20180530_145930.jpg"
   
https://bugs.launchpad.net/bugs/1774281/+attachment/5146677/+files/20180530_145930.jpg

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

Title:
  Username displays incorrectly on login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Just did a clean install on a mid 2012 15" macbook pro. Every time
  that I get to the login screen, my username appears as strange blocks
  and shapes as pictured here:

  https://drive.google.com/file/d/0B4DXnUg-
  SK6WOG1ybjFTYnBWQ3B6eWVEelR6TmJWcHNJb2ZR/view?usp=sharing

  
  18.04 LTS
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:10:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fb]
   NVIDIA Corporation GK107M [GeForce GT 65

[Desktop-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-05-30 Thread Christopher M. Penalver
** Description changed:

- What was expected to happen is when LibreOffice crashes in Xenial, it
- logs a crash report to file against to errors.ubuntu.com.
+ What is expected to happen is when LibreOffice crashes, a crash report
+ is created in the /var/crash folder.
  
- What happened instead is LibreOffice crashed but apport didn't log a
- crash file in /var/crash despite being enabled. Other programs that
- crash are picked up by apport so appears LO+apport issue.
+ What happened instead is LibreOffice crashed but apport didn't create a
+ crash file in the /var/crash folder, despite running and being enabled.
+ Apport creating crash files in /var/crash used to happen in Xenial, and
+ in prior releases. Other programs that crash are picked up by apport so
+ appears LO+apport issue.
+ 
+ LibreOffice has reference to placing crash files as per:
+ cat /etc/libreoffice/sofficerc | grep crash
+ CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash
  
  I don't have any 3rd party LO plugins installed.
  
- apt-show-versions -r libreoffice* 
+ apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed
  
  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1
  
  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs
  
  default = 'ubuntu'
  
  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor
  
  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None
  
  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

** Tags removed: regression-release
** Tags added: regression-update

-- 
You received this bug notification because yo

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Bodinux
For information, I have had switching users issues since the fresh
install of 18.04 on top of not being able to login myself.

I let the gnome people continue to work on this issue and thank them for their 
work. In the meantime, my workaround is to turn back to lightdm which works 
very well for me (as it as done for some many years now):
-no login issues
-no multiple users switching issues
-automatic keyboard layout selection as per the user preference (we use 
different layout in my family)
-working on screen keyboard (displays other layout than qwerty).

I'll probably join ubuntu mainstream packages when these issues will be
solved.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple lines at a time.

2018-05-30 Thread Mike L
1) That is correct. Only rebooting into Windows will trigger the bug when you 
go back into Ubuntu. I've tested this just now to confirm it.
2) OK. Will take note.

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

Title:
  [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll
  multiple lines at a time.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  In 16.04 and 18.04, the mouse scrolls multiple lines at time.
  Sometimes rebooting doesn't fix the issue. This problem doesn't happen
  in Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  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.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV

2018-05-30 Thread Jamie Strandboge
I suspect this is because snapd will do 'sudo udevadm control --reload-
rules && sudo udevadm trigger' on interface connections. These
operations are supposed to be safe but I've seen with my Intel graphics
that gnome-shell/X11 will blink when this happens (due to the 'udevadm
trigger') but it doesn't crash. I suspect that your particular
combination of gnome-shell/X11/nvidia isn't responding particularly well
when this happens.

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

Title:
  Xorg crashed with SIGSEGV

Status in snapd:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  Installed a snap, immediately after I installed it, the machine froze
  and then x crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 30 14:15:35 2018
  Disassembly: => 0x7f6b0008:   Cannot access memory at address 
0x7f6b0008
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541]
  InstallationDate: Installed on 2018-02-13 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook P65_P67RGRERA
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f6b0008:Cannot access memory at address 
0x7f6b0008
   PC (0x7f6b0008) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Mar 29 14:4

[Desktop-packages] [Bug 1771290] Re: Untranslated list of encodings in preferences

2018-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-terminal - 3.28.2-1ubuntu1

---
gnome-terminal (3.28.2-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian. Remaining changes:
+ debian/rules:
  - Install compatibility version of gnome-terminal.desktop
+ gnome-terminal.wrap, debian/rules:
  - Add a wrapper script to restore command line compatibility.
+ debian/control.in:
  - gnome-terminal depends on python3, python3-gi and gir1.2-glib-2.0 for
the wrapper script.
  - Don't Build-Depend on PCRE2
+ Add 0001-Restore-transparency.patch:
  - Restore transparency support
+ Add 0001-Add-style-classes-and-CSS-names-to-some-of-our-widge.patch:
  - Add CSS names and style classes so we can theme things more easily.
+ Add 0001-screen-window-Extra-padding-around-transparent-termi.patch:
  - Fix transparency on Wayland. Patch by Owen Taylor, via Debarshi Ray @
Fedora (LP: #1650395)
+ Add 50_add_unity_quicklist.patch:
  - Add Unity quicklist menu item.
+ Add 52_support_apturl.patch:
  - Support apt: urls.
+ Add 60_add_lp_handler.patch:
  - Add a handler for launchpad bug URLs.
+ Add scrollbar-background-theming.patch:
  - Draw background under the scrollbar that matches the actual terminal
background color. This allows proper theming.
+ Add debian/patches/revert-pcre2.patch:
  - Revert changes that require PCRE2 since it's not in main
(see MIR #163666)
  * Keep 006-fix-invalid-appstream-metadata.patch:
- Ubuntu's AppStream versions and http://appstream.ubuntu.com/
  don't support gnome-terminal's syntax yet
  * debian/{gbp.conf,control{,.in}}: Update for Ubuntu

gnome-terminal (3.28.2-1) unstable; urgency=medium

  [ Iain Lane ]
  * New upstream release 3.28.2 (LP: #1774167)
+ [47a9491] client: legacy: Fix output commenting.
  Make sure each line starts with '#' even if the message contains
  embedded newlines.
+ [1828cb6] prefs: editor: Translate encoding names (LP: #1771290)
  * Bump required vte to 2.52.2, per upstream.

gnome-terminal (3.28.1-2) unstable; urgency=medium

  * Restore File > New Tab menu item. Thanks Debarshi Ray for the suggestion.
(LP: #1747171) (Closes: #783903)

 -- Iain Lane   Wed, 30 May 2018 13:47:09 +0100

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

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

Title:
  Untranslated list of encodings in preferences

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Bionic:
  Triaged

Bug description:
  The list of encodings in Preferences → Compatibility is in English.
  The list in the Terminal → Set Character Encoding menu is properly
  translated, though.

  Upstream bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=795358

  Upstream trivial fix: https://git.gnome.org/browse/gnome-
  terminal/commit/?h=gnome-3-28&id=1828cb6d5

  Could you please backport this tiny fix to Bionic LTS?

  (We're planning to release gnome-terminal 3.28.2 containing this plus
  at least one other tiny fix in about a week.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1 [modified: usr/bin/gnome-terminal 
usr/lib/gnome-terminal/gnome-terminal-server 
usr/share/applications/org.gnome.Terminal.desktop 
usr/share/glib-2.0/schemas/org.gnome.Terminal.gschema.xml 
usr/share/metainfo/org.gnome.Terminal.appdata.xml]
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue May 15 09:46:24 2018
  InstallationDate: Installed on 2016-11-09 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to bionic on 2018-03-14 (61 days ago)

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

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


[Desktop-packages] [Bug 1774167] Re: [SRU] 3.28.2 / 0.52.2

2018-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-terminal - 3.28.2-1ubuntu1

---
gnome-terminal (3.28.2-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian. Remaining changes:
+ debian/rules:
  - Install compatibility version of gnome-terminal.desktop
+ gnome-terminal.wrap, debian/rules:
  - Add a wrapper script to restore command line compatibility.
+ debian/control.in:
  - gnome-terminal depends on python3, python3-gi and gir1.2-glib-2.0 for
the wrapper script.
  - Don't Build-Depend on PCRE2
+ Add 0001-Restore-transparency.patch:
  - Restore transparency support
+ Add 0001-Add-style-classes-and-CSS-names-to-some-of-our-widge.patch:
  - Add CSS names and style classes so we can theme things more easily.
+ Add 0001-screen-window-Extra-padding-around-transparent-termi.patch:
  - Fix transparency on Wayland. Patch by Owen Taylor, via Debarshi Ray @
Fedora (LP: #1650395)
+ Add 50_add_unity_quicklist.patch:
  - Add Unity quicklist menu item.
+ Add 52_support_apturl.patch:
  - Support apt: urls.
+ Add 60_add_lp_handler.patch:
  - Add a handler for launchpad bug URLs.
+ Add scrollbar-background-theming.patch:
  - Draw background under the scrollbar that matches the actual terminal
background color. This allows proper theming.
+ Add debian/patches/revert-pcre2.patch:
  - Revert changes that require PCRE2 since it's not in main
(see MIR #163666)
  * Keep 006-fix-invalid-appstream-metadata.patch:
- Ubuntu's AppStream versions and http://appstream.ubuntu.com/
  don't support gnome-terminal's syntax yet
  * debian/{gbp.conf,control{,.in}}: Update for Ubuntu

gnome-terminal (3.28.2-1) unstable; urgency=medium

  [ Iain Lane ]
  * New upstream release 3.28.2 (LP: #1774167)
+ [47a9491] client: legacy: Fix output commenting.
  Make sure each line starts with '#' even if the message contains
  embedded newlines.
+ [1828cb6] prefs: editor: Translate encoding names (LP: #1771290)
  * Bump required vte to 2.52.2, per upstream.

gnome-terminal (3.28.1-2) unstable; urgency=medium

  * Restore File > New Tab menu item. Thanks Debarshi Ray for the suggestion.
(LP: #1747171) (Closes: #783903)

 -- Iain Lane   Wed, 30 May 2018 13:47:09 +0100

** Changed in: gnome-terminal (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] 3.28.2 / 0.52.2

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Bionic:
  In Progress
Status in vte2.91 source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  The second stable release in the 3.28 series.

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  We're allowed to believe upstream's bug fixes without explicitly
  verifying them:

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

  [ Regresison potential ]

  If the update is rotten then the terminal might not work at all. There
  are fixes related to the list of encodings; if that's bad then you
  might not be able to use this functionality.

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

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


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

2018-05-30 Thread Mike Fairbank
Yes I found this bug too.  The bug arose after I did a clean full
install of Mate 18.04LTS, but I re-used my old Mate 16.04 home
partition. So it's probably confused by my old style configuration files
which were imported from Mate16.04 to Mate 18.04.

The workaround of using Mate Tweak to switch the panel style to
something else and then back to Traditional fixed the problem for me.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 21753] Re: Epiphany 'Move tab to window' option doesn't work in breezy

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Epiphany 'Move tab to window' option doesn't work in breezy

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Won't Fix
Status in xulrunner-1.9 package in Ubuntu:
  Won't Fix

Bug description:
  Using the 'Tabsmenu' extension in epiphany-extensions, the option to move tabs
  between windows no longer works. This feature worked fine in Hoary.

  https://bugzilla.mozilla.org/show_bug.cgi?id=296002:
  https://bugzilla.mozilla.org/show_bug.cgi?id=296002

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

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


[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread KenWilson
Regarding gdm3 3.28.2-0ubuntu1.1; regardless of what I do I cannot make
it work. Switching between users 100% of the time results in failure.

Here is what I have done:

Someone mentioned that after rebooting their system three times
(something like that) it started working albeit slow. I have rebooted my
system more than three times and it still doesn’t work.

Someone mentioned they switch users by locking the screen then from the
locked screen switch to a different user. What I have been doing is
clicking in the upper right corner, click on my name then click on
switch user. I have tried both methods with the same result, doesn’t
work. I can switch from ‘account A’ to ‘account B’ but I have not been
able to switch back to ‘account A’.

I have logged into ‘account A’ and then switched to ‘account B’. I can
logout of ‘account B’ and then login to ‘account B’ again, that works.
If I try to switch to ‘account A’ or logout of ‘account B’ and login to
‘account A’ I get locked out. I have the login screen for the two
accounts but cannot login to either. After a delay I am returned to the
login screen. At this point I did a CTRL-ALT-F4 to get a condole, which
worked. I logged into the console as ‘account A’, which worked. I then
did CTRL-ALT-F2 to return to windows and logged in to ‘account A’ which
sort of worked. I was logged in but things were not setup correct. For
instance I could not launch a terminal window; however, I could launch
Thunderbird. While in the console I did  (as someone suggested) ps aux |
grep , for the two accounts. I saved the output to a file
which I will attach (NOTE: for anonymity I will change the account names
to ‘account A’ and ‘account B’. Hopefully this will help someone better
understand the problem.


** Attachment added: "ps aux log"
   
https://bugs.launchpad.net/ubuntu/bionic/+source/gdm3/+bug/1766137/+attachment/514/+files/ps.log

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  Pr

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

2018-05-30 Thread Shawn Rutledge
I verified that the stylus does still work OK (using the Qt tablet
example which demonstrates pressure-sensitivity etc.)  So I think it's
probably OK to remove that stanza completely: there's probably no reason
to use wacom.drv for the touchscreen, just let it fall back to libinput
or evdev, whichever is installed.

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

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

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1000885] Re: ff crashes on xslt transformation when using oracle java plugin

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => New

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

Title:
  ff crashes on xslt transformation when using oracle java plugin

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

Bug description:
  Firefox crashes when performing an XSLT transformation when also
  loading any  stanza when the Oracle java plugin is used.

  = Environment =

  * oracle jre 6u31 (*any* oracle/sun java plugin)
  * Firefox (any version)
  * Ubuntu 10.04 LTS , 11.04, 11.10 or 12.04 LTS 32-bit
  * Web page containing xslt reproducer (attached)

  = Reproducible =
  100% (see attachment reproducer) but only with the Oracle Java plugin, not 
the iced tea plugins in the archive.

  = Workaround =
  Use the OpenJDK/IcedTea plugin - this is not a viable option due to the 
customers application certification.

  
  = Further Information =
  Reproducing on Ubuntu 12.04 LTS 32-bit with Firefox (11.0+build1-0ubuntu4)

  1. Download the two JRE's from:
  http://www.oracle.com/technetwork/java/javase/downloads/index.html

  2. Extract both Oracle JRE's:
  $ bash ./jre-6u31-linux-i586.bin
  $ tar -xvf jre-7u3-linux-i586.tar.gz
  $ sudo mv jre1.* /usr/lib/jvm

  3. Install the plugins into the alternatives system to switch easily:
  $ sudo update-alternatives --install 
/usr/lib/mozilla/plugins/libjavaplugin.so mozilla-javaplugin.so 
/usr/lib/jvm/jre1.6.0_31/lib/i386/libnpjp2.so 1059
  $ sudo update-alternatives --install 
/usr/lib/mozilla/plugins/libjavaplugin.so mozilla-javaplugin.so 
/usr/lib/jvm/jre1.7.0_03/lib/i386/libnpjp2.so 1058

  4. Unpack the xslt-crash-reproducer.zip
  $ unzip xslt-crash-reproducer.zip

  5. Open Firefox and check "about:plugins", open file:///path/to/test1.html  . 
Repeat with alternating   java plugins using alternatives to reconfiure which 
plugin is active:
  sudo update-alternatives --config mozilla-javaplugin.so

  
  = backtrace  =

  [Thread 0xa38a7b40 (LWP 2384) exited]
  nsPluginNativeWindowGtk2: call SetWindow with xid=0x3e00291
  --DOMWINDOW == 14 (0x811f4368) [serial = 14] [outer = 0x811e7e58] [url = 
about:blank]

  Program received signal SIGSEGV, Segmentation fault.
  0xb5fd9fbb in AssertActivityIsLegal ()
  at 
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/xpcom/base/nsTraceRefcntImpl.cpp:167
  167   
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/xpcom/base/nsTraceRefcntImpl.cpp:
 No such file or directory.
  (gdb) bt
  #0  0xb5fd9fbb in AssertActivityIsLegal ()
  at 
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/xpcom/base/nsTraceRefcntImpl.cpp:167
  #1  0xb5fdc8d2 in NS_LogDtor_P (aPtr=0x81405fe0, 
  aType=0xb6a941ab "txInstruction", aInstanceSize=8)
  at 
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/xpcom/base/nsTraceRefcntImpl.cpp:1148
  #2  0xb5232e0e in txInstruction::~txInstruction (this=0x81405fe0, 
  __in_chrg=)
  at 
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/content/xslt/src/xslt/txInstructions.h:64
  #3  0xb5237966 in txStartLREElement::~txStartLREElement (this=0x81405fe0, 
  __in_chrg=)
  at 
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/content/xslt/src/xslt/txInstructions.h:388
  #4  0xb52379a7 in txStartLREElement::~txStartLREElement (this=0x81405fe0, 
  __in_chrg=)
  at 
/tmp/buildd/firefox-12.0+build1/build-tree/mozilla/content/xslt/src/xslt/txInstructions.h:388
  #5  0xb5237187 in nsAutoPtr::~nsAutoPtr (this=0x81405fc4, 
  __in_chrg=) at ../../../../dist/include/nsAutoPtr.h:105
  #6  0xb5232e1c in txInstruction::~txInstruction (this=0x81405fc0, 
  __in_chrg=)

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

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


[Desktop-packages] [Bug 1009816] Re: Firefox comes to front when opening link via external program.

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Firefox comes to front when opening link via external program.

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

Bug description:
  Firefox 13 no longer remains in the background if opening a new tab
  from a different window, such as an email.

  Prior to the upgrade, the only time Firefox would rise to the
  foreground was if it were not already running.

  1) Ubuntu  12.04 LTS
  2) The version of the package you are using: firefox 
13.0+build1-0ubuntu0.12.04.1
  3) See above.
  4) See above.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 13.0+build1-0ubuntu0.12.04.1
  Uname: Linux 3.4.1-030401-generic i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bjwest 2280 F pulseaudio
  BuildID: 20120601173917
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfd20 irq 16'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,10438444,00100302'
 Controls  : 44
 Simple ctrls  : 21
  Channel: release
  Date: Wed Jun  6 22:35:45 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IpRoute:
   default via 192.168.1.1 dev eth1  proto static 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.119  metric 
1
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  Plugins:
   Skype Buttons for Kopete - /usr/lib/mozilla/plugins/skypebuttons.so (kopete)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: Unexpected character before close parenthesis @ 
[Profile]/extensions/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}/defaults/preferences/greasemonkey.js:4
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=13.0/20120601173917 (In use)
  RelatedPackageVersions: kopete 4:4.8.3-0ubuntu0.1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-28 (40 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd05/30/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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


[Desktop-packages] [Bug 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => New

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

Title:
  Firefox accepts dictionaries and spell check entries from every which
  spell check backend, leaving problems with defaults and the language
  selector enables this behavior

Status in Mozilla Firefox:
  New
Status in Hunspell:
  New
Status in myspell:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Confirmed

Bug description:
  I've been searching for the solution to this bug for a long time.

  Firefox's spell-check, despite my locale being en-US, sets itself to
  en-GB, en-ZA or something en_US, which isn't even correct.

  The problem, it seems, is that Firefox uses whatever spell-checking
  backends you have installed - aspell, myspell, and hunspell. The
  result is that Firefox chooses, en-GB as the default spell checker
  more-often than not. So I uninstalled myspell, hunspell, and a package
  called firefox-locale-en and now everything is correct - only one
  spell checker is installed in Firefox.

  The language selector, however, always prompts to reinstall these
  backends whenever it is loaded.

  This Firefox add-on can assist, it gives you a list of dictionaries
  installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary-
  switcher/

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

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


[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Treviño
** Tags removed: verification-done verification-done-bionic
** Tags added: regression-proposed verification-failed-bionic

** Tags removed: regression

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-05-30 Thread Christopher M. Penalver
Confirmed in Bionic. What happens in Windows is that it offers to send a
crash report to https://crashreport.libreoffice.org/, where one may then
input the crash ID in to review the stack trace.

** Tags added: bionic

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

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What was expected to happen is when LibreOffice crashes in Xenial, it
  logs a crash report to file against to errors.ubuntu.com.

  What happened instead is LibreOffice crashed but apport didn't log a
  crash file in /var/crash despite being enabled. Other programs that
  crash are picked up by apport so appears LO+apport issue.

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice* 
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

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

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

[Desktop-packages] [Bug 1774265] [NEW] Heavy flicker/flashing on external monitors using resolutions higher than 1920x1080

2018-05-30 Thread Beau Graham
Public bug reported:

Laptop model: Lenovo P51 20HH0011US
OS: Fresh install from USB ‘Ubuntu GNOME 16.04.4 LTS’
Monitors: Dell U2415b at 1920x1200, Asus PB278 at 2560x1440

Expected behavior: We install Ubuntu 16.04.4, plug in additional
monitors and those monitors work at the native resolution.

Actual behavior: This one is going to be hard to describe. But when we plug in 
a monitor, that monitor will flicker/flash extremely fast. With both HDMI and 
miniDP outputs. Most of the company has two external monitors and when we plug 
in a second monitor one or both of the external monitors flickered on 14 of the 
15 machines that we tested. We also tested with 20 or so monitors through our 
process of trying to isolate the problem. I will leave links of the video that 
we took of the issue. From the online preview you cannot tell what the problem 
is, but if you download the videos and play them with VLC or something locally, 
you should be able to see what we are talking about. 
https://drive.google.com/file/d/1oZQwIf8uaUEytQPQdihIy3eCpVRLe7-T/view?usp=sharing
https://drive.google.com/file/d/1eBrfXouqXhddobGHZijM_G4qNIKiLtaI/view?usp=sharing


We have noticed that if we change the resolution down to 1920x1080 the issue 
goes away. 

The monitors do not flicker on other models of Lenovo’s that we have tried. 
They also do not flicker with the same computer but running Windows or on any 
macbook that we have tried. The other weird issue is that once the monitor 
starts flickering, it stays flickering for about an hour even without a 
computer plugged into it or if we plug in a different computer that did not 
make that monitor flicker before it was plugged into a P51 running Ubuntu gnome 
16.04.4. 
Our current workaround is to install Ubuntu MATE 16.04.4 instead of gnome. The 
monitors work at native resolutions with MATE. 
Let us know if there is anything else we can do to help with this issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue May 29 15:24:31 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation Device [10de:13b6] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2251]
InstallationDate: Installed on 2018-05-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
MachineType: LENOVO 20HH0011US
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1UET41W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HH0011US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET41W(1.15):bd10/20/2017:svnLENOVO:pn20HH0011US:pvrThinkPadP51:rvnLENOVO:rn20HH0011US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P51
dmi.product.name: 20HH0011US
dmi.product.version: ThinkPad P51
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Heavy flicker/flashing on external monitors using resolutions higher
  than 1920x1080

Status in xorg package in Ubuntu:
  New

Bug description:
  Laptop model: Lenovo P51 20HH0011US
  OS: Fresh install from USB ‘Ubuntu GNOME 16.04.4 LTS’
  Monitors: Dell U2415b at 1920x1200, Asus PB278 at 2560x1440

  Expected behavior: We install Ubuntu 16.04.4, plug in additional
  monitors and those monitors work at the native 

[Desktop-packages] [Bug 1767206] Re: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian

2018-05-30 Thread Olivier Tilloy
Para desinstalar openoffice:

sudo apt remove openoffice-debian-menus

Para desinstalar libreoffice:

sudo apt remove "libreoffice*"

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  intentando sobreescribir `/usr/bin/soffice', que está también en el
  paquete openoffice-debian-menus 4.1.5-9789

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I have OpenOffice installed. Maybe this is the origin of the problem.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 16:12:28 2018
  ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también 
en el paquete openoffice-debian-menus 4.1.5-9789
  InstallationDate: Installed on 2018-03-30 (27 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.1.5-9789
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

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

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


[Desktop-packages] [Bug 1772469] Re: Pressing Ctrl on the input line in Calc removes all formatting

2018-05-30 Thread Olivier Tilloy
Thanks!

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

Title:
  Pressing Ctrl on the input line in Calc removes all formatting

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  In this scenario, I have a Calc cell with formatted text (italics,
  underlining, boldface, font color etc.). Now if I want to change the
  formatting of a part of that same cell afterwards, I would naturally
  select the cell, go to the input line, select the part I want to
  change and press the appropriate keyboard shortcut, e.g. Ctrl-I for
  italics. Now the problem is that if the cursor is on the input line,
  pressing Ctrl removes all formatting from that cell. Doing the same in
  the table view does not have the same effect, so I can change the
  formatting of text with keyboard shortcuts as much as I want in the
  table view. The expected behavior would be for the cell to keep its
  formatting even if I try to use keyboard shortcuts on the input line.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-calc:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-calc 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 18:12:06 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.utf-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

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

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


[Desktop-packages] [Bug 1772414] Re: Justifying Syriac text creates clutter in LibreOffice Writer

2018-05-30 Thread Olivier Tilloy
Thanks!

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

Title:
  Justifying Syriac text creates clutter in LibreOffice Writer

Status in libreoffice package in Ubuntu:
  Confirmed
Status in xfonts-scalable-nonfree package in Ubuntu:
  New

Bug description:
  Justifying a paragraph in LibreOffice Writer with text written in the
  Syriac script (Unicode block U+0700-U+074F) creates graphic clutter
  between every word. See the attached screenshot where the first
  paragraph is justified and the second is right-aligned. The second
  paragraph looks as it should, whereas the first paragraph shows a
  small line added at the end of each word. If you zoom in or out, some
  of the lines may disappear, but when you create a PDF, they are all
  there.

  The same problem occurs with nearly all the Syriac fonts I have tried,
  including Serto Batnan, Estrangelo Antioch, East Syriac Ctesiphon and
  Serto Urhoy (all part of the ttf-xfree86-nonfree-syriac package). For
  the last two, the clutter is not visible on screen but shows up if you
  create a PDF. With East Syriac Adiabene, the problem doesn't seem to
  occur. I have attached a screenshot, a PDF and the document used to
  create them.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 13:26:09 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

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

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


[Desktop-packages] [Bug 1774261] [NEW] package nvidia-340 (not installed) failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-kernel

2018-05-30 Thread Tymek
Public bug reported:

Cannot install package via terminal

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 30 21:32:40 2018
ErrorMessage: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który 
istnieje także w pakiecie nvidia-kernel-common-390 390.48-0ubuntu3
InstallationDate: Installed on 2018-05-28 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: próba 
nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie 
nvidia-kernel-common-390 390.48-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: próba
  nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w
  pakiecie nvidia-kernel-common-390 390.48-0ubuntu3

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

Bug description:
  Cannot install package via terminal

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 21:32:40 2018
  ErrorMessage: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który 
istnieje także w pakiecie nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2018-05-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: próba 
nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie 
nvidia-kernel-common-390 390.48-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 47751] Re: Dos problem with marquee tag

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Dos problem with marquee tag

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix

Bug description:
  Hi,
  as also reported on securityfocus at 
http://www.securityfocus.com/archive/1/435373/30/0/threaded using this kind of 
html page:

  

  

  Credit to n00b..

  

  

  

  
  
  
  
  
  
  
  
  
  
  

  

  

  Firefox uses all the cpu resources and it becames not usable.
  I've tested it in ubuntu dapper (upgraded from flight 6) on amd64 (firefox is 
at version 1.5.0.3)

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

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


[Desktop-packages] [Bug 24398] Re: Form field focus should not be set if user has begun entering text.

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Form field focus should not be set if user has begun entering text.

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

Bug description:
  After loading a page containing a form, Firefox automatically focuses the 
first
  input field in the tab order.  It should not do this if the user has already
  begun entering data into the form.  Not only is the current behavior annoying,
  but it is a potential security issue.  I have often typed passwords into
  plaintext fields because Firefox changed the field focus after a slow page 
load.

  If the event handling isn't too messy, it should also not change the input 
focus
  if the user is typing something in the address bar or search bar.

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

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


[Desktop-packages] [Bug 300080] Re: "print selection only" option cuts multi-page text

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  "print selection only" option cuts multi-page text

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

Bug description:
  I tried selecting some text from a webpage that I wanted to print.
  The text was several pages long.  When I printed it, I noticed that
  the last line of the text was cut horizontally, and the bottom part
  was on the next page, thus making that line very difficult to read.

  I checked with just printing to a file (both postscript and pdf), and
  the same thing happens, and at the same proportions (the same amount
  of the line is cut off, and pushed to the next page)

  Obviously, I think the line of text shouldn't be cut at all.  It
  should be either squeezed into the current page (The "Ignore scaling
  and shrink page to fit width" option is selected, so maybe that could
  justify this?) or, just push the line to the next page.

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

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


[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV

2018-05-30 Thread Alan Pope 🍺🐧🐱 🦄
Just had this again.

https://errors.ubuntu.com/oops/0c692c82-643d-11e8-b7b3-fa163e8d4bab

Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'

Is the error I see in the xorg crash reports. I

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

Title:
  Xorg crashed with SIGSEGV

Status in snapd:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  Installed a snap, immediately after I installed it, the machine froze
  and then x crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 30 14:15:35 2018
  Disassembly: => 0x7f6b0008:   Cannot access memory at address 
0x7f6b0008
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541]
  InstallationDate: Installed on 2018-02-13 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook P65_P67RGRERA
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7f6b0008:Cannot access memory at address 
0x7f6b0008
   PC (0x7f6b0008) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Mar 29 14:49:09 2018
  xserver.configfile: default
  xserver.errors:
   client bug: Invalid path /dev/input/event7
   systemd-logind: failed to take device /dev/input/event19: No such device
   client bug: Invalid path /dev/input/

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Sergei
I don't think you should release this because this produces more critical bug. 
This bug has some kind of workaround (cancel button), but I will have to 
disable updates if there is an upcoming update that will totally break an 
ability to switch users without any workaround. 
I believe I'm not the only one who has multiple users on my PC.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 39136] Re: firefox should render unrecognized text/* as text/plain

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  firefox should render unrecognized text/* as text/plain

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

Bug description:
  The current program suggested to view certain filetypes (e.g. text/x
  -debian-source-package as send when visiting
  http://librarian.launchpad.net/1788684/usplash_0.1-33.dsc) is less.
  Perhaps gedit would be a more sensible choice?

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

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


[Desktop-packages] [Bug 45836] Re: Scrolling in the view-source window

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Scrolling in the view-source window

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

Bug description:
  Using the latest Dapper (05/21/06), I have problems with the view-
  source window. When the source window is maximized and I want to
  select text by mouse going from right to left the window does not
  scroll when hitting the left edge. Going from left to right works
  well. Also Unmaximized window works in both directions.

  To recreate:

  1) Open a view-source window by View > Page Source.
  2) Maximize the view-source window.
  3) Check that there is a line wider then the actual view-source window and go 
to the end of this line.
  4) Select text from the end of this line going far left.
  5) Window does not scroll.

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

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


[Desktop-packages] [Bug 32891] Re: Improve support for non-gnome Input methods

2018-05-30 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Improve support for non-gnome Input methods

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

Bug description:
  Firefox text entry widgets do not support input methods like other
  gnome desktop text entry widgets.

  To reproduce: find a webpage with a form with a text entry widget,
  right click on it, note how the input methods submenu is not
  displayed.

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

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


[Desktop-packages] [Bug 1614769] Re: apparmor profile is incomplete

2018-05-30 Thread Jerry Quinn
My kern.log is spammed by them too.
Ubuntu 16.04 x86_64

evince 3.18.2-1ubuntu4.3


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

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

Title:
  apparmor profile is incomplete

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I get a ton of these

  [1696380.664673] audit: type=1400 audit(1471560429.285:54874):
  apparmor="DENIED" operation="open" profile="/usr/bin/evince"
  name="/n/home/tjaalton/.local/share/gvfs-metadata/home" pid=27496
  comm="pool" requested_mask="r" denied_mask="r" fsuid=187661
  ouid=187661

  filling my syslog

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

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


[Desktop-packages] [Bug 1774246] Re: package libatk-adaptor (not installed) failed to install/upgrade: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from other ins

2018-05-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libatk-adaptor (not installed) failed to install/upgrade:
  trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which
  is different from other instances of package libatk-adaptor:i386

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  xubuntu
  installed Steam
  installed System Shock 2
  tried to start it from Steam; did not work.
  installed wine1.6
  tried to run autorun within the .local/share/Steam/steamapps/common/SS2/bin; 
error missing packages
  installed :sudo apt install libatk-adaptor:i386 libgail-common:i386

  Error install :

  Preparing to unpack .../libatk-adaptor_2.18.1-2ubuntu1_i386.deb ...
  Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
   trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  Processing triggers for libc-bin (2.23-0ubuntu10) ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libatk-adaptor (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 20:24:01 2018
  DuplicateSignature:
   package:libatk-adaptor:(not installed)
   Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  ErrorMessage: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', 
which is different from other instances of package libatk-adaptor:i386
  InstallationDate: Installed on 2017-08-16 (286 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: at-spi2-atk
  Title: package libatk-adaptor (not installed) failed to install/upgrade: 
trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

2018-05-30 Thread Harsh Gupta
I have this issue with kernel 4.15.0.22

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

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

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

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


[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

2018-05-30 Thread Harsh Gupta
Update to comment#35: Upgrading to the latest nvidia drivers with
4.15.0.22 fixed it.

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

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

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

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


[Desktop-packages] [Bug 1774246] [NEW] package libatk-adaptor (not installed) failed to install/upgrade: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from other i

2018-05-30 Thread Robert
Public bug reported:

xubuntu
installed Steam
installed System Shock 2
tried to start it from Steam; did not work.
installed wine1.6
tried to run autorun within the .local/share/Steam/steamapps/common/SS2/bin; 
error missing packages
installed :sudo apt install libatk-adaptor:i386 libgail-common:i386

Error install :

Preparing to unpack .../libatk-adaptor_2.18.1-2ubuntu1_i386.deb ...
Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
 trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
Processing triggers for libc-bin (2.23-0ubuntu10) ...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libatk-adaptor (not installed)
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
Date: Wed May 30 20:24:01 2018
DuplicateSignature:
 package:libatk-adaptor:(not installed)
 Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
ErrorMessage: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', 
which is different from other instances of package libatk-adaptor:i386
InstallationDate: Installed on 2017-08-16 (286 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: at-spi2-atk
Title: package libatk-adaptor (not installed) failed to install/upgrade: trying 
to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different 
from other instances of package libatk-adaptor:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: at-spi2-atk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

** Summary changed:

- installed wine; after start program needed to install packages; it crashed: 
package libatk-adaptor (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from 
other instances of package libatk-adaptor:i386
+ package libatk-adaptor (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from 
other instances of package libatk-adaptor:i386

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

Title:
  package libatk-adaptor (not installed) failed to install/upgrade:
  trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which
  is different from other instances of package libatk-adaptor:i386

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  xubuntu
  installed Steam
  installed System Shock 2
  tried to start it from Steam; did not work.
  installed wine1.6
  tried to run autorun within the .local/share/Steam/steamapps/common/SS2/bin; 
error missing packages
  installed :sudo apt install libatk-adaptor:i386 libgail-common:i386

  Error install :

  Preparing to unpack .../libatk-adaptor_2.18.1-2ubuntu1_i386.deb ...
  Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
   trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  Processing triggers for libc-bin (2.23-0ubuntu10) ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libatk-adaptor (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 20:24:01 2018
  DuplicateSignature:
   package:libatk-adaptor:(not installed)
   Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  ErrorMessage: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', 
which is different from other instances of package libatk-adaptor:i386
  InstallationDate: Installed on 2017-08-16 (286 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: at-spi2-atk
  Title: package libatk-adaptor (not installed) failed to install/upgrade: 
tr

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Treviño
I think the issue is getting is there but maybe different from the one
originating this bug, so maybe to be handled in a different one...

So please, test this:

 1. Create another user
 2. Login with your user (or the other, as you wish)
 3. Lock the session -> Switch to other user from lockscreen
 4. Once back on GDM, select another user... Then you can login and redo what
said in 3. or just go back.
 5. From GDM, again try to unlock the 1st user, it fails.

Also `ps aux | grep ` shows running processes for
that session, while gdm seems to try to initialize a new one.

Anyway, while it's true this could be a regression of this change, I think it 
might be still better to release the version we have in proposed as this kind 
of issue can be handled in a different bug.
In any case I'm looking at it right now.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1767206] Re: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian

2018-05-30 Thread guiyeka
Por favor alguien me puede indicar como desinstalo en Ubuntu Libre
office o opend office. Gracias

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  intentando sobreescribir `/usr/bin/soffice', que está también en el
  paquete openoffice-debian-menus 4.1.5-9789

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I have OpenOffice installed. Maybe this is the origin of the problem.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Apr 26 16:12:28 2018
  ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también 
en el paquete openoffice-debian-menus 4.1.5-9789
  InstallationDate: Installed on 2018-03-30 (27 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.1.5-9789
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

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

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


[Desktop-packages] [Bug 1774244] Re: Rotated Arabic text is displaced in PDF when substitute glyphs are used

2018-05-30 Thread Miikka-Markus Alhonen
This is the ODT document used to create both the PDF and the screenshot.

** Attachment added: "Displaced rotated Arabic.odt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1774244/+attachment/5146583/+files/Displaced%20rotated%20Arabic.odt

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

Title:
  Rotated Arabic text is displaced in PDF when substitute glyphs are
  used

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In this example, I created a document with a few Arabic-script
  characters (U+08A2, U+08A3 & U+08A4), which were quite recently added
  to Unicode for various Arabic-script African languages such as
  Fulfulde. The font I had used in the rest of the document was DejaVu
  Sans, so I used that font setting even for these characters. In
  reality, these glyphs are not found in DejaVu Sans but had to be
  substituted from another font, in my case Scheherazade (from fonts-
  sil-scheherazade, available through packages.sil.org). After rotating
  the letters by 90 degrees, everything looked fine on the screen but
  when I created a PDF, everything was displaced about one inch upwards
  and one inch to the left. See the attached screenshot, where
  everything looks fine, and the PDF where all the letters are
  displaced.

  If I change the font setting for this text to Scheherazade, everything
  looks fine even in a generated PDF. So apparently LibreOffice gets
  confused by the different font metrics of the two fonts, the one
  selected by the user and the one used as the real source for the
  glyphs.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 17:36:37 2018
  InstallationDate: Installed on 2017-02-13 (471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (205 days ago)

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

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


[Desktop-packages] [Bug 1774244] Re: Rotated Arabic text is displaced in PDF when substitute glyphs are used

2018-05-30 Thread Miikka-Markus Alhonen
Here's a screenshot where everything looks fine, unlike the PDF.

** Attachment added: "Screenshot displaced Arabic.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1774244/+attachment/5146582/+files/Screenshot%20displaced%20Arabic.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/1774244

Title:
  Rotated Arabic text is displaced in PDF when substitute glyphs are
  used

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In this example, I created a document with a few Arabic-script
  characters (U+08A2, U+08A3 & U+08A4), which were quite recently added
  to Unicode for various Arabic-script African languages such as
  Fulfulde. The font I had used in the rest of the document was DejaVu
  Sans, so I used that font setting even for these characters. In
  reality, these glyphs are not found in DejaVu Sans but had to be
  substituted from another font, in my case Scheherazade (from fonts-
  sil-scheherazade, available through packages.sil.org). After rotating
  the letters by 90 degrees, everything looked fine on the screen but
  when I created a PDF, everything was displaced about one inch upwards
  and one inch to the left. See the attached screenshot, where
  everything looks fine, and the PDF where all the letters are
  displaced.

  If I change the font setting for this text to Scheherazade, everything
  looks fine even in a generated PDF. So apparently LibreOffice gets
  confused by the different font metrics of the two fonts, the one
  selected by the user and the one used as the real source for the
  glyphs.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 17:36:37 2018
  InstallationDate: Installed on 2017-02-13 (471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (205 days ago)

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

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


[Desktop-packages] [Bug 1774244] [NEW] Rotated Arabic text is displaced in PDF when substitute glyphs are used

2018-05-30 Thread Miikka-Markus Alhonen
Public bug reported:

In this example, I created a document with a few Arabic-script
characters (U+08A2, U+08A3 & U+08A4), which were quite recently added to
Unicode for various Arabic-script African languages such as Fulfulde.
The font I had used in the rest of the document was DejaVu Sans, so I
used that font setting even for these characters. In reality, these
glyphs are not found in DejaVu Sans but had to be substituted from
another font, in my case Scheherazade (from fonts-sil-scheherazade,
available through packages.sil.org). After rotating the letters by 90
degrees, everything looked fine on the screen but when I created a PDF,
everything was displaced about one inch upwards and one inch to the
left. See the attached screenshot, where everything looks fine, and the
PDF where all the letters are displaced.

If I change the font setting for this text to Scheherazade, everything
looks fine even in a generated PDF. So apparently LibreOffice gets
confused by the different font metrics of the two fonts, the one
selected by the user and the one used as the real source for the glyphs.

Description:Ubuntu 17.10
Release:17.10

libreoffice-writer:
  Installed: 1:5.4.6-0ubuntu0.17.10.1
  Candidate: 1:5.4.6-0ubuntu0.17.10.1
  Version table:
 *** 1:5.4.6-0ubuntu0.17.10.1 500
500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:5.4.5-0ubuntu0.17.10.5 500
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
 1:5.4.1-0ubuntu1 500
500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 17:36:37 2018
InstallationDate: Installed on 2017-02-13 (471 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to artful on 2017-11-05 (205 days ago)

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


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

** Attachment added: "Example displaced Arabic.pdf"
   
https://bugs.launchpad.net/bugs/1774244/+attachment/5146579/+files/Example%20displaced%20Arabic.pdf

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

Title:
  Rotated Arabic text is displaced in PDF when substitute glyphs are
  used

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In this example, I created a document with a few Arabic-script
  characters (U+08A2, U+08A3 & U+08A4), which were quite recently added
  to Unicode for various Arabic-script African languages such as
  Fulfulde. The font I had used in the rest of the document was DejaVu
  Sans, so I used that font setting even for these characters. In
  reality, these glyphs are not found in DejaVu Sans but had to be
  substituted from another font, in my case Scheherazade (from fonts-
  sil-scheherazade, available through packages.sil.org). After rotating
  the letters by 90 degrees, everything looked fine on the screen but
  when I created a PDF, everything was displaced about one inch upwards
  and one inch to the left. See the attached screenshot, where
  everything looks fine, and the PDF where all the letters are
  displaced.

  If I change the font setting for this text to Scheherazade, everything
  looks fine even in a generated PDF. So apparently LibreOffice gets
  confused by the different font metrics of the two fonts, the one
  selected by the user and the one used as the real source for the
  glyphs.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 17:36:37 2018
  InstallationDate: Installed on 2017-02-13 (471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Re

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

2018-05-30 Thread Andreas Hasenack
Reproduced on trusty. In xenial the sleed.d packagekit hook is gone.

sudo apt install pm-utils packagekit

I hacked /usr/lib/pm-utils/pm-functions to log which hook it was
running, and forced a suspend with "pm-suspend". In my case I got
multiple runs of 98video-quirk-db-handler right after the incorrect
packagekit directory was hit:

hook var is
base is 99video
runing hook /usr/lib/pm-utils/sleep.d/99video
hook var is /usr/lib/pm-utils/sleep.d/99video
base is 98video-quirk-db-handler
runing hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
hook var is /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
base is 95packagekit
runing hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
hook var is /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
base is 95led
runing hook /usr/lib/pm-utils/sleep.d/95led
hook var is /usr/lib/pm-utils/sleep.d/95led
base is 95hdparm-apm
...

With the proposed fix, the packagekit hook isn't run, and we also don't
get double runs of other hooks.

So the fix could be what is proposed, or/and moving the packagekit hook
to the right place.

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

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

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1677411] Re: package software-center (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package software-center (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  OS : Elementary OS Loki

  Problem: installation error

  Module "Elementary" not found

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   software-center: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Mar 30 07:10:22 2017
  DuplicateSignature:
   package:software-center:(not installed)
   Purging configuration files for software-center (16.01+16.04.20160420) ...
   rmdir: failed to remove '/var/cache/software-center/xapian/': No such file 
or directory
   dpkg: error processing package software-center (--purge):
subprocess installed post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-02-03 (54 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: software-center
  Title: package software-center (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1677411] Re: package software-center (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-05-30 Thread Apport retracing service
** Tags added: xenial

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

Title:
  package software-center (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  OS : Elementary OS Loki

  Problem: installation error

  Module "Elementary" not found

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   software-center: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Mar 30 07:10:22 2017
  DuplicateSignature:
   package:software-center:(not installed)
   Purging configuration files for software-center (16.01+16.04.20160420) ...
   rmdir: failed to remove '/var/cache/software-center/xapian/': No such file 
or directory
   dpkg: error processing package software-center (--purge):
subprocess installed post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-02-03 (54 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: software-center
  Title: package software-center (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-30 Thread Heikki Moisander
I had similar experience yesterday after installing 3.28.2 and I reported
that it does not work. But after couple of boots I have been testing every
now and then maybe some 15 times and every time it has logged in - very
slowly but success anyway. To me that is quite clear that any kind of
success is better that need to boot every time. It is not about speed, but
we can not accept the situation user get frozen screen every time login in
after someone else. So if anything better is not available please take this
into production.


ke 30. toukokuuta 2018 klo 20.11 KenWilson <1766...@bugs.launchpad.net>
kirjoitti:

> I installed package 3.28.2-0ubuntu1.1 and performed the testing again. I
> restricted testing to only switching between accounts. Same result, it
> did not work.
>
> Listing... Done
> gdm3/bionic-proposed,now 3.28.2-0ubuntu1.1 amd64 [installed]
> gdm3/bionic 3.28.0-0ubuntu1 amd64
>
> After installation I rebooted my system. I successfully logged into
> “account A”. I successfully switched to “account B”. I then tried to
> switch back to “account A” but was not successful. I am stuck at the
> login screen. I cannot login to either “account A” or “account B”. I had
> to reboot to gain control of my system.
>
> Ken
>
>
> On 05/30/2018 09:06 AM, Iain Lane wrote:
> > On Wed, May 30, 2018 at 03:45:17PM -, KenWilson wrote:
> >> All,
> >> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect
> >> password issue; however, it creates a new issue. As such I don’t think
> >> this update should be released.
> > That verison is superseded by 3.28.2-0ubuntu1.1. Please try this one.
> >
>
> --
> *Ken Wilson*
> lake
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
>   [regression] Password accepted but login fails (blank purple screen
>   and mouse pointer only)
>
> Status in gdm:
>   Fix Released
> Status in Release Notes for Ubuntu:
>   Fix Released
> Status in gdm3 package in Ubuntu:
>   Fix Released
> Status in gnome-shell package in Ubuntu:
>   Invalid
> Status in gdm3 source package in Bionic:
>   Fix Committed
> Status in gnome-shell source package in Bionic:
>   Invalid
>
> Bug description:
>   [ Description ]
>
>   Due to a refcounting bug, a GDBusConnection was getting disposed when
>   it was still required. The symptom of this was that you couldn't log
>   in on the second attempt if you'd got your password wrong on the first
>   attempt. All you'd see is a blank purple screen and mouse pointer
>   only.
>
>   [ Test case ]
>
>   1. Boot to GDM
>   2. Click your username
>   3. Type the wrong password a couple of times, pressing enter after each
> time
>   4. Type the right password
>
>   If the bug is happening, after 4. the system hangs at a blank screen
>   with the mouse cursor. If you then switch to a VT or otherwise connect
>   to the machine, you can examine the journal and you'll see a
>   G_IS_DBUS_CONNECTION failure.
>
>   [ Fix ]
>
>   Marco and I worked upstream on this fix. We found out that there was a
>   problem like this-
>
>   The GdmClient has a shared GDBusConnection for its operations. The
>   first time  someone calls for it, it is created and stored in the
>   object's private structure. Subsequent calls return *a new reference*
>   to this same object. It turned out that the asynchronous method to get
>   the connection was accidentally unreferencing its object before giving
>   it to the caller if it was returning an already-existing connection.
>
>   For this to work properly, we need to nullify the pointer we stored
>   when the connection goes away, so we know when to make a new one.
>   There were some cases where we didn't add the weak references required
>   to do that. Those are also fixed.
>
>   [ Regression potential ]
>
>   Now we share connections more than we did before. We also more
>   carefully track when to clear our object. If we got this wrong, we
>   might end up leaking the connection or dropping it in even more cases.
>
>   [ Original report ]
>
>   WORKAROUND: After typing an incorrect password, click Cancel, then
>   click your name, then enter your password again.
>
>   ---
>
>   Trying to log into my session (Gnome, Xorg), if I enter the wrong
>   password before entering it correctly, the session doesn't load and I
>   get a purple screen, a mouse cursor, and an invisible but clickable
>   menu in the top right. If I enter it correctly the first time, there
>   is no problem.
>
>   I've replicated this from a fresh boot, after logging out and after
>   'sudo service gdm restart' from the Ctrl-Alt-F4 console.
>
>   This is a fresh install, and didn't occur when I was using a previous
>   install of 18.04 (until Friday).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
>   Uname: Linux 4.15.0-15-generic x86_64
>   ApportVersion

[Desktop-packages] [Bug 1774197] Re: package software-center (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-05-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1677411 ***
https://bugs.launchpad.net/bugs/1677411

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1677411, so 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.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1677411
   package software-center (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1

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

Title:
  package software-center (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in software-center package in Ubuntu:
  New

Bug description:
  Please see atttach report

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 19:20:19 2018
  DuplicateSignature:
   package:software-center:(not installed)
   Purging configuration files for software-center (16.01+16.04.20160420) ...
   rmdir: failed to remove '/var/cache/software-center/xapian/': No such file 
or directory
   dpkg: error processing package software-center (--purge):
subprocess installed post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-08-08 (659 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: software-center
  Title: package software-center (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (497 days ago)

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

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


[Desktop-packages] [Bug 1774197] Re: package software-center (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-05-30 Thread Emily Ratliff
*** This bug is a duplicate of bug 1677411 ***
https://bugs.launchpad.net/bugs/1677411

** Information type changed from Private Security to Public

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

Title:
  package software-center (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in software-center package in Ubuntu:
  New

Bug description:
  Please see atttach report

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 19:20:19 2018
  DuplicateSignature:
   package:software-center:(not installed)
   Purging configuration files for software-center (16.01+16.04.20160420) ...
   rmdir: failed to remove '/var/cache/software-center/xapian/': No such file 
or directory
   dpkg: error processing package software-center (--purge):
subprocess installed post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-08-08 (659 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: software-center
  Title: package software-center (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (497 days ago)

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

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


[Desktop-packages] [Bug 1774243] [NEW] Rotated Arabic text is displaced in PDF when substitute glyphs are used

2018-05-30 Thread Miikka-Markus Alhonen
Public bug reported:

In this example, I created a document with a few Arabic-script
characters (U+08A2, U+08A3 & U+08A4), which were quite recently added to
Unicode for various Arabic-script African languages such as Fulfulde.
The font I had used in the rest of the document was DejaVu Sans, so I
used that font setting even for these characters. In reality, these
glyphs are not found in DejaVu Sans but had to be substituted from
another font, in my case Scheherazade (from fonts-sil-scheherazade,
available through packages.sil.org). After rotating the letters by 90
degrees, everything looked fine on the screen but when I created a PDF,
everything was displaced about one inch upwards and one inch to the
left. See the attached screenshot, where everything looks fine, and the
PDF where all the letters are displaced.

If I change the font setting for this text to Scheherazade, everything
looks fine even in a generated PDF. So apparently LibreOffice gets
confused by the different font metrics of the two fonts, the one
selected by the user and the one used as the real source for the glyphs.

Description:Ubuntu 17.10
Release:17.10

libreoffice-writer:
  Installed: 1:5.4.6-0ubuntu0.17.10.1
  Candidate: 1:5.4.6-0ubuntu0.17.10.1
  Version table:
 *** 1:5.4.6-0ubuntu0.17.10.1 500
500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:5.4.5-0ubuntu0.17.10.5 500
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
 1:5.4.1-0ubuntu1 500
500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 17:36:37 2018
InstallationDate: Installed on 2017-02-13 (471 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to artful on 2017-11-05 (205 days ago)

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


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

** Attachment added: "Example displaced Arabic.pdf"
   
https://bugs.launchpad.net/bugs/1774243/+attachment/5146576/+files/Example%20displaced%20Arabic.pdf

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

Title:
  Rotated Arabic text is displaced in PDF when substitute glyphs are
  used

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In this example, I created a document with a few Arabic-script
  characters (U+08A2, U+08A3 & U+08A4), which were quite recently added
  to Unicode for various Arabic-script African languages such as
  Fulfulde. The font I had used in the rest of the document was DejaVu
  Sans, so I used that font setting even for these characters. In
  reality, these glyphs are not found in DejaVu Sans but had to be
  substituted from another font, in my case Scheherazade (from fonts-
  sil-scheherazade, available through packages.sil.org). After rotating
  the letters by 90 degrees, everything looked fine on the screen but
  when I created a PDF, everything was displaced about one inch upwards
  and one inch to the left. See the attached screenshot, where
  everything looks fine, and the PDF where all the letters are
  displaced.

  If I change the font setting for this text to Scheherazade, everything
  looks fine even in a generated PDF. So apparently LibreOffice gets
  confused by the different font metrics of the two fonts, the one
  selected by the user and the one used as the real source for the
  glyphs.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 17:36:37 2018
  InstallationDate: Installed on 2017-02-13 (471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Re

  1   2   3   >