date:20180802

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

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

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

Title:
  cups sees Xerox Phaser 3330 but doesnot print

Status in cups package in Ubuntu:
  Expired

Bug description:
  Hey,

  I have Xerox Phaser 3330 with installed official drivers.Cups sees
  this usb printer, sends the job and says that the job is completed. In
  fact nothing happens.

  I connected to this printer through the network, it works. But
  unfortunately i need the usb connection.

  Could you help me with this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  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: Unity:Unity7:ubuntu
  Date: Fri Jun  1 16:31:14 2018
  InstallationDate: Installed on 2017-09-08 (266 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: device for Xerox-Phaser-3330: 
usb://Xerox/Phaser%203330?serial=3385783140=1
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Xerox-Phaser-3330: Xerox Tuscany, 1.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-05-22 (10 days ago)
  dmi.bios.date: 11/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1706
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1706:bd11/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1774890] Re: Stopping typing every second when prompted for a password.

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

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

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

Title:
  Stopping typing every second when prompted for a password.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Stopping typing every second when prompted for a password.

  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
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  3 16:57:33 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-05-14 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20B7A0S4BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=120c671a-235c-462b-966e-ba1fe93b341f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7A0S4BR
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20B7A0S4BR:pvrThinkPadT440:rvnLENOVO:rn20B7A0S4BR:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440
  dmi.product.name: 20B7A0S4BR
  dmi.product.version: ThinkPad T440
  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 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/1774890/+subscriptions

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

[Desktop-packages] [Bug 1774784] Re: tras escribir la constraseña de usuario, gnome-shell, no arranca usando el perfil Community Theme.

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

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

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

Title:
  tras escribir la constraseña de usuario, gnome-shell, no arranca
  usando el perfil Community Theme.

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  tras escribir la constraseña de usuario, gnome-shell, no arranca
  usando el perfil Community Theme.

  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  2 16:26:25 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (34 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/1774784/+subscriptions

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

[Desktop-packages] [Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_wi

** Also affects: gnome-shell (Ubuntu Bionic)
   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/1422253

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message("assertion
  failed: (window->display->focus_window != window)") from
  g_assertion_message_expr() from meta_window_unmanage() from
  handle_other_xevent()

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  New

Bug description:
  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15

  [ Description ]

  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic
  was in process of installing programs (downloads were complete &
  actual install was in progress)

  [ Test case ]

  1. Run one of the reproducer test (python or gjs version) available at:
 https://gitlab.gnome.org/GNOME/mutter/issues/15
  2. when that close, g-s should not crash

  [ Regression potential ]

  Possible break for windows that have the grab but are not the active
  ones.

  
  

  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

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

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

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

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/130
  https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339

  ---

  [ Description ]

  This happened while I was away from the computer. By the timing it
  should have been well after the time it should have gone *into*
  displaysleep, and was also about 45min before I returned, so certainly
  wasn't the wake-up process either.

  What I observed when I did return: My 4K monitor didn't wake up
  (that's a known problem with this monitor, Dell P2715Q), the second
  monitor (Dell U2711) did wake up, showing the login screen.

  So although I've considered my Dell 4K problem a problem with waking
  up, I wonder if it might be actually a problem with it apparently
  going away completely after a longer displaysleep (it's usually fine
  if I just do a short sleep of a minute or two).

  Another possibility is the cat stepped on the keyboard and thus
  triggered an attempted display-wake. But that would actually be out of
  character (for the cat).

  Either way is a bug because the session should survive monitor
  shenanigans... :-)

  In some not known conditions, g-s might crash while computing global
  resolution for monitors.

  [ Test case ]

  There's really no test case for this bug, a part that g-s should not
  crash with this stacktrace. Unforuntaltey this is quite hard to
  reproduce, it might happen while resetting the crtc when setting up a
  (new) monitor or at wake up, but so far nobody has reported a way for
  reproducing this.

  [ Regression potential ]

  Global scale for attached monitors could not be properly computed, and
  thus if attaching an HiDPI device, the UI could not be scaled properly

  ---

  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct 14 15:39:50 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-30 (75 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fae20ab44a0 : 
mov0x8(%rdi),%eax
   PC (0x7fae20ab44a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_mode_get_resolution () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_calculate_mode_scale () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_update_logical_state_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_rebuild_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_xrandr_handle_xevent () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
  UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1767956] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_b

** Also affects: gnome-shell (Ubuntu Bionic)
   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/1767956

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from
  meta_monitor_manager_kms_initable_init() from g_initable_new_valist()
  from g_initable_new() from meta_backend_create_monitor_manager()

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  New

Bug description:
  [ Description ]

  GNome shell crashes after Xorg logging

  [ Test case ]

  From GDM login in a GNOME Ubuntu session (so Xorg).
  It should start with no issues

  [ Regression potential ]

  Nothing know, this is a safe NULL check, so no crash will happen.
  It's not granted that the session will work properly aftewards though.

  --

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

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

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

[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

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

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

** Also affects: gnome-shell (Ubuntu Bionic)
   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/1754949

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

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

Bug description:
  [ Description ]

  GNome shell crashes after Xorg loggin

  [ Test case ]

  From GDM login in a GNOME Ubuntu session (so Xorg).
  It should start with no issues

  [ Regression potential ]

  We were deferencing a NULL pointer while outputting an error.
  This is pretty safe. Although the session might still not run properly as per 
a driver issue to be addressed in linux package.

  ---

  https://gitlab.gnome.org/GNOME/mutter/issues/70
  https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665

  https://salsa.debian.org/gnome-team/mutter/merge_requests/6

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180

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

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

Title:
  gnome-control-center does not respond after we set the resolution
  320x180

Status in gnome-control-center:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Bionic:
  New

Bug description:
  [ Description ]

  gnome-control-center does not respond after we set the resolution
  320x180

  
  [ Test case ]

  Open gnome-control-center -> Displays
  Low resolutions (such as 320x180) should not be listed.

  Trying to set the lowst listed resolution, should just apply without
  breaking gnome-control-center.

  [ Regression potential ]

  No alternative resolutions are shown in g-c-c

  ---

  Expected results: shows the countdown dialog
  Actual results: the countdown dialog doesn't show. Only mouse cursor can 
move. All of the buttons/icons don't respond.

  Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log",
  the count-down dialog shows up!

  Notebook: Dell XPS 13

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

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

[Desktop-packages] [Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal

** Also affects: gnome-shell (Ubuntu Bionic)
   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/1784398

Title:
  Changing monitor settings crashes on
  meta_window_wayland_move_resize_internal

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  New

Bug description:
  [ Description ]

  Under wayland adding a monitor in cloned mode might crash g-s

  See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248

  [ Test case ]

  Open an Ubuntu session on Wayland:

  1. Attach another monitor
  2. Mark as cloned display
  3. Gnome-shell should not crash

  
  [ Regression potential ]

  Global scale for attached monitors could not be properly computed, and
  thus if attaching an HiDPI device, the UI could not be scaled properly

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

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

[Desktop-packages] [Bug 1785090] Re: Graphics rendering is buggy

2018-08-02 Thread Daniel van Vugt

Can you please take a screenshot (PrtScn) or a photo of the problem and
attach it here?

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

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

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

Title:
  Graphics rendering is buggy

Status in Ubuntu:
  Incomplete

Bug description:
  When any app opens popup on top of another popup data being displayed
  blank

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 20:42:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.45, 4.15.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2018-07-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=9f95808b-710c-4190-8278-52512792741d ro nomodeset quiet splash 
acpi_backlight=vendor acpi_osi=Linux nouveau.runpm=0 vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/05/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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/+bug/1785090/+subscriptions

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2018-08-02 Thread Daniel van Vugt

jMyles, does your keyboard also stop responding to everything, including
the Windows key? If so then that sounds like your shell is frozen, which
is a different bug. In that case please open a new bug by running:

  ubuntu-bug gnome-shell

on the machine.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error

2018-08-02 Thread Daniel van Vugt

** Tags added: xenial

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

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

Title:
  QinHeng Electronics CH345 MIDI adapter triggers error

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Cheap oriental MIDI adapter starts up with the following error, but
  works as expected.*

  E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
  (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
  deferred_volume=yes use_ucm=yes card_properties="module-udev-
  detect.discovered=1""): initialization failed.

  The device:
  1a86:752d QinHeng Electronics CH345 MIDI adapter

  Of course i'm not sure whether this is a PA problem or an ALSA or UDEV
  bug.

  Ubuntu 14.04.2 LTS
  Pulseaudio 1:4.0-0ubuntu11.1

  *  works almost as expected: there is one physical input and one
  output, but in ALSA one input and two outputs appear.

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

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

[Desktop-packages] [Bug 1622730] Re: No sound on headphones after suspend

2018-08-02 Thread Fanjin Zeng

I can confirm this exact same problem still exists today. Is there any
easy workaround for this?

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

Title:
  No sound on headphones after suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a common problem on XMG Clevo W230SS there is no
  output on the headphone jack after suspend. The headphones are
  detected and the speakers are muted, but there is no output to the
  headphones. Init-headphones does not help:

  sudo init-headphone 
  WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax
  WARNING:root:Module is not loaded: i2c_dev
  ERROR:root:Can't find i2c bus
  ERROR:root:Operation failed

  Any workaround beside reboot?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  pia   23276 F pulseaudio
   /dev/snd/controlC0:  pia   23276 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Mon Sep 12 21:56:08 2016
  InstallationDate: Installed on 2015-11-05 (312 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815

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

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

[Desktop-packages] [Bug 1785024]

2018-08-02 Thread Alex Murray

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1.
the specific steps or actions you took that caused you to encounter the
problem, 2. the behavior you expected, and 3. the behavior you actually
encountered (in as much detail as possible). Thanks!

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

Title:
  It gives error

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xwayland error

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Aug  2 14:27:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   btusb, 4.0, 4.15.0-24-generic, x86_64: installed
   btusb, 4.0, 4.15.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2017-08-14 (352 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 6475ET8
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=b69f9cc7-5d91-4cfd-81da-243d4719d396 ro plymouth:debug drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6475ET8
  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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6475ET8:pvrThinkPadT400:rvnLENOVO:rn6475ET8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6475ET8
  dmi.product.version: ThinkPad T400
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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: Tue May 29 18:19:54 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Desktop-packages] [Bug 1785024] Re: It gives error

2018-08-02 Thread Alex Murray

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  It gives error

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xwayland error

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Aug  2 14:27:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   btusb, 4.0, 4.15.0-24-generic, x86_64: installed
   btusb, 4.0, 4.15.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2017-08-14 (352 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 6475ET8
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=b69f9cc7-5d91-4cfd-81da-243d4719d396 ro plymouth:debug drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6475ET8
  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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6475ET8:pvrThinkPadT400:rvnLENOVO:rn6475ET8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6475ET8
  dmi.product.version: ThinkPad T400
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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: Tue May 29 18:19:54 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Desktop-packages] [Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

2018-08-02 Thread Beat

Confirming that with new glib2.0 - 2.48.2-0ubuntu4 in updates
repository, I could now easily do the 14.04 to 16.04 upgrade.

Thanks to all who made this fix happen quickly!

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

Title:
  upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

Status in glib2.0 package in Ubuntu:
  Invalid
Status in glib2.0 source package in Xenial:
  Fix Released

Bug description:
  [Test case]
  Verify that a release-upgrade of an Ubuntu desktop works from trusty to 
xenial with -proposed enabled.

  Package failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul 27 18:31:08 2018
  DuplicateSignature:
   package:libglib2.0-0:2.48.2-0ubuntu3
   Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack):
    triggers ci file contains unknown directive `interest-await'
  ErrorMessage: triggers ci file contains unknown directive `interest-await'
  InstallationDate: Installed on 2015-03-31 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: 
triggers ci file contains unknown directive `interest-await'
  UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions

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

[Desktop-packages] [Bug 1767817] Re: Full text search does not work

2018-08-02 Thread Mahendra Tallur

Hi !

I have the same issue as I stated here :
https://askubuntu.com/questions/1061855/ubuntu-18-04-and-tracker-files-
properly-indexed-but-not-searchable-in-gs-naut

1. I installed tracker
2. I indexed all my data (as indicated on the command line by "tracker status" 
/ "tracker daemon")
3. I checked whether everything was properly indexed by making some queries on 
the command line based on the content of some text files : the command line 
"tracker search" command did yield the right results
4. I made the same searches from Nautilus : they yielded no result : Nautilus 
(and thus the shell) only seem to use the "mlocate" database and not the 
tracker one.

Hypothesis : the fact Ubuntu makes use of Nautilus 3.26 while the rest
of the Gnome stack is 3.28 ?

Actually, did anyone manage to get Nautilus 3.26 (and thus Gnome Shell
with the nautilus search provider) from Ubuntu 18.04 to use the result
of the tracker indexing ? I checked all possible settings in dconf-
editor and found no relevant option.

Cheers :-)

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

[Desktop-packages] [Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()

2018-08-02 Thread Brian Murray

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

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

Title:
  Traceback calling Vte.Terminal.feed_child()

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in vte2.91 source package in Bionic:
  Fix Committed

Bug description:
  [Test Case]
  1) Ensure the following packages from -updates (version 
0.52.2-1ubuntu1~18.04.1) are installed on an Ubuntu 18.04 system: 
gir1.2-vte-2.91 libvte-2.91-0 libvte-2.91-common
  2) Modify /etc/issue e.g. I changed 18.04 to 18.04.2
  3) Ensure /etc/update-manager/release-upgrades contains "Prompt=normal"
  4) Run /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d
  5) When prompted about replacing "the customized configuration file 
'/etc/issue'" click Keep
  6) Observe a traceback in Vte.Terminal.feed_child()

  After installing the new version of vte2.91 in -proposed you should no
  longer receive a Traceback when clicking keep during the upgrade
  process.

  [Regression Potential]
  Per laney: "The regression potential is that I messed up the upload and 
everything using feed* breaks."

  It'd probably be good to test guake too since it uses feed_child().

  [Original Description]
  I was upgrading from Bionic to Cosmic when I received a conffile prompt 
regarding /etc/update-initramfs/initramfs.conf, I clicked keep and then saw 
this Traceback:

  Original exception was:
  Traceback (most recent call last):
    File "/tmp/ubuntu-release-upgrader-filpk342/cosmic", line 8, in 
  sys.exit(main())
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py", 
line 1949, in run
  return self.fullUpgrade()
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py", 
line 1912, in fullUpgrade
  if not self.doDistUpgrade():
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py", 
line 1248, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeCache.py", line 
293, in commit
  apt.Cache.commit(self, fprogress, iprogress)
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 606, in commit
  pm = apt_pkg.PackageManager(self._depcache)
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 569, in 
install_archives
  # compat with older API
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeView.py", line 
229, in run
  res = os.WEXITSTATUS(self.wait_child())
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py", 
line 340, in wait_child
  self.update_interface()
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py", 
line 347, in update_interface
  InstallProgress.update_interface(self)
    File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 252, in 
update_interface
  if err.errno != errno.EAGAIN and err.errno != errno.EWOULDBLOCK:
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py", 
line 276, in conffile
  self.term.feed_child("n\n", -1)
  TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)

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

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

[Desktop-packages] [Bug 1785144] [NEW] /usr/lib/gnome-terminal/gnome-terminal-server:11:gtk_widget_get_toplevel:gtk_main_do_event:gdk_event_source_dispatch:g_main_dispatch:g_main_context_dispatch

2018-08-02 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: xenial yakkety

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

Title:
  /usr/lib/gnome-terminal/gnome-terminal-
  
server:11:gtk_widget_get_toplevel:gtk_main_do_event:gdk_event_source_dispatch:g_main_dispatch:g_main_context_dispatch

Status in gnome-terminal package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()

2018-08-02 Thread Brian Murray

Here is a crash in terminator which occurs with the version of vte2.91
in bionic-updates:

https://errors.ubuntu.com/problem/13b5b72882f409d035b674102f45b0eae419ab2d

Here are some in guake:

https://errors.ubuntu.com/problem/a15ca647934a403f748dad5b3400f805a59a0de7 
(count of 52)
https://errors.ubuntu.com/problem/8f1005750706310a47d63b1eaae0b6e823a9194f 
(count of 93)
https://errors.ubuntu.com/problem/6607888ac9d7c05d5785334483ea2cfe22f9e158 
(count of 64)

Looking at the guake crashes I was able to recreate the crash using the
following command:

/usr/bin/guake -n -r htop -e htop

I then upgraded to the versions of gir1.2-vte-2.91, libvte-2.91-0, and
libvte-2.91-common in -proposed and those also fixed this crash.

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

Title:
  Traceback calling Vte.Terminal.feed_child()

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in vte2.91 source package in Bionic:
  Fix Committed

Bug description:
  [Test Case]
  1) Ensure the following packages from -updates (version 
0.52.2-1ubuntu1~18.04.1) are installed on an Ubuntu 18.04 system: 
gir1.2-vte-2.91 libvte-2.91-0 libvte-2.91-common
  2) Modify /etc/issue e.g. I changed 18.04 to 18.04.2
  3) Ensure /etc/update-manager/release-upgrades contains "Prompt=normal"
  4) Run /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d
  5) When prompted about replacing "the customized configuration file 
'/etc/issue'" click Keep
  6) Observe a traceback in Vte.Terminal.feed_child()

  After installing the new version of vte2.91 in -proposed you should no
  longer receive a Traceback when clicking keep during the upgrade
  process.

  [Regression Potential]
  Per laney: "The regression potential is that I messed up the upload and 
everything using feed* breaks."

  It'd probably be good to test guake too since it uses feed_child().

  [Original Description]
  I was upgrading from Bionic to Cosmic when I received a conffile prompt 
regarding /etc/update-initramfs/initramfs.conf, I clicked keep and then saw 
this Traceback:

  Original exception was:
  Traceback (most recent call last):
    File "/tmp/ubuntu-release-upgrader-filpk342/cosmic", line 8, in 
  sys.exit(main())
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py", 
line 1949, in run
  return self.fullUpgrade()
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py", 
line 1912, in fullUpgrade
  if not self.doDistUpgrade():
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py", 
line 1248, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeCache.py", line 
293, in commit
  apt.Cache.commit(self, fprogress, iprogress)
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 606, in commit
  pm = apt_pkg.PackageManager(self._depcache)
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 569, in 
install_archives
  # compat with older API
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeView.py", line 
229, in run
  res = os.WEXITSTATUS(self.wait_child())
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py", 
line 340, in wait_child
  self.update_interface()
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py", 
line 347, in update_interface
  InstallProgress.update_interface(self)
    File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 252, in 
update_interface
  if err.errno != errno.EAGAIN and err.errno != errno.EWOULDBLOCK:
    File 
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py", 
line 276, in conffile
  self.term.feed_child("n\n", -1)
  TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)

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

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

[Desktop-packages] [Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server

** Merge proposal linked:
   https://code.launchpad.net/~awe/network-manager/+git/ubuntu/+merge/352119

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

Title:
  NetworkManager not able to manage WWAN devices in 18.04 server

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Installed a 18.04 server image, and installed NetworkManager.

  NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10
  -globally-managed-devices.conf" file where it speciefies that all
  devices are by default unmanaged except for types "wifi" and "wwan".

  Now, the problem is that the filter should apply to "gsm" or "cdma"
  types, not "wwan".

  E.g.:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Before the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  eth0  ethernet  unmanaged  -- 
  cdc-wdm0  gsm   unmanaged  -- 
  loloopback  unmanaged  -- 

  After the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  cdc-wdm0  gsm   connected  cell   
  eth0  ethernet  unmanaged  -- 
  loloopback  unmanaged  --

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

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

[Desktop-packages] [Bug 1785107] Re: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver

2018-08-02 Thread Bug Watch Updater

Launchpad has imported 2 comments from the remote bug at
http://bugs.ghostscript.com/show_bug.cgi?id=698652.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2017-10-10T00:45:32+00:00 Reinhard-nissl wrote:

Hi,

News.htm doesn't mention deprecating DELAYBIND as incompatible change.

Bye.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1785107/comments/0

On 2017-10-10T01:28:31+00:00 Ken Sharp wrote:

(In reply to Reinhard Nißl from comment #0)
> Hi,
> 
> News.htm doesn't mention deprecating DELAYBIND as incompatible change.

This doesn't really seem like an incompatible change to me.

As the log message for the commit implementing the change notes, we
don't believe DELAYBIND does anything useful which cannot be achieved
another way.

In addition, if you do use DELAYBIND then it will give you a warning,
and you can use REALLYDELAYBIND instead, so the functionality is not
lost. As the warning message states, anyone using this switch is
encouraged to contact us and discuss it. I'd suggest you do that (but
please don't raise a bug report for it, its not a bug).

Finally, this is a documentation issue, and we won't change news.htm now
that the release is complete. If you feel strongly about this then I
would urge you to download the release candidates in future and let us
know about issues before we complete a release.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1785107/comments/1

** Changed in: pstoedit
   Status: Unknown => Won't Fix

** Changed in: pstoedit
   Importance: Unknown => Medium

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

Title:
  Ghostscript and pstoedit versions not compatible in 18.04 Bionic
  Beaver

Status in pstoedit:
  Won't Fix
Status in ghostscript package in Ubuntu:
  New
Status in pstoedit package in Ubuntu:
  New

Bug description:
  The Ghostscript version 9.22 included in Ubuntu 18.04 has an issue with 
pstoedit.
  There is a known issue with the DELAYBIND command in that particular 
ghostscript version which causes the problems:

  https://bugs.ghostscript.com/show_bug.cgi?id=698652

  Therefore an update of ghostscript and or pstoedit is urgently
  necessary.

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

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

[Desktop-packages] [Bug 1712661] Re: gnome-shell crash using ubuntu-dock with dual monitors

** Description changed:

+ [ Description ]
+ 
+ Using Ubuntu 17.04 on a laptop with an external display on its right
+ hand side all is well with dash-to-dock provided the laptop display is
+ set to the primary display. However if I set the external display to be
+ the primary display (with dash-to-dock disabled) then as soon as I
+ enable it gnome-shell crashes and I am logged off. See attached excerpt
+ from syslog. I have to remove .local/share/gnome-shell in order to
+ recover the situation.
+ 
+ [ Test case ]
+ 
+ Plug an external monitor to a laptop, with the external monitor on the
+ right side and configure the externals primary monitor.
+ 
+ Login and Logout
+ 
+ Gnome shell shouold not crash.
+ 
+ [ Regression Potential ]
+ 
+ The dock won't be temporarily shown in a monitor
+ 
+ 
+ ---
+ 
  To replicate on Artful daily on a laptop, plug in an external monitor
  with the external monitor to the right of the laptop and configure the
  external monitor as the primary display. On configuration it works ok,
  but on logging out and back in gnome-shell crashes.  The problem is only
  seen if the external monitor is the primary display.
  
  I think it likely that this is the same issue reported for dash-to-dock:
  https://github.com/micheleg/dash-to-dock/issues/493
  
- ProblemType: Bug
- DistroRelease: Ubuntu 17.10
+ ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 20:29:17 2017
  InstallationDate: Installed on 2017-08-22 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170821)
- PackageArchitecture: all
- SourcePackage: gnome-shell-extension-ubuntu-dock
+ PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome-shell crash using ubuntu-dock with dual monitors

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  [ Description ]

  Using Ubuntu 17.04 on a laptop with an external display on its right
  hand side all is well with dash-to-dock provided the laptop display is
  set to the primary display. However if I set the external display to
  be the primary display (with dash-to-dock disabled) then as soon as I
  enable it gnome-shell crashes and I am logged off. See attached
  excerpt from syslog. I have to remove .local/share/gnome-shell in
  order to recover the situation.

  [ Test case ]

  Plug an external monitor to a laptop, with the external monitor on the
  right side and configure the externals primary monitor.

  Login and Logout

  Gnome shell shouold not crash.

  [ Regression Potential ]

  The dock won't be temporarily shown in a monitor

  
  ---

  To replicate on Artful daily on a laptop, plug in an external monitor
  with the external monitor to the right of the laptop and configure the
  external monitor as the primary display. On configuration it works ok,
  but on logging out and back in gnome-shell crashes.  The problem is
  only seen if the external monitor is the primary display.

  I think it likely that this is the same issue reported for dash-to-dock:
  https://github.com/micheleg/dash-to-dock/issues/493

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 20:29:17 2017
  InstallationDate: Installed on 2017-08-22 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170821)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

Tested in a Xenial machine, upgrading packages to:

x11-common:
  Installato: 1:7.7+13ubuntu3.1
  Candidato:  1:7.7+13ubuntu3.1
  Tabella versione:
 *** 1:7.7+13ubuntu3.1 500
500 http://ppa.launchpad.net/ci-train-ppa-service/3303/ubuntu 
xenial/main amd64 Packages
500 http://ppa.launchpad.net/ci-train-ppa-service/3303/ubuntu 
xenial/main i386 Packages
100 /var/lib/dpkg/status
 1:7.7+13ubuntu3 500
500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 Packages
nux-tools:
  Installato: 4.0.8+16.04.20180622.2-0ubuntu1
  Candidato:  4.0.8+16.04.20180622.2-0ubuntu1
  Tabella versione:
 *** 4.0.8+16.04.20180622.2-0ubuntu1 500
500 http://ppa.launchpad.net/ci-train-ppa-service/3303/ubuntu 
xenial/main amd64 Packages
100 /var/lib/dpkg/status
 4.0.8+16.04.20170816-0ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 4.0.8+16.04.20160209-0ubuntu2 500
500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Running unity works propery, after upgrade, nux-tools is kept and file
not run... After autoremove, it gets removed and gnome-shell runs
properly.

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

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

** Changed in: nux (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Won't Fix
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached

[Desktop-packages] [Bug 175316] Re: no IDN in nslookup and host

2018-08-02 Thread Vasya Pupkin

Any chances the fix will arrive in xenial?

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

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

** Tags removed: verification-needed-artful

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

-- 
Mailing list: https://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 429391] Re: cups new printer does not find cups printer on a server on network

2018-08-02 Thread Heitzso

No longer a problem.
Please close it out.
> Hello Heitzso,
> Thank you for submitting this bug and reporting a problem with cups and 
> printing.  You made this bug report some time ago and Ubuntu has been updated 
> since then.
>   
> Could you confirm that this is no longer a problem and that we can close the 
> ticket?
> If it is still a problem, are you still interested in finding a solution to 
> this bug?
> If you are, could you let us know, and in the current version, run the 
> following (only once):
> apport-collect BUGNUMBER
> and upload the updated logs and and any other logs that are relevant for this 
> particular issue.
>
> Thank you again for helping make Ubuntu better.
> G
>
> ** Changed in: cups (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  cups new printer does not find cups printer on a server on network

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Karmic alpha 5 (as of Sep 14)
  click on system->administration->printers->new printer
  scan for a cups printer on an ubuntu jaunty server and cannot find it
  tried several ways, e.g. spec the ipp printer, etc.
  finally gave up and just cut and pasted my older jaunty 
/etc/cups/printers.conf stanza 
  for the network-remote jaunty server's cups printer into my new desktop's 
karmic's 
  /etc/cups/printers.conf file
  restarted cups via /etc/init.d/cups restart and works fine

  cups:
Installed: 1.4.0-5
Candidate: 1.4.0-5
Version table:
   *** 1.4.0-5 0

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

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

[Desktop-packages] [Bug 175316] Re: no IDN in nslookup and host

2018-08-02 Thread Andreas Hasenack

This is fixed in cosmic:
https://launchpad.net/ubuntu/+source/bind9/1:9.11.4+dfsg-3ubuntu1


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

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

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

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

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

[Desktop-packages] [Bug 1785122] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1785122/+attachment/5170926/+files/StacktraceSource.txt

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus closed all of a sudden

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 23:16:25 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:  mov
0x10(%rsi),%r9
   PC (0x7f34073e43c1) ok
   source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at 
malloc.c:3612
   _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
   __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230
   g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1785122] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1785122/+attachment/5170927/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1785122/+attachment/5170914/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus closed all of a sudden

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 23:16:25 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:  mov
0x10(%rsi),%r9
   PC (0x7f34073e43c1) ok
   source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at 
malloc.c:3612
   _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
   __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230
   g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1785122] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1785122/+attachment/5170925/+files/Stacktrace.txt

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus closed all of a sudden

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 23:16:25 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:  mov
0x10(%rsi),%r9
   PC (0x7f34073e43c1) ok
   source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at 
malloc.c:3612
   _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
   __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230
   g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1785122] nautilus crashed with SIGSEGV in _int_malloc()

StacktraceTop:
 _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612
 _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=bytes@entry=32) at 
malloc.c:3230
 g_realloc (mem=, n_bytes=32) at ../../../../glib/gmem.c:164
 g_array_maybe_expand (array=0x7f33ec019840, len=len@entry=1) at 
../../../../glib/garray.c:794

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus closed all of a sudden

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 23:16:25 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:  mov
0x10(%rsi),%r9
   PC (0x7f34073e43c1) ok
   source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at 
malloc.c:3612
   _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
   __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230
   g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1785122] [NEW] nautilus crashed with SIGSEGV in _int_malloc()

2018-08-02 Thread Mohammad Hizzani

Public bug reported:

The nautilus closed all of a sudden

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  2 23:16:25 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
 b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:mov
0x10(%rsi),%r9
 PC (0x7f34073e43c1) ok
 source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region 
(needed readable region)!
 destination "%r9" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612
 _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230
 g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

** Affects: nautilus (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash bionic

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in nautilus package in Ubuntu:
  New

Bug description:
  The nautilus closed all of a sudden

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 23:16:25 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:  mov
0x10(%rsi),%r9
   PC (0x7f34073e43c1) ok
   source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region 
(needed readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at 
malloc.c:3612
   _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, 
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
   __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230
   g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 926948] Re: Yahoo! Mail Contacts Will Not Display Under New Firefox 10.0

2018-08-02 Thread Paul White

Thanks Raleigh. Closing as "Invalid" as cause of issue was never
established.

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

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

Title:
  Yahoo! Mail Contacts Will Not Display Under New Firefox 10.0

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  While under Firefox version 9, I was able to display my Yahoo! Mail
  Contacts.  This is no longer the case under Firefox version 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 10.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ac5jw 28134 F pulseaudio
   /dev/snd/controlC0:  ac5jw 28134 F pulseaudio
   /dev/snd/controlC2:  ac5jw 28134 F pulseaudio
  BuildID: 20120129141551
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'V8237'/'VIA 8237 with AD1980 at 0x1000, irq 22'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 53
 Simple ctrls  : 35
  Card1.Amixer.info:
   Card hw:1 'Audigy2'/'SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 
0xa800, irq 17'
 Mixer name : 'SigmaTel STAC9750,51'
 Components : 'AC97a:83847650'
 Controls  : 211
 Simple ctrls  : 46
  Card2.Amixer.info:
   Card hw:2 'U0x46d0x819'/'USB Device 0x46d:0x819 at usb-:00:10.4-4, high 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0819'
 Controls  : 2
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 6144
 Mono: Capture 6144 [100%] [27.00dB] [off]
  Channel: release
  CurrentDmesg: [ 2647.445145] process `skype' is using obsolete setsockopt 
SO_BSDCOMPAT
  Date: Sat Feb  4 19:51:48 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232}, 
Version=2.2.9, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, 
Type=extension, Active=Yes
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  IpRoute:
   default via 192.168.1.254 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2  metric 1
  Profiles: Profile0 (Default) - LastVersion=10.0/20120129141551 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2011-11-10 (87 days ago)
  dmi.bios.date: 02/09/2004
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001.005
  dmi.board.name: K8VSEDX
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1001.005:bd02/09/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnK8VSEDX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/ubuntu/+source/firefox/+bug/926948/+subscriptions

-- 
Mailing list: https://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 926948] Re: Yahoo! Mail Contacts Will Not Display Under New Firefox 10.0

2018-08-02 Thread Raleigh Daniel Stout

I am so far beyond that Mozilla Firefox version that I am ok with closing
this issue.

Regards.

Raleigh Stout

On Tue, Jul 31, 2018 at 10:35 AM, Paul White <926...@bugs.launchpad.net>
wrote:

> Raleigh,
>
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Presumably this problem was a one time occurrence and/or is no longer an
> issue? Can this bug report now be closed?
>
> If we do not hear from you the bug report will close itself in
> approximately 60 days time.
>
> Thank you for helping make Ubuntu better.
>
> Paul White
> [Ubuntu Bug Squad]
>
> ** Changed in: firefox (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/926948
>
> Title:
>   Yahoo! Mail Contacts Will Not Display Under New Firefox 10.0
>
> Status in firefox package in Ubuntu:
>   Incomplete
>
> Bug description:
>   While under Firefox version 9, I was able to display my Yahoo! Mail
>   Contacts.  This is no longer the case under Firefox version 10.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 11.10
>   Package: firefox 10.0+build1-0ubuntu0.11.10.1
>   ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
>   Uname: Linux 3.0.0-15-generic i686
>   AddonCompatCheckDisabled: False
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>   ApportVersion: 1.23-0ubuntu4
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  ac5jw 28134 F pulseaudio
>/dev/snd/controlC0:  ac5jw 28134 F pulseaudio
>/dev/snd/controlC2:  ac5jw 28134 F pulseaudio
>   BuildID: 20120129141551
>   CRDA: Error: [Errno 2] No such file or directory
>   Card0.Amixer.info:
>Card hw:0 'V8237'/'VIA 8237 with AD1980 at 0x1000, irq 22'
>  Mixer name : 'Analog Devices AD1980'
>  Components : 'AC97a:41445370'
>  Controls  : 53
>  Simple ctrls  : 35
>   Card1.Amixer.info:
>Card hw:1 'Audigy2'/'SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102)
> at 0xa800, irq 17'
>  Mixer name : 'SigmaTel STAC9750,51'
>  Components : 'AC97a:83847650'
>  Controls  : 211
>  Simple ctrls  : 46
>   Card2.Amixer.info:
>Card hw:2 'U0x46d0x819'/'USB Device 0x46d:0x819 at usb-:00:10.4-4,
> high speed'
>  Mixer name : 'USB Mixer'
>  Components : 'USB046d:0819'
>  Controls  : 2
>  Simple ctrls  : 1
>   Card2.Amixer.values:
>Simple mixer control 'Mic',0
>  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
>  Capture channels: Mono
>  Limits: Capture 0 - 6144
>  Mono: Capture 6144 [100%] [27.00dB] [off]
>   Channel: release
>   CurrentDmesg: [ 2647.445145] process `skype' is using obsolete
> setsockopt SO_BSDCOMPAT
>   Date: Sat Feb  4 19:51:48 2012
>   ForcedLayersAccel: False
>   IfupdownConfig:
>auto lo
>iface lo inet loopback
>   IncompatibleExtensions: NoScript - 
> ID={73a6fe31-595d-460b-a920-fcc0f8843232},
> Version=2.2.9, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile,
> Type=extension, Active=Yes
>   InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386
> (20100429)
>   IpRoute:
>default via 192.168.1.254 dev eth0  proto static
>169.254.0.0/16 dev eth0  scope link  metric 1000
>192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2
> metric 1
>   Profiles: Profile0 (Default) - LastVersion=10.0/20120129141551 (Running)
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   RunningIncompatibleAddons: True
>   SourcePackage: firefox
>   UpgradeStatus: Upgraded to oneiric on 2011-11-10 (87 days ago)
>   dmi.bios.date: 02/09/2004
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1001.005
>   dmi.board.name: K8VSEDX
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: Rev 1.xx
>   dmi.chassis.asset.tag: Asset-1234567890
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Chassis Manufacture
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001.005:bd02/09/2004:
> svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:
> rvnASUSTeKComputerInc.:rnK8VSEDX:rvrRev1.xx:cvnChassisManufacture:ct3:
> cvrChassisVersion:
>   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/ubuntu/+source/firefox/+bug/
> 926948/+subscriptions
>

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

Title:
  Yahoo! Mail Contacts Will Not Display Under New Firefox 10.0

Status in firefox package in

[Desktop-packages] [Bug 1785107] Re: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver

2018-08-02 Thread Paul White

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

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

** Bug watch added: Ghostscript (AFPL) Bugzilla #698652
   http://bugs.ghostscript.com/show_bug.cgi?id=698652

** Also affects: pstoedit via
   http://bugs.ghostscript.com/show_bug.cgi?id=698652
   Importance: Unknown
   Status: Unknown

** Tags added: bionic

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

Title:
  Ghostscript and pstoedit versions not compatible in 18.04 Bionic
  Beaver

Status in pstoedit:
  Unknown
Status in ghostscript package in Ubuntu:
  New
Status in pstoedit package in Ubuntu:
  New

Bug description:
  The Ghostscript version 9.22 included in Ubuntu 18.04 has an issue with 
pstoedit.
  There is a known issue with the DELAYBIND command in that particular 
ghostscript version which causes the problems:

  https://bugs.ghostscript.com/show_bug.cgi?id=698652

  Therefore an update of ghostscript and or pstoedit is urgently
  necessary.

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

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

[Desktop-packages] [Bug 1581076] Re: Xorg segfaults on start-up on Big Endian PPC hardware

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

** Changed in: xorg-server-lts-xenial (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xorg segfaults on start-up on Big Endian PPC hardware

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-xenial package in Ubuntu:
  Confirmed
Status in xorg-server-lts-xenial source package in Trusty:
  Fix Committed
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server-lts-xenial source package in Xenial:
  Invalid

Bug description:
  On my Big Endian PowerPC machine, Xorg segfaults when starting. I have
  been able to confirm that this does not happen when building Xorg from
  upstream source, and then further confirmed that the source of the
  segfault appears to be caused by a non-upstreamed, ubuntu specific
  patch.

  When building the xorg-server-1.18.3 deb from source, I commented out
  the following patches from debian/patches/series to try to isolate the
  source of the crash. With the following patches not-applied, and the
  resulting .deb package built, the segfault on start does not occur.

  08_xfree86_fix_ia64_inx_outx.diff
  105_nvidia_autodetect.patch
  168_glibc_trace_to_stderr.patch
  188_default_primary_to_first_busid.patch
  190_cache-xkbcomp_output_for_fast_start_up.patch
  191-Xorg-add-an-extra-module-path.patch
  232-xf86compatoutput-valgrind.patch
  no-nv.patch
  228_autobind_gpu.patch
  xf86-inactive-gpuscreen.patch
  config-add-no-removal.patch
  xf86-ignore-conflicting-rr-caps.patch
  fix-detach-gpu.patch
  disable-rotation-transform-gpuscreens.patch
  xmir.patch
  xmir-desktop-file-hint-flag.patch
  drm_device_keep_trying.patch
  xi2-resize-touch.patch
  xmir-fixes.diff

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

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

[Desktop-packages] [Bug 1785107] [NEW] Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver

You have been subscribed to a public bug:

The Ghostscript version 9.22 included in Ubuntu 18.04 has an issue with 
pstoedit.
There is a known issue with the DELAYBIND command in that particular 
ghostscript version which causes the problems:

https://bugs.ghostscript.com/show_bug.cgi?id=698652

Therefore an update of ghostscript and or pstoedit is urgently
necessary.

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


** Tags: ghostscript pstoedit
-- 
Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver
https://bugs.launchpad.net/bugs/1785107
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to ghostscript in Ubuntu.

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

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

2018-08-02 Thread Rachel Greenham

FWIW I can't reproduce this any more either; since 18.04 in fact I've
had no problems with gnome-shell crashing. The monitor very nearly
always does wake up when it's supposed to now (some difference in the
dpms signal being sent? Previously it would always wake for windows and
just had a hard time with Linux), and on the few occasions it hasn't, I
haven't lost my session and I just needed to powercycle the monitor
properly. So I was under the impression this was all fixed. :-) Possibly
by not-obviously-related changes elsewhere.

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

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

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/130
  https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339

  ---

  [ Description ]

  This happened while I was away from the computer. By the timing it
  should have been well after the time it should have gone *into*
  displaysleep, and was also about 45min before I returned, so certainly
  wasn't the wake-up process either.

  What I observed when I did return: My 4K monitor didn't wake up
  (that's a known problem with this monitor, Dell P2715Q), the second
  monitor (Dell U2711) did wake up, showing the login screen.

  So although I've considered my Dell 4K problem a problem with waking
  up, I wonder if it might be actually a problem with it apparently
  going away completely after a longer displaysleep (it's usually fine
  if I just do a short sleep of a minute or two).

  Another possibility is the cat stepped on the keyboard and thus
  triggered an attempted display-wake. But that would actually be out of
  character (for the cat).

  Either way is a bug because the session should survive monitor
  shenanigans... :-)

  In some not known conditions, g-s might crash while computing global
  resolution for monitors.

  [ Test case ]

  There's really no test case for this bug, a part that g-s should not
  crash with this stacktrace. Unforuntaltey this is quite hard to
  reproduce, it might happen while resetting the crtc when setting up a
  (new) monitor or at wake up, but so far nobody has reported a way for
  reproducing this.

  [ Regression potential ]

  Global scale for attached monitors could not be properly computed, and
  thus if attaching an HiDPI device, the UI could not be scaled properly

  ---

  ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct 14 15:39:50 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-30 (75 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fae20ab44a0 : 
mov0x8(%rdi),%eax
   PC (0x7fae20ab44a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_mode_get_resolution () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_calculate_mode_scale () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_update_logical_state_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_rebuild_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_xrandr_handle_xevent () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
  UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 446246] Re: printing two files in a row makes wait for 'getting printer info'

Hello Andrew,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  printing two files in a row makes wait for 'getting printer info'

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gedit

  when printing the first file prints immediately (without that printer status 
is checked).
  when printing a second file while the first is still printing then the 
printer status is checked and users have to wait till they can click to print 
the second file. this is different than in jaunty.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: 71519a5e155620fc8a489e4b79619f6a
  CheckboxSystem: 2abf16d4e86c450ae46e3232dd0d1917
  Date: Thu Oct  8 13:26:55 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.28.0-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.39-generic
  SourcePackage: gedit
  Uname: Linux 2.6.31-12-generic i686

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

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

[Desktop-packages] [Bug 445700] Re: cupsd taking 100% cpu after unsucessful network printer search

Hello Leandro
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  cupsd taking 100% cpu after unsucessful network printer search

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  
  I tried to search for a new printer and the system-config-printer hang 
forever. I closed it
  (the system asked me to "force quit" or "wait", I had to "force quit").

  After some hours I noticed that cupsd is taking 100% of one of my
  cpus.

  Also the tray icon disapeared, but I'm not sure if this has something to do 
with it (it 
  no longer appears when I print something). And I can print normaly, on the 
other
  side.

  This is a desktop and server, so I did not reboot it very often.

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

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

[Desktop-packages] [Bug 444752] Re: cant print at school

Hello Ronnie,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  cant print at school

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Bug in both Jaunty and Karmic

  CUPS version 1.3.9-17ubuntu3.2 (Jaunty)

  When i try to print at my school, the file isn't send to the printer

  I added the printer as an Internet Printing Protocol (https) with the 
following url:
  https://po.fontys.nl:443/printers//.printer

  When i go to cups 'webpage' (http://localhost:631/) i see the following error:
  Error: "Printing: Printer does not support IPP/1.1, trying IPP/1.0..."

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

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

[Desktop-packages] [Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_wi

** Description changed:

  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15
  
- ---
+ [ Description ]
  
  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic was
  in process of installing programs (downloads were complete & actual
  install was in progress)
  
- -
+ [ Test case ]
+ 
+ 1. Run one of the reproducer test (python or gjs version) available at:
+https://gitlab.gnome.org/GNOME/mutter/issues/15
+ 2. when that close, g-s should not crash
+ 
+ [ Regression potential ]
+ 
+ Possible break for windows that have the grab but are not the active
+ ones.
+ 
+ 
+ 
  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
-  SHELL=/bin/bash
- Signal: 6SourcePackage: gnome-shell
+  SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message("assertion
  failed: (window->display->focus_window != window)") from
  g_assertion_message_expr() from meta_window_unmanage() from
  handle_other_xevent()

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15

  [ Description ]

  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic
  was in process of installing programs (downloads were complete &
  actual install was in progress)

  [ Test case ]

  1. Run one of the reproducer test (python or gjs version) available at:
 https://gitlab.gnome.org/GNOME/mutter/issues/15
  2. when that close, g-s should not crash

  [ Regression potential ]

  Possible break for windows that have the grab but are not the active
  ones.

  
  

  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell

[Desktop-packages] [Bug 429391] Re: cups new printer does not find cups printer on a server on network

Hello Heitzso,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  cups new printer does not find cups printer on a server on network

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Karmic alpha 5 (as of Sep 14)
  click on system->administration->printers->new printer
  scan for a cups printer on an ubuntu jaunty server and cannot find it
  tried several ways, e.g. spec the ipp printer, etc.
  finally gave up and just cut and pasted my older jaunty 
/etc/cups/printers.conf stanza 
  for the network-remote jaunty server's cups printer into my new desktop's 
karmic's 
  /etc/cups/printers.conf file
  restarted cups via /etc/init.d/cups restart and works fine

  cups:
Installed: 1.4.0-5
Candidate: 1.4.0-5
Version table:
   *** 1.4.0-5 0

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

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

[Desktop-packages] [Bug 437302] Re: cups [Job 61] Stopping job because the scheduler could not open the output file.

Hello Guy,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  cups [Job 61] Stopping job because the scheduler could not open the
  output file.

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Hello all,
  No more possible to print.

   lpstat -t
  le programmateur s’exécute
  destination système par défaut : RX425
  périphérique pour RX425 : ///dev/usb/usbmon3
  RX425 acceptant des requêtes depuis sam. 26 sept. 2009 19:45:07 CEST
  l’imprimante RX425 est inactive, mais activée depuis sam. 26 sept. 2009 
19:45:07 CEST
  guy@guy-desktop:/var/log/cups$

  D [26/Sep/2009:19:45:01 +0200] cupsdReadClient: 9 1.1 Get-Printer-Attributes 1
  D [26/Sep/2009:19:45:01 +0200] Get-Printer-Attributes 
ipp://localhost/printers/RX425
  D [26/Sep/2009:19:45:01 +0200] Returning IPP successful-ok for 
Get-Printer-Attributes (ipp://localhost/printers/RX425) from localhost
  D [26/Sep/2009:19:45:01 +0200] cupsdSetBusyState: Not busy
  D [26/Sep/2009:19:45:07 +0200] cupsdAcceptClient: 10 from localhost (Domain)
  D [26/Sep/2009:19:45:07 +0200] cupsdReadClient: 10 POST /printers/RX425 
HTTP/1.1
  D [26/Sep/2009:19:45:07 +0200] cupsdSetBusyState: Active clients
  D [26/Sep/2009:19:45:07 +0200] cupsdAuthorize: No authentication data 
provided.
  D [26/Sep/2009:19:45:07 +0200] cupsdReadClient: 10 1.1 Print-Job 1
  D [26/Sep/2009:19:45:07 +0200] Print-Job ipp://localhost/printers/RX425
  D [26/Sep/2009:19:45:07 +0200] [Job ???] Auto-typing file...
  I [26/Sep/2009:19:45:07 +0200] [Job ???] Request file type is 
application/postscript.
  D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(J-)
  D [26/Sep/2009:19:45:07 +0200] cupsdSetBusyState: Active clients and dirty 
files
  D [26/Sep/2009:19:45:07 +0200] add_job: requesting-user-name="guy"
  D [26/Sep/2009:19:45:07 +0200] Adding default job-sheets values "none,none"...
  I [26/Sep/2009:19:45:07 +0200] [Job 61] Adding start banner page "none".
  D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(-S)
  D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(J-)
  I [26/Sep/2009:19:45:07 +0200] [Job 61] Adding end banner page "none".
  I [26/Sep/2009:19:45:07 +0200] [Job 61] File of type application/postscript 
queued by "guy".
  D [26/Sep/2009:19:45:07 +0200] [Job 61] hold_until=0
  I [26/Sep/2009:19:45:07 +0200] [Job 61] Queued on "RX425" by "guy".
  D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(J-)
  D [26/Sep/2009:19:45:07 +0200] cupsdSetBusyState: Active clients, printing 
jobs, and dirty files
  D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(-S)
  D [26/Sep/2009:19:45:07 +0200] [Job 61] job-sheets=none,none
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[0]="RX425"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[1]="61"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[2]="guy"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[3]="Test Page"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[4]="1"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[5]="PageSize=A4 
job-uuid=urn:uuid:dcddb2ee-42ec-3869-5c98-1911b0e554e7 
job-originating-host-name=localhost"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[6]="/var/spool/cups/d00061-001"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] 
envp[0]="CUPS_CACHEDIR=/var/cache/cups"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[1]="CUPS_DATADIR=/usr/share/cups"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] 
envp[2]="CUPS_DOCROOT=/usr/share/cups/doc-root"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] 
envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] 
envp[4]="CUPS_REQUESTROOT=/var/spool/cups"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[5]="CUPS_SERVERBIN=/usr/lib/cups"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[6]="CUPS_SERVERROOT=/etc/cups"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[7]="CUPS_STATEDIR=/var/run/cups"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[8]="HOME=/var/spool/cups/tmp"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] 
envp[9]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin"
  D [26/Sep/2009:19:45:07 +0200] [Job 61] 
envp[10]="SERVER_ADMIN=root@guy-desktop"
  D

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

** Description changed:

  https://gitlab.gnome.org/GNOME/mutter/issues/130
  https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
  
  ---
+ 
+ [ Description ]
  
  This happened while I was away from the computer. By the timing it
  should have been well after the time it should have gone *into*
  displaysleep, and was also about 45min before I returned, so certainly
  wasn't the wake-up process either.
  
  What I observed when I did return: My 4K monitor didn't wake up (that's
  a known problem with this monitor, Dell P2715Q), the second monitor
  (Dell U2711) did wake up, showing the login screen.
  
  So although I've considered my Dell 4K problem a problem with waking up,
  I wonder if it might be actually a problem with it apparently going away
  completely after a longer displaysleep (it's usually fine if I just do a
  short sleep of a minute or two).
  
  Another possibility is the cat stepped on the keyboard and thus
  triggered an attempted display-wake. But that would actually be out of
  character (for the cat).
  
  Either way is a bug because the session should survive monitor
  shenanigans... :-)
  
- ProblemType: Crash
- DistroRelease: Ubuntu 17.10
+ In some not known conditions, g-s might crash while computing global
+ resolution for monitors.
+ 
+ [ Test case ]
+ 
+ There's really no test case for this bug, a part that g-s should not
+ crash with this stacktrace. Unforuntaltey this is quite hard to
+ reproduce, it might happen while resetting the crtc when setting up a
+ (new) monitor or at wake up, but so far nobody has reported a way for
+ reproducing this.
+ 
+ [ Regression potential ]
+ 
+ Global scale for attached monitors could not be properly computed, and
+ thus if attaching an HiDPI device, the UI could not be scaled properly
+ 
+ ---
+ 
+ ProblemType: CrashDistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct 14 15:39:50 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
  
  InstallationDate: Installed on 2017-07-30 (75 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fae20ab44a0 : 
mov0x8(%rdi),%eax
   PC (0x7fae20ab44a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
- Signal: 11
- SourcePackage: gnome-shell
+ Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_mode_get_resolution () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_calculate_mode_scale () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_update_logical_state_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_rebuild_derived () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_manager_xrandr_handle_xevent () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
  UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
  UserGroups:

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

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

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/130
  https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339

  ---

  [ Description ]

  This happened while I was away from the computer. By the timing it
  should have been well after the time it should have gone *into*
  displaysleep, and was also about 45min before I returned, so certainly
  wasn't the wake-up process either.

  What I observed when I did return: My 4K monitor didn't wake up
  (that's a known problem with this monitor, Dell P2715Q), the second
  monitor (Dell U2711) did wake up, showing the login screen.

  So although I've considered my Dell 4K problem a problem with waking
  up, I wonder if it might be actually a problem with it apparently
  going away completely after a longer displaysleep (it's usually fine
  if I just do a short sleep of a minute or two).

  Another possibility is the cat stepped on the keyboard and thus
  triggered an attempted display-wake. But that would actually be out of
  character (for the cat).

  Either way is a bug because the session should survive monitor
  shenanigans... :-)

  In

[Desktop-packages] [Bug 426776] Re: Deleted printer comes back

Hello Popey,
Love the Ubuntu Podcast!
A few episodes ago you challenged each other to spend lunch hours helping out
with a project. Well, your choice of bug triaging inspired me. And here I am
attempting to clear up the old bugs.

You submitted this one in 2009. Here is my usual blurb:

Thank you for submitting this bug and reporting a problem with cups and
printing. You made this bug report some time ago and Ubuntu has been updated
since then.

Could you confirm that this is no longer a problem and that we can close the
ticket?
If it is still a problem, are you still interested in finding a solution to
this bug?
If you are, could you let us know, and in the current version, run the
following (only once):
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this
particular issue.

Thank you again for helping make Ubuntu better.
G
PS Again, love the podcast! And love Ubuntu!

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

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

Title:
Deleted printer comes back

Status in cups package in Ubuntu:
Incomplete

Bug description:
Binary package hint: cups

I have an HP 6310 All In One printer/scanner/copier/fax device.
Firstly, thanks for making this device painless to use in Ubuntu, I
love it!

The issue is that the device is a scanner and printer (via USB) and a
printer (via Ethernet). I print to it from multiple computers, so I
have them all set to print over the network. This works fine. However
on the desktop PC it is sat next to, it is also connected via USB, and
as such gets auto detected and I now have two printers on my desktop.
The name doesn't explicitly identify which is the 'usb connected' one
and which is the 'network connected' one.

I deleted the USB connected printer because I want all machines to
print over the network, even this one. However the next time I booted
up the printer it was re-detected and reappeared on my desktop.

I would like a deleted printer to go away and stay away. I appreciate
this may not be a bug, it may be a wishlist item, I just wanted it to
be noted that there is a use case for a printer to be removed. I don't
want to have to maintain multiple printer definitions on my desktop
PC.

ProblemType: Bug
Architecture: amd64
Date: Wed Sep 9 12:56:24 2009
DistroRelease: Ubuntu 9.10
Lpstat:
device for Officejet-6300-series:
hp:/usb/Officejet_6300_series?serial=CN88BFB5N204M4
device for Officejet-6300-series-Fax:
hpfax:/usb/Officejet_6300_series?serial=CN88BFB5N204M4
device for Officejet-6300_Network:
dnssd://Officejet%206300%20series%20%5B4337AB%5D._pdl-datastream._tcp.local/
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: cups 1.4.0-5
Papersize: a4
PccardctlIdent:

PccardctlStatus:

PpdFiles:
Officejet-6300-series-Fax: HP Fax hpcups
Officejet-6300_Network: HP Officejet 6300 Series, hpcups 3.9.8
Officejet-6300-series: HP Officejet 6300 Series, hpcups 3.9.8
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-9-generic
root=UUID=c0284904-fb40-40a3-bf9b-7d7fd302fb33 ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SourcePackage: cups
Uname: Linux 2.6.31-9-generic x86_64
dmi.bios.date: 04/24/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1801
dmi.board.name: P5N32-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIACPIBIOSRevision1801:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

[Desktop-packages] [Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180

This will be fixed in mutter (3.29.90-1)

** Description changed:

+ [ Description ]
+ 
  gnome-control-center does not respond after we set the resolution
  320x180
+ 
+ 
+ [ Test case ]
+ 
+ Open gnome-control-center -> Displays
+ Low resolutions (such as 320x180) should not be listed.
+ 
+ Trying to set the lowst listed resolution, should just apply without
+ breaking gnome-control-center.
+ 
+ [ Regression potential ]
+ 
+ No alternative resolutions are shown in g-c-c
+ 
+ ---
  
  Expected results: shows the countdown dialog
  Actual results: the countdown dialog doesn't show. Only mouse cursor can 
move. All of the buttons/icons don't respond.
  
  Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the
  count-down dialog shows up!
  
- 
  Notebook: Dell XPS 13

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

Title:
  gnome-control-center does not respond after we set the resolution
  320x180

Status in gnome-control-center:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  gnome-control-center does not respond after we set the resolution
  320x180

  
  [ Test case ]

  Open gnome-control-center -> Displays
  Low resolutions (such as 320x180) should not be listed.

  Trying to set the lowst listed resolution, should just apply without
  breaking gnome-control-center.

  [ Regression potential ]

  No alternative resolutions are shown in g-c-c

  ---

  Expected results: shows the countdown dialog
  Actual results: the countdown dialog doesn't show. Only mouse cursor can 
move. All of the buttons/icons don't respond.

  Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log",
  the count-down dialog shows up!

  Notebook: Dell XPS 13

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

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

[Desktop-packages] [Bug 413867] Re: something touched my cupsd.conf

Hello Alexander,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  something touched my cupsd.conf

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  On this system I never had a printer. However, my cupsd.conf file was
  modified somehow:

  Setting up cups (1.3.11-1ubuntu6) ...

  Configuration file `/etc/cups/cupsd.conf'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.

  Maybe its not cups itself that changed the conf file - I dont know,
  but something did as I get what i pasted above.

  Are there packages that are known to touch that file? If so, please
  add the packages that do that without me touching printing ;).

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

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

[Desktop-packages] [Bug 425176] Re: Can't remove old shared printers

Hello Patrice,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  Can't remove old shared printers

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Under Jaunty. I can't remove old shared printers automatically found
  by cups. There are still present in client but no more here on my
  servers (no more physically, and no more shared by cups on my server).

  At the end, the client offers me to print under 5 or 6 printers that
  do not exist since one year. And I can't remove them.

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

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

[Desktop-packages] [Bug 1568852] Re: missing title bar for some applications

2018-08-02 Thread Martin Fiedler

I've not seen it yet on bionic (which uses 3.28), but it's still not
fixed on xenial's 3.18. Even though I encounter this quite frequently
there, I couldn't find a way to reproduce it in a consistent manner.

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

Title:
  missing title bar for some applications

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Some applications are missing the titlebar in gnome-session-flashback
  with Metacity. Standard GNOME applications are not affected, but some
  that use Xlib directly, like mupdf or feh, are.

  Steps to reproduce:
  - Use mupdf to display any .pdf file, or use feh to display any image file.

  Expected result:
  - A window with a title bar appears.

  Actual result:
  - A window without title bar, but thicker borders, appears.
  - This does not always happen; sometimes, the title bars appear just fine.
  - see attached screenshot

  Things I tried:
  - Enabling/disabling org.gnome.metacity.compositing-manager via dconf-editor 
doesn't make a difference.
  - In an Xlib-based program I wrote myself, I could get rid of this by doing a 
dummy call to XSetWMNormalHints() with BaseSize set to the window size I was 
using anyway and MinSize set to 1x1.

  metacity:
    Installed: 1:3.18.3-1ubuntu2
    Candidate: 1:3.18.3-1ubuntu2
    Version table:
   *** 1:3.18.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

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

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

[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

** Description changed:

+ [ Description ]
+ 
+ GNome shell crashes after Xorg loggin
+ 
+ [ Test case ]
+ 
+ From GDM login in a GNOME Ubuntu session (so Xorg).
+ It should start with no issues
+ 
+ [ Regression potential ]
+ 
+ We were deferencing a NULL pointer while outputting an error.
+ This is pretty safe. Although the session might still not run properly as per 
a driver issue to be addressed in linux package.
+ 
+ ---
+ 
  https://gitlab.gnome.org/GNOME/mutter/issues/70
  https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
  
  https://salsa.debian.org/gnome-team/mutter/merge_requests/6
  
  ---
  
  The crash was reported after booting and logging in to an X.Org session.
  
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  
  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
  
  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
- SegvReason: reading NULL VMA
- Signal: 11SourcePackage: gnome-shell
+ SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  [ Description ]

  GNome shell crashes after Xorg loggin

  [ Test case ]

  From GDM login in a GNOME Ubuntu session (so Xorg).
  It should start with no issues

  [ Regression potential ]

  We were deferencing a NULL pointer while outputting an error.
  This is pretty safe. Although the session might still not run properly as per 
a driver issue to be addressed in linux package.

  ---

  https://gitlab.gnome.org/GNOME/mutter/issues/70
  https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665

  https://salsa.debian.org/gnome-team/mutter/merge_requests/6

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault

[Desktop-packages] [Bug 1784397] Re: dev channel (69.0.3497.12) FTBFS on cosmic amd64

2018-08-02 Thread Nicolas Capens

I don't have a system I can reproduce this on, but please try https
://swiftshader-review.googlesource.com/c/SwiftShader/+/19608

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

Title:
  dev channel (69.0.3497.12) FTBFS on cosmic amd64

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since a recent binutils update in cosmic, chromium-browser 69 fails to
  build on cosmic/amd64. It builds fine on other supported architectures
  (i386, armhf, arm64):

  [11790/33363] SOLINK swiftshader/libGLESv2.so
  FAILED: swiftshader/libGLESv2.so swiftshader/libGLESv2.so.TOC 
  python "../../build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" 
--nm="nm" --sofile="swiftshader/libGLESv2.so" 
--tocfile="swiftshader/libGLESv2.so.TOC" --output="swiftshader/libGLESv2.so"  
-- ../../../../../usr/bin/clang++ -shared 
-Wl,--version-script=../../third_party/swiftshader/src/OpenGL/libGLESv2/libGLESv2.lds
 -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro 
-Wl,-z,defs -Wl,--as-needed -fuse-ld=bfd -m64 -Wl,-O2 -Wl,--gc-sections 
-nostdlib++ -rdynamic -Wl,--hash-style=both -Wl,--gc-sections -o 
"swiftshader/libGLESv2.so" -Wl,-soname="libGLESv2.so" 
@"swiftshader/libGLESv2.so.rsp"
  /<>/out/Release/../../../../../usr/bin/ld.bfd: 
obj/third_party/swiftshader/src/OpenGL/libGLESv2/libswiftshader_libGLESv2_static.a(libGLESv2.o):
 relocation R_X86_64_PC32 against protected symbol `glBlendEquationSeparate' 
can not be used when making a shared object
  /<>/out/Release/../../../../../usr/bin/ld.bfd: final link 
failed: bad value
  clang: error: linker command failed with exit code 1 (use -v to see 
invocation)

  I have downgraded to binutils 2.30-22ubuntu1 and this builds fine.
  Then upgraded to binutils 2.31-1ubuntu1 and it failed to build.

  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=451875b4f976a527395e9303224c7881b65e12ed looks related.

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

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

[Desktop-packages] [Bug 1767956] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_b

** Description changed:

+ [ Description ]
+ 
+ GNome shell crashes after Xorg logging
+ 
+ [ Test case ]
+ 
+ From GDM login in a GNOME Ubuntu session (so Xorg).
+ It should start with no issues
+ 
+ [ Regression potential ]
+ 
+ Nothing know, this is a safe NULL check, so no crash will happen.
+ It's not granted that the session will work properly aftewards though.
+ 
+ --
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/ceb319b41dc72ad98263c386ee6891b05fca8623 
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/.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from
  meta_monitor_manager_kms_initable_init() from g_initable_new_valist()
  from g_initable_new() from meta_backend_create_monitor_manager()

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  GNome shell crashes after Xorg logging

  [ Test case ]

  From GDM login in a GNOME Ubuntu session (so Xorg).
  It should start with no issues

  [ Regression potential ]

  Nothing know, this is a safe NULL check, so no crash will happen.
  It's not granted that the session will work properly aftewards though.

  --

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

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

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

[Desktop-packages] [Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal

** Description changed:

- Under wayland:
+ [ Description ]
+ 
+ Under wayland adding a monitor in cloned mode might crash g-s
+ 
+ See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248
+ 
+ [ Test case ]
+ 
+ Open an Ubuntu session on Wayland:
  
  1. Attach another monitor
  2. Mark as cloned display
  3. Gnome-shell should not crash
  
  
- See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248
+ [ Regression potential ]
+ 
+ Global scale for attached monitors could not be properly computed, and
+ thus if attaching an HiDPI device, the UI could not be scaled properly

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

Title:
  Changing monitor settings crashes on
  meta_window_wayland_move_resize_internal

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  Under wayland adding a monitor in cloned mode might crash g-s

  See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248

  [ Test case ]

  Open an Ubuntu session on Wayland:

  1. Attach another monitor
  2. Mark as cloned display
  3. Gnome-shell should not crash

  
  [ Regression potential ]

  Global scale for attached monitors could not be properly computed, and
  thus if attaching an HiDPI device, the UI could not be scaled properly

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

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

[Desktop-packages] [Bug 405320] Re: crash CUPS after print logout

Hello Komentarku,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G

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

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

Title:
  crash CUPS after print logout

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: libdebian-installer4-udeb

  iacnt print from my Ubuntu jaunty on Epson c90

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

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

[Desktop-packages] [Bug 1542519] Re: Double menu bar

2018-08-02 Thread janot

^ this solution doesn't work anymore

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

Title:
  Double menu bar

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  I currently get two menu bars in VLC on Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-3
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  5 23:31:41 2016
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user's groups )

Just noticed in $HOME/.xsession-errors the following:


(polkit-gnome-authentication-agent-1:4029): polkit-gnome-1-WARNING **: 
15:04:54.498: Failed to register client: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

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

Title:
  Regression due to CVE-2018-1116 (processes not inheriting user's
  groups )

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  This report is tracking a possible regression caused by the recent
  CVE-2018-1116 patches to policykit-1.

  On 18.04, since package upgrades on July 23rd, and after the first
  reboot since then on Aug 1st, I hit an issue with the primary (sudo,
  adm, etc...) user getting Permission Denied trying to do:

  tail -f /var/log/syslog

  when that file is owned by syslog:adm and is g=r.

  I then found that "groups" reports only the $USER and not the entire
  list, but "groups $USER" reports all the groups correctly.

  The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g
  default-shell /bin/bash"

  After changing the user's shell back to /bin/bash and logging in on
  tty1 the list of groups shows correctly for the /bin/bash process
  running on tty1.

  I investigated and found that for the affected processes, such as the
  tmux process, /proc/$PID/loginuid = 4294967295  whereas the /bin/bash
  process on tty1 correctly reported 1000. The same with the respective
  gid_map and uid_map.

  4294967295 == -1 == 0x

  The recent CVE patch to policykit has several functions where it does
  "uid = -1" which seems to tie in to my findings so far.

  I also noticed Ubuntu is still based on version 0.105 which was
  released in 2012 - upstream released 0.115 with the CVE patch.

  I suspect the backporting has missed something.

  The Ubuntu backport patch is:

  https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu
  /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935

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

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

[Desktop-packages] [Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server

2018-08-02 Thread Alfonso Sanchez-Beato

** Merge proposal unlinked:
   https://code.launchpad.net/~awe/network-manager/+git/ubuntu/+merge/352119

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

Title:
  NetworkManager not able to manage WWAN devices in 18.04 server

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Installed a 18.04 server image, and installed NetworkManager.

  NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10
  -globally-managed-devices.conf" file where it speciefies that all
  devices are by default unmanaged except for types "wifi" and "wwan".

  Now, the problem is that the filter should apply to "gsm" or "cdma"
  types, not "wwan".

  E.g.:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Before the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  eth0  ethernet  unmanaged  -- 
  cdc-wdm0  gsm   unmanaged  -- 
  loloopback  unmanaged  -- 

  After the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  cdc-wdm0  gsm   connected  cell   
  eth0  ethernet  unmanaged  -- 
  loloopback  unmanaged  --

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

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

[Desktop-packages] [Bug 1784671] Re: Keeping Alt+Space pressed shows the window menu and then minimizes the window

** Description changed:

  To reproduce:
- 
  
  Open a couple of windows
  Press Alt+Space and keep it pressed
  
- 
  Expected results:
- 
  
  The window menu opens and nothing else happens
  
- 
  Current behavior:
- 
  
  The window menu opens
  The window is minimized
  The window menu of the following window is open
  The window is minized
  ...
+ 
+ [ Description ]
+ 
+ Pressing Alt+Space and keeping it pressed causes a window to be
+ minimized
+ 
+ [ Test case ]
+ 
+ 1. Press Alt+Space and keep it pressed
+ 2. The menu should stay open without any action being performed automatically
+ 
+ [ Regression potential ]
+ 
+ Key-actions happening with popups open when keybindings use modifiers
+ might be broken afterwards. No case that I know.

** Description changed:

+ 
+ [ Description ]
+ 
+ Pressing Alt+Space and keeping it pressed causes a window to be
+ minimized
+ 
+ [ Test case ]
+ 
+ 1. Press Alt+Space and keep it pressed
+ 2. The menu should stay open without any action being performed automatically
+ 
+ [ Regression potential ]
+ 
+ Key-actions happening with popups open when keybindings use modifiers
+ might be broken afterwards. No case that I know.
+ 
+ ---
+ 
  To reproduce:
  
  Open a couple of windows
  Press Alt+Space and keep it pressed
  
  Expected results:
  
  The window menu opens and nothing else happens
  
  Current behavior:
  
  The window menu opens
  The window is minimized
  The window menu of the following window is open
  The window is minized
- ...
- 
- [ Description ]
- 
- Pressing Alt+Space and keeping it pressed causes a window to be
- minimized
- 
- [ Test case ]
- 
- 1. Press Alt+Space and keep it pressed
- 2. The menu should stay open without any action being performed automatically
- 
- [ Regression potential ]
- 
- Key-actions happening with popups open when keybindings use modifiers
- might be broken afterwards. No case that I know.

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

Title:
  Keeping Alt+Space pressed shows the window menu and then minimizes the
  window

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  
  [ Description ]

  Pressing Alt+Space and keeping it pressed causes a window to be
  minimized

  [ Test case ]

  1. Press Alt+Space and keep it pressed
  2. The menu should stay open without any action being performed automatically

  [ Regression potential ]

  Key-actions happening with popups open when keybindings use modifiers
  might be broken afterwards. No case that I know.

  ---

  To reproduce:

  Open a couple of windows
  Press Alt+Space and keep it pressed

  Expected results:

  The window menu opens and nothing else happens

  Current behavior:

  The window menu opens
  The window is minimized
  The window menu of the following window is open
  The window is minized

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

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

[Desktop-packages] [Bug 1785090] [NEW] Graphics rendering is buggy

2018-08-02 Thread Anand Chandrabhanu

Public bug reported:

When any app opens popup on top of another popup data being displayed
blank

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  2 20:42:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 396.45, 4.15.0-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2018-07-18 (14 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=9f95808b-710c-4190-8278-52512792741d ro nomodeset quiet splash 
acpi_backlight=vendor acpi_osi=Linux nouveau.runpm=0 vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/05/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
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 possible-manual-nvidia-install 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/1785090

Title:
  Graphics rendering is buggy

Status in xorg package in Ubuntu:
  New

Bug description:
  When any app opens popup on top of another popup data being displayed
  blank

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 20:42:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.45, 4.15.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2018-07-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=9f95808b-710c-4190-8278-52512792741d ro nomodeset quiet splash 
acpi_backlight=vendor acpi_osi=Linux nouveau.runpm=0 vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Desktop-packages] [Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor

2018-08-02 Thread Bruce A. MacNaughton

Thank you!

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

Title:
  Ubuntu 18.04 Workspaces only change on primary monitor

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  After connecting an external monitor to the laptop:

  - the 4 workspaces that I could access using keyboard shortcuts seem to have 
been reduced to only 2
  - the 'workspace' does not appear to be changeable on the external 
(secondary) monitor

  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: Sat Apr 28 12:42:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-28 (0 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/1767564/+subscriptions

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4

---
gdm3 (3.28.2-3ubuntu4) cosmic; urgency=medium

  * ubuntu_nvidia_prime.patch:
- Run scripts for Prime before and after Gdm sessions (LP: #1778011).

 -- Alberto Milone   Mon, 30 Jul 2018
18:31:17 +0200

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

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-prime source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  
  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  
  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

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

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

[Desktop-packages] [Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts

This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4

---
gdm3 (3.28.2-3ubuntu4) cosmic; urgency=medium

  * ubuntu_nvidia_prime.patch:
- Run scripts for Prime before and after Gdm sessions (LP: #1778011).

 -- Alberto Milone   Mon, 30 Jul 2018
18:31:17 +0200

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

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

Title:
  GDM blocks SIGUSR1 used in PAM scripts

Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Xenial:
  New
Status in gdm3 source package in Bionic:
  New
Status in gdm3 source package in Cosmic:
  Fix Released
Status in gdm3 package in Debian:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/399

  [Impact]
  GDM blocks SIGUSR1 for it's processes, since this is used in communication 
with X. This signal is later unblocked, however it happens after PAM
  interaction, so if PAM depends on this signal in any way it will get blocked.
  The issue has been fixed upstream.

  [Test Case]
  1. Prepare a setup described in Other Info using the attached scripts.
  2. Log in.
  3. Check logs /tmp/auth.log.

  Expected result: SIGUSR1 has been received.
  Actual result: SIGUSR1 never reaches the process.

  [Regression Potential]
  If there were components depending on SIGUSR1 their behavior may change - 
features that were inactive before may be triggered.

  [Other Info]

   Original bug description:

  In case of the following scenario:
  1. PAM configured to run auth and session with pam_exec scripts synchronizing 
via SIGUSR1
  2. Using GDM as the login manager causes SIGUSR1 never reaches the target 
scripts.

  Workaround:
  a) Use SIGUSR2 in the scripts.
  b) Comment out block_sigusr1() call in daemon/main.c.

  To reproduce add the following entries:
  /etc/pam.d/common-auth:
  auth  optionalpam_exec.so log=/tmp/auth.log expose_authtok quiet 
/usr/local/bin/auth.py

  /etc/pam.d/common-session:
  session   optional  pam_exec.so   log=/tmp/session.log  
/usr/local/bin/session.py

  Attaching example scripts.
  When using SIGUSR1 - sigusr1_handler is never called, with SIGUSR2 it is 
called without issues.

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2018-08-02 Thread jMyles

I am experiencing this issue and it's just totally crippling.  I can't
keep a session going for more than a few minutes without suddenly losing
the ability to interact with applications.

The specifics of my experience more closely match bug #1730229 -
although that is marked as a duplicate of this one.  Specifically,
unlike this issue (but like bug #1730229), I am unable to use alt-f2
once the issue manifests itself.

Other mentioned workarounds in this thread do not work for me, including
switching-to-tty-and-back, logging-out-and-back-in, and alt-tab.

I have also disabled gnome-shell extensions altogether and set the
number of workspaces to 1.  Any other ideas for a temporary workaround?

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1568852] Re: missing title bar for some applications

2018-08-02 Thread Alberts Muktupāvels

3.18 is very old release, does this happens with 3.28?

Is there any way to reproduce this bug always? Bug description says that
it does not happen always... :(

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

Title:
  missing title bar for some applications

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Some applications are missing the titlebar in gnome-session-flashback
  with Metacity. Standard GNOME applications are not affected, but some
  that use Xlib directly, like mupdf or feh, are.

  Steps to reproduce:
  - Use mupdf to display any .pdf file, or use feh to display any image file.

  Expected result:
  - A window with a title bar appears.

  Actual result:
  - A window without title bar, but thicker borders, appears.
  - This does not always happen; sometimes, the title bars appear just fine.
  - see attached screenshot

  Things I tried:
  - Enabling/disabling org.gnome.metacity.compositing-manager via dconf-editor 
doesn't make a difference.
  - In an Xlib-based program I wrote myself, I could get rid of this by doing a 
dummy call to XSetWMNormalHints() with BaseSize set to the window size I was 
using anyway and MinSize set to 1x1.

  metacity:
    Installed: 1:3.18.3-1ubuntu2
    Candidate: 1:3.18.3-1ubuntu2
    Version table:
   *** 1:3.18.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

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

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

[Desktop-packages] [Bug 1568852] Re: missing title bar for some applications

2018-08-02 Thread Charles Lohr

I am also having this problem.  Additional notes:  This happens even on
the most primitive X11 applications.  Even applications like the Rosetta
Code X11 xlib application.  This happens regardless of if you use
XCreate window or XCreateSimpleWindow.  Additionally, even if you change
the window title, the window title in bar does not appear.

This bug does not seem to happen with Xt, Gnome, KDE and similar
applications.

This bug is VERY annoying. Hopefully this helps move things along.

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

Title:
  missing title bar for some applications

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Some applications are missing the titlebar in gnome-session-flashback
  with Metacity. Standard GNOME applications are not affected, but some
  that use Xlib directly, like mupdf or feh, are.

  Steps to reproduce:
  - Use mupdf to display any .pdf file, or use feh to display any image file.

  Expected result:
  - A window with a title bar appears.

  Actual result:
  - A window without title bar, but thicker borders, appears.
  - This does not always happen; sometimes, the title bars appear just fine.
  - see attached screenshot

  Things I tried:
  - Enabling/disabling org.gnome.metacity.compositing-manager via dconf-editor 
doesn't make a difference.
  - In an Xlib-based program I wrote myself, I could get rid of this by doing a 
dummy call to XSetWMNormalHints() with BaseSize set to the window size I was 
using anyway and MinSize set to 1x1.

  metacity:
    Installed: 1:3.18.3-1ubuntu2
    Candidate: 1:3.18.3-1ubuntu2
    Version table:
   *** 1:3.18.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

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

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

[Desktop-packages] [Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu4

---
glib2.0 (2.48.2-0ubuntu4) xenial; urgency=medium

  * Add a versioned Pre-Depends for dpkg because the libglib2.0-0 -await
trigger requires a newer dpkg than the one in Ubuntu 14.04. (LP: #1784065)

 -- Brian Murray   Mon, 30 Jul 2018 08:29:26 -0700

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Xenial:
  Fix Released

Bug description:
  [Test case]
  Verify that a release-upgrade of an Ubuntu desktop works from trusty to 
xenial with -proposed enabled.

  Package failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul 27 18:31:08 2018
  DuplicateSignature:
   package:libglib2.0-0:2.48.2-0ubuntu3
   Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack):
    triggers ci file contains unknown directive `interest-await'
  ErrorMessage: triggers ci file contains unknown directive `interest-await'
  InstallationDate: Installed on 2015-03-31 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: 
triggers ci file contains unknown directive `interest-await'
  UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions

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

[Desktop-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

2018-08-02 Thread Curtis Gedak

I tried using OpenGL and EGL for the compositor, but unfortunately EGL
has issues.  More specifically with EGL I experienced an inability to
login due to SDDM login screen hangs.  This is similar to the issue I
experienced with XRender [1] which I noted earlier in this report.

[1] https://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-
screen-hangs/

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Triaged

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For

[Desktop-packages] [Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor

2018-08-02 Thread David Robbe

Just to follow up on this issue. I just realized that if you install 
gnome-tweak tool 
[sudo apt install gnome-tweak-tool] you can actually choose between coherent or 
independent behavior of your multiple monitors across workspaces.

Once installed, launch tweak and then click on workspaces. then choose "
Workspaces span displays"  (instead of the default choice "Workspaces on
primary display only" !)

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

Title:
  Ubuntu 18.04 Workspaces only change on primary monitor

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  After connecting an external monitor to the laptop:

  - the 4 workspaces that I could access using keyboard shortcuts seem to have 
been reduced to only 2
  - the 'workspace' does not appear to be changeable on the external 
(secondary) monitor

  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: Sat Apr 28 12:42:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-28 (0 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/1767564/+subscriptions

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

This bug was fixed in the package ubuntu-drivers-common - 1:0.5.3

---
ubuntu-drivers-common (1:0.5.3) cosmic; urgency=medium

  * gpu-manager.(c|py):
- Set automatic pci power management when the dGPU is disabled (LP: 
#1778011).
- Load the nvidia modules when switching to performance mode.
- Do not skip unbound devices.
- Make remove_prime_outputclass() void.
- Report failures in enable_power_management().
- Look for blacklisted modules in /lib/modprobe.d too.
- Report failure when the nvidia modules cannot be unloaded,
  kill the main display session created by gdm3, and try
  unloading the nvidia modules once again.
  * gpu-manager.service:
- Start before oem-config.service.

 -- Alberto Milone   Thu, 02 Aug 2018
15:45:42 +0200

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in gdm3 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-prime source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  
  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  
  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

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

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

[Desktop-packages] [Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

2018-08-02 Thread Brian Murray

** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

Status in glib2.0 package in Ubuntu:
  Invalid
Status in glib2.0 source package in Xenial:
  Fix Released

Bug description:
  [Test case]
  Verify that a release-upgrade of an Ubuntu desktop works from trusty to 
xenial with -proposed enabled.

  Package failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul 27 18:31:08 2018
  DuplicateSignature:
   package:libglib2.0-0:2.48.2-0ubuntu3
   Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack):
    triggers ci file contains unknown directive `interest-await'
  ErrorMessage: triggers ci file contains unknown directive `interest-await'
  InstallationDate: Installed on 2015-03-31 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: 
triggers ci file contains unknown directive `interest-await'
  UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions

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

[Desktop-packages] [Bug 1071593]

2018-08-02 Thread Gitlab-migration

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/60.

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

Title:
  padsp segfaults in VLC call to freopen()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  vlc segfaults when i launch it with:

  PULSE_SERVER=localhost:4716 ALSA_PCM_NAME=pulse padsp vlc /dev/cdrom
  >>/tmp/vlc.$$.ort 2>&1

  and if i just launch it with "vlc", it shows a window with a orange
  striped cone, i select media->open disc, and the window ceases to
  render, staying all grey.

  works fine in natty.

  failures are in freshly installed (and updated) quantal:

  ii  vlc  2.0.4-0ubuntu1
  i386 multimedia player and streamer

  reinstalled from scratch, same result.

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

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

[Desktop-packages] [Bug 1458947]

2018-08-02 Thread Gitlab-migration

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/200.

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

Title:
  QinHeng Electronics CH345 MIDI adapter triggers error

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Cheap oriental MIDI adapter starts up with the following error, but
  works as expected.*

  E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
  (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
  deferred_volume=yes use_ucm=yes card_properties="module-udev-
  detect.discovered=1""): initialization failed.

  The device:
  1a86:752d QinHeng Electronics CH345 MIDI adapter

  Of course i'm not sure whether this is a PA problem or an ALSA or UDEV
  bug.

  Ubuntu 14.04.2 LTS
  Pulseaudio 1:4.0-0ubuntu11.1

  *  works almost as expected: there is one physical input and one
  output, but in ALSA one input and two outputs appear.

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

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

[Desktop-packages] [Bug 1071593] Re: padsp segfaults in VLC call to freopen()

2018-08-02 Thread Bug Watch Updater

** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  padsp segfaults in VLC call to freopen()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  vlc segfaults when i launch it with:

  PULSE_SERVER=localhost:4716 ALSA_PCM_NAME=pulse padsp vlc /dev/cdrom
  >>/tmp/vlc.$$.ort 2>&1

  and if i just launch it with "vlc", it shows a window with a orange
  striped cone, i select media->open disc, and the window ceases to
  render, staying all grey.

  works fine in natty.

  failures are in freshly installed (and updated) quantal:

  ii  vlc  2.0.4-0ubuntu1
  i386 multimedia player and streamer

  reinstalled from scratch, same result.

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

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

[Desktop-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error

2018-08-02 Thread Bug Watch Updater

** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  QinHeng Electronics CH345 MIDI adapter triggers error

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Cheap oriental MIDI adapter starts up with the following error, but
  works as expected.*

  E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
  (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
  deferred_volume=yes use_ucm=yes card_properties="module-udev-
  detect.discovered=1""): initialization failed.

  The device:
  1a86:752d QinHeng Electronics CH345 MIDI adapter

  Of course i'm not sure whether this is a PA problem or an ALSA or UDEV
  bug.

  Ubuntu 14.04.2 LTS
  Pulseaudio 1:4.0-0ubuntu11.1

  *  works almost as expected: there is one physical input and one
  output, but in ALSA one input and two outputs appear.

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

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-08-02 Thread Sebastien Bacher

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

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in gdm3 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-prime source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  
  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  
  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

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

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

[Desktop-packages] [Bug 1784065] Update Released

2018-08-02 Thread Łukasz Zemczak

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

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

Title:
  upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Xenial:
  Fix Released

Bug description:
  [Test case]
  Verify that a release-upgrade of an Ubuntu desktop works from trusty to 
xenial with -proposed enabled.

  Package failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul 27 18:31:08 2018
  DuplicateSignature:
   package:libglib2.0-0:2.48.2-0ubuntu3
   Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack):
    triggers ci file contains unknown directive `interest-await'
  ErrorMessage: triggers ci file contains unknown directive `interest-await'
  InstallationDate: Installed on 2015-03-31 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: 
triggers ci file contains unknown directive `interest-await'
  UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions

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

[Desktop-packages] [Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server

** Merge proposal linked:
   https://code.launchpad.net/~awe/network-manager/+git/ubuntu/+merge/352119

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

Title:
  NetworkManager not able to manage WWAN devices in 18.04 server

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Installed a 18.04 server image, and installed NetworkManager.

  NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10
  -globally-managed-devices.conf" file where it speciefies that all
  devices are by default unmanaged except for types "wifi" and "wwan".

  Now, the problem is that the filter should apply to "gsm" or "cdma"
  types, not "wwan".

  E.g.:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Before the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  eth0  ethernet  unmanaged  -- 
  cdc-wdm0  gsm   unmanaged  -- 
  loloopback  unmanaged  -- 

  After the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  cdc-wdm0  gsm   connected  cell   
  eth0  ethernet  unmanaged  -- 
  loloopback  unmanaged  --

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

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

[Desktop-packages] [Bug 1712661] Re: gnome-shell crash using ubuntu-dock with dual monitors

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
63ubuntu1

---
gnome-shell-extension-ubuntu-dock (63ubuntu1) cosmic; urgency=medium

  * Merged with latest master
- Fix crash connecting/disconnecting monitors (LP: #1712661)
- showApps button label position (LP: #1784920)
- Add wrapper to properly run in both gnome-shell 3.28 and 3.29.90
- Update translations, fixed settings typos
  * Updated versioning to match with extensions.gnome.org
  * debian/gbp.conf:
- updated branches and tags settings accordingly

 -- Marco Trevisan (Treviño)   Thu, 02 Aug 2018
13:29:47 +0200

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gnome-shell crash using ubuntu-dock with dual monitors

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  To replicate on Artful daily on a laptop, plug in an external monitor
  with the external monitor to the right of the laptop and configure the
  external monitor as the primary display. On configuration it works ok,
  but on logging out and back in gnome-shell crashes.  The problem is
  only seen if the external monitor is the primary display.

  I think it likely that this is the same issue reported for dash-to-dock:
  https://github.com/micheleg/dash-to-dock/issues/493

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 20:29:17 2017
  InstallationDate: Installed on 2017-08-22 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170821)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1784023] Re: Update profiles for usrmerge

2018-08-02 Thread Dimitri John Ledkov

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

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in fwknop package in Ubuntu:
  New
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  New
Status in lightdm-remote-session-x2go package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  New
Status in surf package in Ubuntu:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  New
Status in strongswan package in Debian:
  New

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> _filter,
  ./usr.bin.man:  /bin/gzip rmCx -> _filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,

  above list might be incomplete

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

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

[Desktop-packages] [Bug 1784023] Re: Update profiles for usrmerge

This bug was fixed in the package apparmor - 2.12-4ubuntu7

---
apparmor (2.12-4ubuntu7) cosmic; urgency=medium

  * Cherry-pick upstream patch for usr-merge for useradd profile.
  * Update chromium-browser profile with latest from profiles project.
  * Fixes LP: #1784023

 -- Dimitri John Ledkov   Wed, 01 Aug 2018 15:20:51
+0100

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

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in fwknop package in Ubuntu:
  New
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  New
Status in lightdm-remote-session-x2go package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  New
Status in surf package in Ubuntu:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  New
Status in strongswan package in Debian:
  New

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> _filter,
  ./usr.bin.man:  /bin/gzip rmCx -> _filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,

[Desktop-packages] [Bug 1784920] Re: "Show applications" label is shown in the right in every dock orientation

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
63ubuntu1

---
gnome-shell-extension-ubuntu-dock (63ubuntu1) cosmic; urgency=medium

  * Merged with latest master
- Fix crash connecting/disconnecting monitors (LP: #1712661)
- showApps button label position (LP: #1784920)
- Add wrapper to properly run in both gnome-shell 3.28 and 3.29.90
- Update translations, fixed settings typos
  * Updated versioning to match with extensions.gnome.org
  * debian/gbp.conf:
- updated branches and tags settings accordingly

 -- Marco Trevisan (Treviño)   Thu, 02 Aug 2018
13:29:47 +0200

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  "Show applications" label is shown in the right in every dock
  orientation

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  From upstream bug: https://github.com/micheleg/dash-to-dock/issues/732

  [ Description ]

  Text for all other applications is normal I.E when dock is on bottom
  text is on top / dock on right text on left but Show applications is
  always to the right. Occurs for me in both ubuntu 16.04 and ubuntu
  18.04 using vanilla gnome.

  [ Test case ]

  - From gnome-control-center, set option to show the dock in the bottom of the 
screen
  - Mouse hover the "Show applications" icon
  - The popup should show

  [ Regression potential ]

  Fix has landed upstream and it's already available for g-s users, so I 
consider this pretty safe.
  Label could be not be shown in other dock orientations

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

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

[Desktop-packages] [Bug 1785063] [NEW] [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

2018-08-02 Thread Nathanael Inkson

Public bug reported:

No sound at all, through speakers or headphones jack.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  natty  4286 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Aug  2 15:07:12 2018
InstallationDate: Installed on 2017-10-12 (293 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1248 F pulseaudio
  natty  4286 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to bionic on 2018-04-04 (120 days ago)
dmi.bios.date: 06/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02HAC.004.170626.WY.1442
dmi.board.asset.tag: No Asset Tag
dmi.board.name: SM-W720NZKBBTU
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8766A2S-C01-G001-S0001+10.0.14393
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02HAC.004.170626.WY.1442:bd06/26/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook12:pvrP02HAC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W720NZKBBTU:rvrSGL8766A2S-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
dmi.product.family: SAMSUNG GALAXY
dmi.product.name: Galaxy Book 12
dmi.product.version: P02HAC
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-13T14:38:49.320280

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound at all, through speakers or headphones jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  natty  4286 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug  2 15:07:12 2018
  InstallationDate: Installed on 2017-10-12 (293 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1248 F pulseaudio
natty  4286 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (120 days ago)
  dmi.bios.date: 06/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02HAC.004.170626.WY.1442
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W720NZKBBTU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8766A2S-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02HAC.004.170626.WY.1442:bd06/26/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook12:pvrP02HAC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W720NZKBBTU:rvrSGL8766A2S-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 12
  dmi.product.version: P02HAC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-13T14:38:49.320280

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

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

[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user's groups )

And this is the same output using the 'correct' scenario by logging into
the TTY console first.

cmdline: -bash 
 Tgid:  3516
Ngid:   0
Pid:3516
PPid:   3488
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
Groups: 0 4 6 7 20 24 25 27 29 44 46 100 108 114 132 134 134 137 142 1000 
NStgid: 3516
NSpid:  3516
NSpgid: 3516
NSsid:  3516

cmdline: -tmux 
 Tgid:  3488
Ngid:   0
Pid:3488
PPid:   1
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
Groups: 0 4 6 7 20 24 25 27 29 44 46 100 108 114 132 134 134 137 142 1000 
NStgid: 3488
NSpid:  3488
NSpgid: 3488
NSsid:  3488

cmdline: /sbin/init 
 Tgid:  1
Ngid:   0
Pid:1
PPid:   0
TracerPid:  0
Uid:0   0   0   0
Gid:0   0   0   0
Groups:  
NStgid: 1
NSpid:  1
NSpgid: 1
NSsid:  1

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

Title:
  Regression due to CVE-2018-1116 (processes not inheriting user's
  groups )

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  This report is tracking a possible regression caused by the recent
  CVE-2018-1116 patches to policykit-1.

  On 18.04, since package upgrades on July 23rd, and after the first
  reboot since then on Aug 1st, I hit an issue with the primary (sudo,
  adm, etc...) user getting Permission Denied trying to do:

  tail -f /var/log/syslog

  when that file is owned by syslog:adm and is g=r.

  I then found that "groups" reports only the $USER and not the entire
  list, but "groups $USER" reports all the groups correctly.

  The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g
  default-shell /bin/bash"

  After changing the user's shell back to /bin/bash and logging in on
  tty1 the list of groups shows correctly for the /bin/bash process
  running on tty1.

  I investigated and found that for the affected processes, such as the
  tmux process, /proc/$PID/loginuid = 4294967295  whereas the /bin/bash
  process on tty1 correctly reported 1000. The same with the respective
  gid_map and uid_map.

  4294967295 == -1 == 0x

  The recent CVE patch to policykit has several functions where it does
  "uid = -1" which seems to tie in to my findings so far.

  I also noticed Ubuntu is still based on version 0.105 which was
  released in 2012 - upstream released 0.115 with the CVE patch.

  I suspect the backporting has missed something.

  The Ubuntu backport patch is:

  https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu
  /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935

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

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

[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

2018-08-02 Thread Saurabh

Same issue on my Lenovo G50-80 running Ubuntu 18.04. Please let me know
if there's any other information I can post that would help rectify
this.

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user's groups )

Just noticed the PID tree trace didn't match on the Group: from
proc/$PID/status. Here's the corrected output.

$ pid=$BASHPID; while [[ $pid -ne 0 ]]; do ids=$(grep
'^\(.*id:\|Group\)' /proc/$pid/status); echo -e "cmdline: $(cat
/proc/$pid/cmdline) \n $ids" 2>/dev/null; pid=$(echo $ids | awk '{print
$8}'); done

cmdline: -bash 
 Tgid:  3610
Ngid:   0
Pid:3610
PPid:   3548
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
Groups:  
NStgid: 3610
NSpid:  3610
NSpgid: 3610
NSsid:  3610

cmdline: tmux 
 Tgid:  3548
Ngid:   0
Pid:3548
PPid:   1
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
Groups:  
NStgid: 3548
NSpid:  3548
NSpgid: 3548
NSsid:  3548

cmdline: /sbin/init 
 Tgid:  1
Ngid:   0
Pid:1
PPid:   0
TracerPid:  0
Uid:0   0   0   0
Gid:0   0   0   0
Groups:  
NStgid: 1
NSpid:  1
NSpgid: 1
NSsid:  1

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

Title:
  Regression due to CVE-2018-1116 (processes not inheriting user's
  groups )

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  This report is tracking a possible regression caused by the recent
  CVE-2018-1116 patches to policykit-1.

  On 18.04, since package upgrades on July 23rd, and after the first
  reboot since then on Aug 1st, I hit an issue with the primary (sudo,
  adm, etc...) user getting Permission Denied trying to do:

  tail -f /var/log/syslog

  when that file is owned by syslog:adm and is g=r.

  I then found that "groups" reports only the $USER and not the entire
  list, but "groups $USER" reports all the groups correctly.

  The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g
  default-shell /bin/bash"

  After changing the user's shell back to /bin/bash and logging in on
  tty1 the list of groups shows correctly for the /bin/bash process
  running on tty1.

  I investigated and found that for the affected processes, such as the
  tmux process, /proc/$PID/loginuid = 4294967295  whereas the /bin/bash
  process on tty1 correctly reported 1000. The same with the respective
  gid_map and uid_map.

  4294967295 == -1 == 0x

  The recent CVE patch to policykit has several functions where it does
  "uid = -1" which seems to tie in to my findings so far.

  I also noticed Ubuntu is still based on version 0.105 which was
  released in 2012 - upstream released 0.115 with the CVE patch.

  I suspect the backporting has missed something.

  The Ubuntu backport patch is:

  https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu
  /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935

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

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

[Desktop-packages] [Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor

2018-08-02 Thread David Robbe

Totally agree with Bruce!
I have two monitors. Let say I use LibreOffice on the left (primary) monitor 
and a reference manager on the right monitor.
When I switch workspace (let say to do some programming) I don' t expect that 
the reference manager keeps appearing?

This should be fixed. Or at least the possibility to have a coherence
behavior of multiple monitors be an option.

Please .

Otherwise, Ubuntu is great (I just switch from OpenSUSE in which, by the
way,  multiple monitors switch coherently across workspaces) !!

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

Title:
  Ubuntu 18.04 Workspaces only change on primary monitor

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  After connecting an external monitor to the laptop:

  - the 4 workspaces that I could access using keyboard shortcuts seem to have 
been reduced to only 2
  - the 'workspace' does not appear to be changeable on the external 
(secondary) monitor

  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: Sat Apr 28 12:42:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-28 (0 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/1767564/+subscriptions

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

[Desktop-packages] [Bug 1780996] Re: Convert triggers to noawait

2018-08-02 Thread Ken VanDine

** Changed in: libreoffice (Ubuntu Xenial)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Convert triggers to noawait

Status in appstream package in Ubuntu:
  Fix Released
Status in bumblebee package in Ubuntu:
  Fix Released
Status in clutter-imcontext package in Ubuntu:
  Triaged
Status in django-countries package in Ubuntu:
  Fix Released
Status in dochelp package in Ubuntu:
  Fix Released
Status in dovecot package in Ubuntu:
  Fix Released
Status in fusiondirectory package in Ubuntu:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gosa package in Ubuntu:
  Won't Fix
Status in guile-2.0 package in Ubuntu:
  Fix Released
Status in guile-2.2 package in Ubuntu:
  Fix Released
Status in hicolor-icon-theme package in Ubuntu:
  Fix Released
Status in libomxil-bellagio package in Ubuntu:
  Triaged
Status in libreoffice package in Ubuntu:
  Fix Released
Status in ltsp package in Ubuntu:
  Fix Released
Status in mate-icon-theme package in Ubuntu:
  Fix Released
Status in maxima package in Ubuntu:
  Fix Released
Status in neurodebian package in Ubuntu:
  Fix Released
Status in nevow package in Ubuntu:
  Fix Released
Status in octave package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in pike7.8 package in Ubuntu:
  Fix Released
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in postgresql-common package in Ubuntu:
  Fix Released
Status in qgis package in Ubuntu:
  Fix Released
Status in reconf-inetd package in Ubuntu:
  Won't Fix
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in sphinx package in Ubuntu:
  Fix Released
Status in syslog-ng-incubator package in Ubuntu:
  Fix Released
Status in tex-common package in Ubuntu:
  Fix Released
Status in wokkel package in Ubuntu:
  Fix Released
Status in xpdf package in Ubuntu:
  Fix Released
Status in yorick package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Released
Status in bumblebee source package in Xenial:
  Fix Released
Status in clutter-imcontext source package in Xenial:
  Won't Fix
Status in django-countries source package in Xenial:
  Fix Released
Status in dochelp source package in Xenial:
  Fix Released
Status in dovecot source package in Xenial:
  Fix Released
Status in fusiondirectory source package in Xenial:
  Fix Released
Status in gdk-pixbuf source package in Xenial:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released
Status in gosa source package in Xenial:
  Won't Fix
Status in guile-2.0 source package in Xenial:
  Fix Released
Status in hicolor-icon-theme source package in Xenial:
  Fix Released
Status in libomxil-bellagio source package in Xenial:
  Triaged
Status in libreoffice source package in Xenial:
  Triaged
Status in ltsp source package in Xenial:
  Fix Released
Status in mate-icon-theme source package in Xenial:
  Fix Released
Status in maxima source package in Xenial:
  Fix Committed
Status in neurodebian source package in Xenial:
  Fix Released
Status in nevow source package in Xenial:
  Fix Released
Status in octave source package in Xenial:
  Fix Released
Status in packagekit source package in Xenial:
  Fix Released
Status in pike7.8 source package in Xenial:
  Fix Released
Status in pike8.0 source package in Xenial:
  Fix Released
Status in postgresql-common source package in Xenial:
  Fix Released
Status in qgis source package in Xenial:
  Fix Released
Status in reconf-inetd source package in Xenial:
  Won't Fix
Status in shared-mime-info source package in Xenial:
  Fix Released
Status in sphinx source package in Xenial:
  Fix Released
Status in syslog-ng-incubator source package in Xenial:
  Fix Released
Status in tex-common source package in Xenial:
  Fix Released
Status in wokkel source package in Xenial:
  Fix Released
Status in xpdf source package in Xenial:
  Fix Released
Status in yorick source package in Xenial:
  Fix Released
Status in appstream source package in Bionic:
  Fix Released
Status in bumblebee source package in Bionic:
  Fix Released
Status in clutter-imcontext source package in Bionic:
  Won't Fix
Status in django-countries source package in Bionic:
  Fix Released
Status in dochelp source package in Bionic:
  Fix Released
Status in dovecot source package in Bionic:
  Fix Released
Status in fusiondirectory source package in Bionic:
  Fix Released
Status in gdk-pixbuf source package in Bionic:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in gosa source package in Bionic:
  Won't Fix
Status in guile-2.0 source package in Bionic:
  Fix Released
Status in guile-2.2 source package in Bionic:
  Fix Released
Status in hicolor-icon-theme source package in Bionic:
  Fix Released
Status in

[Desktop-packages] [Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts

2018-08-02 Thread Dariusz Gadomski

Although I originally shared Daniel's doubt, I reported it to Debian and
shared the patch (bug linked above).

** Bug watch added: Debian Bug tracker #905277
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905277

** Also affects: gdm3 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905277
   Importance: Unknown
   Status: Unknown

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

Title:
  GDM blocks SIGUSR1 used in PAM scripts

Status in gdm3 package in Ubuntu:
  In Progress
Status in gdm3 source package in Xenial:
  New
Status in gdm3 source package in Bionic:
  New
Status in gdm3 source package in Cosmic:
  In Progress
Status in gdm3 package in Debian:
  Unknown

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/399

  [Impact]
  GDM blocks SIGUSR1 for it's processes, since this is used in communication 
with X. This signal is later unblocked, however it happens after PAM
  interaction, so if PAM depends on this signal in any way it will get blocked.
  The issue has been fixed upstream.

  [Test Case]
  1. Prepare a setup described in Other Info using the attached scripts.
  2. Log in.
  3. Check logs /tmp/auth.log.

  Expected result: SIGUSR1 has been received.
  Actual result: SIGUSR1 never reaches the process.

  [Regression Potential]
  If there were components depending on SIGUSR1 their behavior may change - 
features that were inactive before may be triggered.

  [Other Info]

   Original bug description:

  In case of the following scenario:
  1. PAM configured to run auth and session with pam_exec scripts synchronizing 
via SIGUSR1
  2. Using GDM as the login manager causes SIGUSR1 never reaches the target 
scripts.

  Workaround:
  a) Use SIGUSR2 in the scripts.
  b) Comment out block_sigusr1() call in daemon/main.c.

  To reproduce add the following entries:
  /etc/pam.d/common-auth:
  auth  optionalpam_exec.so log=/tmp/auth.log expose_authtok quiet 
/usr/local/bin/auth.py

  /etc/pam.d/common-session:
  session   optional  pam_exec.so   log=/tmp/session.log  
/usr/local/bin/session.py

  Attaching example scripts.
  When using SIGUSR1 - sigusr1_handler is never called, with SIGUSR2 it is 
called without issues.

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

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

[Desktop-packages] [Bug 1781716] Re: package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of file on stdin at conffile prompt

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

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

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I do not know, there is a bug report, but it is the system, I do not
  understand anything

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.5
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Jul 12 07:47:13 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-02-21 (142 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat:
   device for ML-1660-Series: 
usb://Samsung/ML-1660%20Series?serial=Z4S2BKDZB05423Y.
   device for Stylus-CX5600: usb://EPSON/Stylus%20CX5600?serial=0=1
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles:
   ML-1660-Series: Samsung ML-1660, 2.0.0
   Stylus-CX5600: Epson Stylus CX5600 - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=220f47cc-2dd0-4ffb-9a2d-677aaa1a535c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=220f47cc-2dd0-4ffb-9a2d-677aaa1a535c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pam.d.cups:
   @include common-auth
   @include common-account
   @include common-session
  modified.conffile..etc.ufw.applications.d.cups:
   [CUPS]
   title=Common UNIX Printing System server
   description=CUPS is a printing system with support for IPP, samba, lpd, and 
other protocols.
   ports=631
  mtime.conffile..etc.apparmor.d.usr.sbin.cupsd: 2016-03-25T14:42:02
  mtime.conffile..etc.cups.cups-files.conf: 2016-03-25T14:41:32
  mtime.conffile..etc.init.cups.conf: 2016-03-25T14:42:00
  mtime.conffile..etc.init.d.cups: 2016-02-13T12:37:50
  mtime.conffile..etc.logrotate.d.cups-daemon: 2016-02-13T12:37:50
  mtime.conffile..etc.pam.d.cups: 2016-02-13T12:37:50
  mtime.conffile..etc.ufw.applications.d.cups: 2016-03-25T14:42:02

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

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

[Desktop-packages] [Bug 1785060] [NEW] Evince cannot open cbr-files based on rar v5

2018-08-02 Thread gustl

Public bug reported:

Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv 
(application/vnd.rar) wird nicht unterstützt."
CBR-Files based on other rar-Types, e.g. rarv4 works fine.

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

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

Title:
  Evince cannot open cbr-files based on rar v5

Status in evince package in Ubuntu:
  New

Bug description:
  Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp 
RAR-Archiv (application/vnd.rar) wird nicht unterstützt."
  CBR-Files based on other rar-Types, e.g. rarv4 works fine.

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

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

[Desktop-packages] [Bug 1674089] Re: Tamil 99 keyboard layout

2018-08-02 Thread Balaji பாலாஜி

Tamil99 is an important keyboard layout. Please add them natively for
typing. Its already available in apple natively.

I can do any help in keyboard mapping. Kindly let me know how to add
this keyboard layout.

** Tags added: type

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

Title:
  Tamil 99 keyboard layout

Status in ibus-m17n package in Ubuntu:
  Confirmed

Bug description:
  Tamil 99 keyboard layout which is the default keyboard layout prescribed by 
the Indian State of Tamil Nadu is not present. Selecting Tamil layout selects 
the Tamil Inscript layout which is prescribed by the Government of India.
  However, considering that Tamil is used only in the state of Tamil Nadu and 
that most keyboards are manufactured with Tamil 99, the layout by the Tamil 
Nadu government is the only one sold currently (usually by a company called 
TVS-e). This can be verified by Googling for Tamil+English bilingual keyboards. 
The current Inscript layout is useless for actual users and the lack of Tamil 
99 layout forces people to switch to Google Input tools.

  I have observed this on Ubuntu 16.04.2 LTS

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

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

[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user's groups )