[Desktop-packages] [Bug 1760603] Re: chromium-browser crashed with SIGABRT

[Olivier Tilloy]

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

** This bug is no longer a duplicate of private bug 1760425
** This bug has been marked a duplicate of bug 1729963
   chromium-browser crashed in OnConnectionDisconnectedFilter()

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  No idea why this is coming up.  This crash occurs right after boot
  even before Chrome has been started.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEadMiEGEBABQaAQOAMBt4Knylo1ROoCcSUFS37wDRwIFAgYCVALMAcU+BwIEAAjqAGHE4LUBYLEUA2wsRAAAe/wBHNUxNVEYwOTAzODQK/QAySxhTEQAKICAgICAg/ABBU1VTIFZTMjI5CiAgAI0=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 
1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 
800x600 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Sun Apr  1 21:02:19 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-02-02 (58 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202)
  Load-Avg-1min: 0.59
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=a3446b0a-57a5-444a-8114-a13f3a126610 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1760551] Re: chromium-browser crashed with SIGABRT in dbus_connection_dispatch()

[Olivier Tilloy]

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

** This bug is no longer a duplicate of private bug 1760425
** This bug has been marked a duplicate of bug 1729963
   chromium-browser crashed in OnConnectionDisconnectedFilter()

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

Title:
  chromium-browser crashed with SIGABRT in dbus_connection_dispatch()

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  None

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-LVDS-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAwrhFTAQOAGhB46rqVl1lVjCchUFQBAQEBAQEBAQEBAQEBAQEBEhsAgFAgFDAYIEQABaMQAAAfkxYAgFAgFDAYIEQABaMQAAAfDwCBCjyBCjIWCQAw5PAB/gBMUDEyMVdYMy1UTEMxAKw=
   modes: 1280x800 1280x800
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Mon Mar 26 17:33:21 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 17984 bytes, mtime: Fri Mar 30 10:21:27 2018)
  Load-Avg-1min: 1.29
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 3626AC9
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ec9530a0-ae18-4ab4-a6f4-b46c2e0f97c4 ro quiet splash
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   dbus_connection_dispatch () from /lib/i386-linux-gnu/libdbus-1.so.3
   ?? ()
  Title: chromium-browser crashed with SIGABRT in dbus_connection_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626AC9
  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:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3626AC9:pvrThinkPadX201:rvnLENOVO:rn3626AC9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626AC9
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

[Daniel van Vugt]

Bug 1760448 is from the login screen:
"CurrentDesktop: GNOME-Greeter:GNOME"

So it is Wayland, not Xorg.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

[Per-Inge]

I also get this in Xorg.
My duplicate is #Bug 1760448

2018-04-03 5:40 GMT+02:00 swadesh Parasher <1748...@bugs.launchpad.net>:

> Yes, at least the bug I reported was from Ubuntu 18.04 which doesn't use
> Wayland by default.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1760448).
> https://bugs.launchpad.net/bugs/1748450
>
> Title:
>   gnome-shell crashed with SIGTRAP in _g_log_abort() from
>   g_log_default_handler() from default_log_handler(message="Connection
>   to xwayland lost") from g_logv() from g_log() from 
>
> Status in gnome-shell package in Ubuntu:
>   Triaged
>
> Bug description:
>   *** This is a duplicate of bug 1505409, but is being kept separate so
>   as to automatically collect duplicate reports since the stacktrace
>   signature has changed recently. Any resolution and discussion should
>   occur in bug 1505409. ***
>
>   See also:
>   https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988
> f78ecd0f95
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.26.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>   Uname: Linux 4.13.0-33-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: GNOME-Greeter:GNOME
>   Date: Thu Feb  8 23:50:23 2018
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2016-03-21 (690 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160307)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/false
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>_XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>() at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>   Title: gnome-shell crashed with signal 5
>   UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>   UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1748450/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760758] Re: /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin: pinyin.cpp:991\357\274\232bool pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme): \345\201\207\3

[Gunnar Hjalmarsson]

In 16.04 och 17.10 ibus-sunpinyin is the default IM for Simplified
Chinese through IBus, and ibus-libpinyin just an option available in
universe. Setting priority "Low".

** Also affects: im-config (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ibus-libpinyin (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ibus-libpinyin (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ibus-libpinyin (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: ibus-libpinyin (Ubuntu Bionic)
   Status: New => Fix Released

** No longer affects: im-config (Ubuntu Bionic)

** No longer affects: im-config (Ubuntu Artful)

** No longer affects: im-config (Ubuntu Xenial)

** No longer affects: im-config (Ubuntu)

** Changed in: ibus-libpinyin (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: ibus-libpinyin (Ubuntu Artful)
   Importance: Undecided => Low

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

Title:
  /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin:
  pinyin.cpp:991\357\274\232bool
  pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme):
  \345\201\207\350\256\276 \342\200\230(0)\342\200\231
  \345\244\261\350\264\245\343\200\202

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Xenial:
  New
Status in ibus-libpinyin source package in Artful:
  New
Status in ibus-libpinyin source package in Bionic:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ibus-libpinyin.  This problem was most recently seen with package version 
1.7.3-2, the problem page at 
https://errors.ubuntu.com/problem/93033df7be22fcd00507d4744cd85fe4a72b727f 
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/ibus-libpinyin/+bug/1760758/+subscriptions

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

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[Launchpad Bug Tracker]

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

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   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'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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

[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock

[Launchpad Bug Tracker]

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

Title:
  gnome-shell freezes after resume then unlock

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Often after resuming and then entering my password to unlock gnome-
  shell, when I press the enter key gnome-shell immediately freezes. The
  lock screen is still displayed, the mouse no longer responds, and the
  keys no longer respond (I can't even get a tty console with CTRL-ALT-
  Fn key). I have to perform a hard reset at this point because gnome-
  shell remains frozen even after leaving the PC alone for 15 minutes.

  I haven't been able to find any crash files or error logs.

  It seems that this freeze is much more likely to occur if I have
  changed location between suspending and resuming and am therefore
  connecting to a different wifi router. Once, however, it happened at
  home on the same router and I was able to log in via ssh from another
  machine (so only gnome-shell was frozen, not the kernel). However, I
  couldn't see any messages or reason that gnome-shell had crashed, so
  all I could do was reboot (any hints as to what I should try at this
  stage are welcome).

  Bug #1709994 looks similar but in that case a) the user is using Xorg,
  not Wayland, b) he also gets past the lock screen, and c) gnome-shell
  eventually restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:46:43 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago)

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

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

[Desktop-packages] [Bug 1746587] Re: my bug's

[Launchpad Bug Tracker]

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

Title:
  my bug's

Status in xorg package in Ubuntu:
  Expired

Bug description:
  see my bugs please. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jan 31 20:47:44 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RV710 [Radeon HD 4350/4550] 
[1458:21ae]
  InstallationDate: Installed on 2017-04-22 (284 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: Acer APF6/AST660/ASE560
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-B1
  dmi.board.name: E415SM
  dmi.board.vendor: Acer
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-B1:bd04/02/2007:svnAcer:pnAPF6/AST660/ASE560:pvr1.0:rvnAcer:rnE415SM:rvr1.0:cvnAcer:ct3:cvr:
  dmi.product.name: APF6/AST660/ASE560
  dmi.product.version: 1.0
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jan 31 20:43:32 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

[Tim Lunn]

OP said that this also affects Xubuntu and Lubuntu so its not likely
only gnome-settings-daemon involved here, since neither of them use it.

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

[swadesh Parasher]

Yes, at least the bug I reported was from Ubuntu 18.04 which doesn't use
Wayland by default.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760274] Re: videos are stuttering extremely

[Daniel van Vugt]

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

I expect to add more tasks to bug 1698270 for this...

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


** This bug has been marked a duplicate of bug 1698270
   Totem pauses and stutters during video playback even when CPU usage is low

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

Title:
  videos are stuttering extremely

Status in budgie-desktop package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  New

Bug description:
  I am using totem, stuttering are not in browser.
  After installation all works fine, any update has triggered it!

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Mar 31 10:42:00 2018
  InstallationDate: Installed on 2018-03-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180314)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

[Daniel van Vugt]

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

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

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.

[Daniel van Vugt]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Opinion => Triaged

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

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

Title:
  Desktop icons goes under the Dock, if the Dock is set to auto-hide.

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  This bug is found in Artful.

  Desktop icons goes under the Dock, if the Dock is set to auto-hide.

  Either the Dock should auto-hide on the Desktop as well, or the
  Desktop Icons should leave a margin with the same size of the Dock.

  This happen both horizontal and vertical Dock positions.

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

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

[Desktop-packages] [Bug 1760486] Re: Desktop icons under dock when auto-hide on

[Daniel van Vugt]

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

Let's discuss this in bug 1723117

** This bug has been marked a duplicate of bug 1723117
   Desktop icons goes under the Dock, if the Dock is set to auto-hide.

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

Title:
  Desktop icons under dock when auto-hide on

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Turn on auto-hide in gnome shell
  2. create a few icons on the desktop
  3. If required, right click on the desktop and do 'Organize desktop by name'

  Result: see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 01:09:37 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['firefox_firefox.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 
'gnome-system-monitor_gnome-system-monitor.desktop', 
'android-studio_android-studio.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  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/1760486/+subscriptions

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

[Desktop-packages] [Bug 1759929] Re: gnome-shell crashed with signal 5

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

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

  edgar@pichirila3:~$ sudo apt-cache policy 
  Archivos de paquetes:
   100 /var/lib/dpkg/status
   release a=now
   500 http://ppa.launchpad.net/wfg/0ad/ubuntu bionic/main i386 Packages
   release v=18.04,o=LP-PPA-wfg-0ad,a=bionic,n=bionic,l=0 A.D.,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/wfg/0ad/ubuntu bionic/main amd64 Packages
   release v=18.04,o=LP-PPA-wfg-0ad,a=bionic,n=bionic,l=0 
A.D.,c=main,b=amd64
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic/main i386 
Packages
   release v=18.04,o=LP-PPA-webupd8team-java,a=bionic,n=bionic,l=Oracle 
Java (JDK) 8 / 9 Installer PPA,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic/main amd64 
Packages
   release v=18.04,o=LP-PPA-webupd8team-java,a=bionic,n=bionic,l=Oracle 
Java (JDK) 8 / 9 Installer PPA,c=main,b=amd64
   origin ppa.launchpad.net
   500 https://packages.microsoft.com/repos/vscode stable/main amd64 Packages
   release o=vscode stable,a=stable,n=stable,l=vscode stable,c=main,b=amd64
   origin packages.microsoft.com
   500 https://deb.opera.com/opera-stable stable/non-free i386 Packages
   release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free,b=i386
   origin deb.opera.com
   500 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
   release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free,b=amd64
   origin deb.opera.com
   500 https://deb.nodesource.com/node_8.x bionic/main i386 Packages
   release o=Node Source,n=bionic,l=Node Source,c=main,b=i386
   origin deb.nodesource.com
   500 https://deb.nodesource.com/node_8.x bionic/main amd64 Packages
   release o=Node Source,n=bionic,l=Node Source,c=main,b=amd64
   origin deb.nodesource.com
   500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic/main i386 Packages
   release v=18.04,o=LP-PPA-libreoffice,a=bionic,n=bionic,l=LibreOffice 
Fresh,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic/main amd64 
Packages
   release v=18.04,o=LP-PPA-libreoffice,a=bionic,n=bionic,l=LibreOffice 
Fresh,c=main,b=amd64
   origin ppa.launchpad.net
   500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
   release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64
   origin dl.google.com
   500 http://storage.googleapis.com/bazel-apt stable/jdk1.8 amd64 Packages
   release o=Bazel Authors,n=stable,l=Bazel,c=jdk1.8,b=amd64
   origin storage.googleapis.com
   500 http://archive.canonical.com/ubuntu bionic/partner i386 Packages
   release v=18.04,o=Canonical,a=bionic,n=bionic,l=Partner 
archive,c=partner,b=i386
   origin archive.canonical.com
   500 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages
   release v=18.04,o=Canonical,a=bionic,n=bionic,l=Partner 
archive,c=partner,b=amd64
   origin archive.canonical.com
   500 http://ftp.usf.edu/pub/ubuntu bionic/universe i386 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=i386
   origin ftp.usf.edu
   500 http://ftp.usf.edu/pub/ubuntu bionic/universe amd64 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=amd64
   origin ftp.usf.edu
   500 http://ftp.usf.edu/pub/ubuntu bionic/multiverse i386 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=i386
   origin ftp.usf.edu
   500 http://ftp.usf.edu/pub/ubuntu bionic/multiverse amd64 Packages
   release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=amd64
   origin ftp.usf.edu
   500 

[Desktop-packages] [Bug 1760415] Re: gnome-shell crashed with SIGSEGV

[Daniel van Vugt]

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV inintel_miptree_supports_hiz() from 
needs_separate_stencil()

** Summary changed:

- gnome-shell crashed with SIGSEGV inintel_miptree_supports_hiz() from 
needs_separate_stencil()
+ gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from 
needs_separate_stencil()

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from
  needs_separate_stencil()

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

Bug description:
  Screen had automatically locked overnight. Bug report prompt appeared
  a few seconds after I logged in.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 10:24:03 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-10-23 (159 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8c18dbc870:mov(%rdi),%eax
   PC (0x7f8c18dbc870) ok
   source "(%rdi)" (0x0074) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-17 (14 days ago)
  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/1760415/+subscriptions

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

[Desktop-packages] [Bug 1759760] Re: Wayland: Out-of-memory results in unusable system.

[Daniel van Vugt]

Thanks.

Next step: Please report the bug upstream here:

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

And then tell use the ID of the new bug.

** Tags added: wayland wayland-session

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

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

Title:
  Wayland: Out-of-memory results in unusable system.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Please re-assign this bug report as needed:

  When I was using Xwindows if the system ran out of memory one of the
  applications that was running was killed. Now that I am using Wayland
  instead the mouse and the keyboard stop responding and using a hotkey
  in order to switch to a different virtual console doesn't work any
  more.

  My guess is that a process vital for wayland to work gets killed since
  wayland isn't obviously connected to the user experience in the view
  of many possible metrics.

  My computer is using intel embedded graphics. But as gnome-shell
  currently tends to occupy an additional megabyte per second (there is
  a second but ticket on launchpad for that) and as I get the bug
  reports for a mathematics program that is able to find big solutions,
  if needed I frequently read  "system becomes unresponsive" messages
  nowaday.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.0-0ubuntu1
  Uname: Linux 4.16.0-041600rc6-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 29 07:19:36 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  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/1759760/+subscriptions

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

[Desktop-packages] [Bug 1759548] Re: Authentication window is painted above the lock screen

[Daniel van Vugt]

Thanks.

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

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

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

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/166
+ 
  Reproduce:
  - Trigger a situation that requires authentication. For example open a 
terminal window and type "snap install" (without sudo)
  - Press Super + L to lock the screen
  
  Observe that the authentication window is shown on top of the lock
  screen.
  
  Expected behavior:
  Don't show the authentication box on top of the lock screen

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

Title:
  Authentication window is painted above the lock screen

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/166

  Reproduce:
  - Trigger a situation that requires authentication. For example open a 
terminal window and type "snap install" (without sudo)
  - Press Super + L to lock the screen

  Observe that the authentication window is shown on top of the lock
  screen.

  Expected behavior:
  Don't show the authentication box on top of the lock screen

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

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

[Desktop-packages] [Bug 1758107] Re: Firefox: View > Toolbars is Missing "Bookmarks Toolbar"

[Daniel van Vugt]

Great video, thanks.

The menu in the top bar is actually displayed by the shell, and
communicated from Firefox via 'libdbusmenu'. So I'm moving this bug
there. It's not a theme issue.

** Summary changed:

- View > Toolbars is Missing "Bookmarks Toolbar"
+ Firefox: View > Toolbars is Missing "Bookmarks Toolbar"

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

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

Title:
  Firefox: View > Toolbars is Missing "Bookmarks Toolbar"

Status in firefox package in Ubuntu:
  Confirmed
Status in libdbusmenu package in Ubuntu:
  Confirmed

Bug description:
  The "Bookmarks Toolbar" toggler is missing from the View > Toolbars
  menu in Firefox 59 on Ubuntu 16.04.4.

  Video:
  https://youtu.be/Josm0VqtUDQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 59.0.1+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1902 F pulseaudio
   /dev/snd/pcmC0D0p:   lonnie 1902 F...m pulseaudio
   /dev/snd/controlC0:  lonnie 1902 F pulseaudio
  BuildID: 20180316021607
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Mar 22 11:42:51 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-09 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.77.1 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.77.0/24 dev enp3s0  proto kernel  scope link  src 192.168.77.252  
metric 100
  NoProfiles: True
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1754691] Re: Missing IP address info in Gnome Network Indicator pulldown

[Daniel van Vugt]

An IP address is specific to a network interface, so one machine can
have many IP addresses. This is probably why the IP address information
is hidden behind the gear button for each network interface.

I agree this interface is unexpected after using Unity, but it does make
good design sense.

To see it go: Settings > Network > click on the gear button


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

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

Title:
  Missing IP address info in Gnome Network Indicator pulldown

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  
  In order to support end-users using Ubuntu over the telephone it is often 
necessary to request the user to tell you their IP address. In previous 
versions of ubuntu it was in two clicks Network, Network Status.

  For some reason this information is no longer available in 18.04LTS
  Beta 1. This makes it very difficult to support.

  It is unreasonable and not-secure for end users to be opening the
  terminal to identify the IP address. Even if that is how Windows does
  it, Ubuntu has always been better on supportability.

  Steps to reproduce:
  Click the combined Network, Volume, Power indicator dropdown
  Click Wired Connected
  Click Wired Settings

  No IP, MAC, Gateway information shown. No useful information at all in
  fact.

  What should happen:
  Click the Network Icon
  Click Network Information
  A dialog box (that you can copy paste from) with all the network information 
IP, MAC, Gateway are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-appindicator 18.04
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 14:42:16 2018
  Dependencies:
   
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  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/1754691/+subscriptions

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

[Desktop-packages] [Bug 1760341] Re: Intermittent freeze in display output, XPS 9530 with nouveau

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1756877
   High visual latency in 18.04 when using nouveau

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

Title:
  Intermittent freeze in display output, XPS 9530 with nouveau

Status in xorg package in Ubuntu:
  New

Bug description:
  Display output intermittently pauses for approximately a second,
  causing the system to appear "stuttery". During freezes mouse input
  doesn't seem to be registered and keyboard input is repeated, as
  though keys are being held down.

  Watching the journal via `journalctl -f`, the following message
  appears each time the problem occurs:

  Mar 31 20:16:18 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write 
of 0002 FAULT at 4188ac [ IBUS ]
  Mar 31 20:16:27 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write 
of 0002 FAULT at 4188ac [ IBUS ]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar 31 20:11:01 2018
  DistUpgraded: 2018-03-31 16:47:43,480 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05fe]
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe]
  InstallationDate: Installed on 2018-01-29 (61 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 15 9530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=58327001-b3e0-4118-a0e6-03e8221a44f2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-03-31 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  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.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-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 986716] Re: Orca doesn't read the ubiquity promotional slides

[Simon Quigley]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 986716

and any other logs that are relevant for this particular issue.

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

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

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Status: New => Incomplete

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

Title:
  Orca doesn't read the ubiquity promotional slides

Status in gnome-orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Incomplete

Bug description:
  Release of Ubuntu: Ubuntu precise, 12.04
  Package Version: ubiquity 2.10.16, gnome-orca 3.4.0-0ubuntu2
  Expected Results: Orca should read the promotional slides while the 
installation is on progress
  Actual Results: Orca only keeps track of the percentage of the installation

  Probably the ubiquity slides are images, which explains why orca
  doesn't read them, it also doesn't explain in what step of the
  installation it's working, for example when copying file, it shouts
  the percentage, and when starts repartitioning, or installing others
  packages the percentage reading is reset and gives no clue about why
  it happened or in what part of the installation it is.

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

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

[Desktop-packages] [Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop

[Daniel van Vugt]

This bug has become a little overloaded.

Everyone please log your own bugs, and/or review the related bugs:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick

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

Title:
  [artful] mouse clicks are completely ignored both in Gnome's gdm and
  once logged in to the desktop

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 17.04 to 17.10, I encounter strange mouse issues,
  namely :

  - The mouse cursor moves allright

  - But mouse clicks are completely ignored both in Gnome's gdm and once
  logged in to the desktop, they are also ignored in all the Gnome panel
  and lef side dock.

  However, once started using keyboard, mouse DOES work INSIDE applications 
allright (all the times), and SOME windows can be moved by dragging their title 
bar when focus is given to them (i.e. I currently have a gedit window that I 
can move around with the mouse, while I cannot move a gnome-terminal or the 
firefox in which I type this text).
  Also, a directory/file selection dialog for the "save" action in gedit works 
perfectly well with the mouse.

  This is definitely not a hardware mouse issue.

  But I cannot change focus with the mouse, I have to [Alt]-[Tab] to
  change window.

  Also if I shift focus to the desktop, I can interact with icons on the
  desktop and the right-click on the background *may* work.

  I've purged all the .something config dirs in my homedir to no avail
  (and I don't believe it relates to it because gdm shows this behaviour
  even before I actually login).

  I've seen the exact same problem (after upgrade from 17.04 to 17.10)
  being reported on miscellaneous forums by at least 3 other people. So
  I'm not alone, but I have no clue.

  Trying to investigate this I checked a big part of my system's
  configuration and fell upon im-config.

  I have noticed that, when completely uninstalled (all the files that
  it refers to being removed), then reinstalled, this package actually
  FAILS installing any of its configuration files (but without any error
  message), resulting in the following situation :

  root@totor:~# dpkg -r --force depends im-config
  dpkg: im-config : problème de dépendance, mais suppression comme demandé :
   language-selector-gnome dépend de im-config (>= 0.29-1ubuntu10~).

  (Lecture de la base de données... 387605 fichiers et répertoires déjà 
installés.)
  Suppression de im-config (0.32-1ubuntu3) ...
  Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ...
  Traitement des actions différées (« triggers ») pour desktop-file-utils 
(0.23-1ubuntu3) ...
  Traitement des actions différées (« triggers ») pour gnome-menus 
(3.13.3-6ubuntu5) ...
  Traitement des actions différées (« triggers ») pour mime-support 
(3.60ubuntu1) ...

  
  root@totor:~# apt-get install im-config
  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les NOUVEAUX paquets suivants seront installés :
im-config
  0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 0 o/24,5 ko dans les archives.
  Après cette opération, 365 ko d'espace disque supplémentaires seront utilisés.
  Sélection du paquet im-config précédemment désélectionné.
  (Lecture de la base de données... 387551 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../im-config_0.32-1ubuntu3_all.deb ...
  Dépaquetage de im-config (0.32-1ubuntu3) ...
  Paramétrage de im-config (0.32-1ubuntu3) ...
  Traitement des actions différées (« triggers ») pour mime-support 
(3.60ubuntu1) ...
  Traitement des actions différées (« triggers ») pour desktop-file-utils 
(0.23-1ubuntu3) ...
  Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ...
  Traitement des actions différées (« triggers ») pour gnome-menus 
(3.13.3-6ubuntu5) ...

  
  root@totor:~# dpkg -V im-config
  ??5?? c /etc/X11/Xsession.d/70im-config_launch
  ??5?? c /etc/X11/xinit/xinputrc
  ??5?? c /etc/default/im-config
  ??5?? c /etc/profile.d/input-method-config.sh

  
  Any help greatly appreciated, my desktop being currently quite unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: im-config 0.32-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 09:42:24 2017
  EcryptfsInUse: Yes
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group 

[Desktop-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

[Daniel van Vugt]

Yes I can confirm that. But I think it should be discussed in a
different bug report.

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

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

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

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

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

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

[Desktop-packages] [Bug 1719408] Re: Application window outside of its frame in spread mode

[Daniel van Vugt]

And now tracking in:
https://bugzilla.gnome.org/show_bug.cgi?id=776588

:)

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

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

** Changed in: gnome-shell
   Status: Invalid => Unknown

** Changed in: gnome-shell
 Remote watch: GNOME Bug Tracker #792681 => GNOME Bug Tracker #776588

** Description changed:

  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/3
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/143
  https://bugzilla.gnome.org/show_bug.cgi?id=792681
+ https://bugzilla.gnome.org/show_bug.cgi?id=776588
  
  Test Case:
  1. On a workspace with no window, toggle spread mode (super key)
  2. Open a terminal with its keybinding: CTRL+ALT+T
  
  Expected result
  The terminal opens in the center of the screen with a frame around it
  
  Actual result
  The frame is displayed in the center of the screen but the application window 
is outside of the frame (cf screenshot)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin 1.14.0-1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 15:00:29 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed
   virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Application window outside of its frame in spread mode

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

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/3
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/143
  https://bugzilla.gnome.org/show_bug.cgi?id=792681
  https://bugzilla.gnome.org/show_bug.cgi?id=776588

  Test Case:
  1. On a workspace with no window, toggle spread mode (super key)
  2. Open a terminal with its keybinding: CTRL+ALT+T

  Expected result
  The terminal opens in the center of the screen with a frame around it

  Actual result
  The frame is displayed in the center of the screen but the application window 
is outside of the frame (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin 1.14.0-1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 

[Desktop-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

[Daniel van Vugt]

** Tags added: fixed-in-3.28.1

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

Title:
  two mouse cursors visible at the same time on rotated screen

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in wayland package in Fedora:
  Unknown

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/gnome-shell/+bug/1724977/+subscriptions

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

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Daniel van Vugt]

Yes I imagine gnome-shell contains multiple different leaks. Each
different leak will get a different upstream bug and a different fix.

So this bug may stay open indefinitely as more and more people jump on
board. Or we may have to cut it off at some point and use other bug
reports for specific cases.

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 

[Desktop-packages] [Bug 1751829] Re: chromium-browser crashed with signal 5 in ChromeMain()

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  chromium-browser crashed with signal 5 in ChromeMain()

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Was doing several things at a time (watching tv streaming, about 10
  chromium tabs opened with a few news streaming too.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 64.0.3282.167-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA2g4kCAQ8WAQMIXTV46qqqoFRGmCQOSEy/74CBQIHAi8CpQAEBAQEBAQEBAjqAGHE4LUBYLEUAogsyAAAe/QA4VR9LEQAKICAgICAg/ABNT04tU0lTMjg5CiAg/wBTTi0wMDAwMDAwMDEKAE4=
   modes: 1920x1080 1600x1200 1280x1024 1280x960 1360x768 1152x864 1280x720 
1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Mon Feb 26 14:42:41 2018
  Desktop-Session:
   'gnome-xorg'
   '/etc/xdg/xdg-gnome-xorg:/etc/xdg/xdg-gnome-xorg:/etc/xdg'
   
'/usr/share/gnome-xorg:/usr/share/gnome:/usr/share/gnome-xorg:/home/oem/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  Load-Avg-1min: 2.69
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=zygote\ 
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so\ 
--ppapi-flash-version=28.0.0.161
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  Signal: 5
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ChromeMain ()
  Title: chromium-browser crashed with signal 5 in ChromeMain()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV: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.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1693609] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click

[Daniel van Vugt]

The update that was released actually solved more subtle issues. It
didn't solve this bug, as was mentioned in
https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-
padding/+merge/342171


** Changed in: ubuntu-themes (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  The "Minimize", " Maximize" and "Close" buttons are too small to click

Status in Ubuntu UX:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  The window control buttons ( _  X ) in Ambiance are noticeably
  smaller than other icon buttons in the headerbar of a "native" GNOME3
  app.

  I think this is both a visual issue and an accessibility issue since
  it is harder to click the window control buttons than the other
  buttons. Please compare with Adwaita which has a much larger click
  area for the window control buttons.

  Commentary
  --
  Remember that one of the major strengths of GNOME 3 is that it is usable on a 
touch-enabled laptop.

  And while there are many people that complain about Adwaita, I believe
  many more actually like the proportions and padding of the default
  GNOME theme!

  ubuntu-themes  16.10+17.10.20170518-0ubuntu1
  Ubuntu 17.10 Alpha

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

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

[Desktop-packages] [Bug 1760745] Re: chromium-browser crashed with signal 5 in ChromeMain()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760745/+attachment/5099364/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760745/+attachment/5099373/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760745/+attachment/5099375/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760745/+attachment/5099376/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760745/+attachment/5099379/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760745/+attachment/5099380/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1751829
   chromium-browser crashed with signal 5 in ChromeMain()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with signal 5 in ChromeMain()

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  crashed under ubuntu 18.04 beta with all updates at 04/03/2018

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebQlM/iUIAAcWAQNsKRd46tAlolhVnCgPUFSnagAxT0VPYU+BwAEBAQEBAQEBZiFWqlEAHjBGjzMAmuYQAAAe/QA4Sx49CQAKICAgICAg/ABFMTk0MgogICAgICAg/wAyMDdORFJGRlEwMTQKAHY=
   modes: 1366x768 1280x720 1024x768 1024x768 832x624 800x600 800x600 800x600 
640x480 640x480 720x400
  Date: Tue Apr  3 04:04:59 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-04-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  Load-Avg-1min: 1.21
  Load-Processes-Running-Percent:   0.2%
  MachineType: Dell Inc. OptiPlex 780
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=zygote
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=d77dbc45-be54-42a9-93dc-7b4e32991704 ro quiet splash vt.handoff=1
  Signal: 5
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ChromeMain ()
  Title: chromium-browser crashed with signal 5 in ChromeMain()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0200DY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1197395] Re: /run/user/$ID/pulse owned by root and not by the user

[Daniel van Vugt]

This bug is closed. If you have any issues, please open a new bug.

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

Title:
  /run/user/$ID/pulse owned by root and not by the user

Status in elementary OS:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Saucy:
  Invalid
Status in systemd source package in Saucy:
  Fix Released
Status in systemd package in Fedora:
  Won't Fix

Bug description:
  I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a 
media player (I use Musique), it freezes, as it finds that it cannot write into 
/run/user/$ID/pulse.
  If I change the owner of that directory to me, the media player starts as 
usual and is able to play music.
  I've never had this problem with previous versions of Ubuntu.
  Someone says that running PulseAudio with the -D argument changes the owner 
of that directory, but I didn't try.

  This is before manually changing the owner of that directory:
  $ musique
  Failed to create secure directory (/run/user/1000/pulse): Permission denied+

  ... # it doesn't crash, it keeps waiting

  If needed:
  (dmesg attached)
  lspci:
  00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
  00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
  00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
  00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 
(rev 03)
  00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
  00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
  00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 
port SATA Controller [AHCI mode] (rev 03)
  02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter 
(PCI-Express) (rev 01)
  85:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8072 PCI-E 
Gigabit Ethernet Controller (rev 10)

  From /var/log/syslog:
  Jul  3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] core-util.c: 
Failed to create secure directory (/run/user/1000/pulse): Permission denied
  Jul  3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] main.c: 
User-configured server at 
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to 
start/autospawn.
  Jul  3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] core-util.c: 
Failed to create secure directory (/run/user/1000/pulse): Permission denied
  Jul  3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] main.c: 
User-configured server at 
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to 
start/autospawn.

  This is a fresh installation, I haven't updated it from a previous version. 
I'm using Ubuntu with Unity, not a derivative.
  These are my PPAs:
  canonical-qt5-edgers-qt5-proper-saucy.list
  dropbox.list
  dukto.list
  google-earth.list
  jd-team-jdownloader-saucy.list
  kivy-team-kivy-saucy.list
  mitya57-ppa-saucy.list
  numix-icon-theme-dev-utouch-saucy.list
  otto-kesselgulasch-gimp-saucy.list
  phablet-team-desktop-deps-saucy.list
  satyajit-happy-themes-saucy.list
  steam.list
  ubuntu-sdk-team-ppa-saucy.list
  ubuntutrucchi.list
  ubuntutrucchi-testing.list
  ubuntu-wine-ppa-saucy.list
  webupd8team-y-ppa-manager-saucy.list

  SRU INFORMATION
  ===
  TEST CASE:
  - Ensure that as a normal user "echo $XDG_RUNTIME_DIR" is something like 

[Desktop-packages] [Bug 1754445] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_ico

[Daniel van Vugt]

And in:
https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a

** Description changed:

  https://errors.ubuntu.com/problem/990288ee13e03a048791700aa0af1ccfaecd49bc
+ https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a
  
  ---
  
  i don´t know
  
  ProblemType: Crash
  DistroRelease: 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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  8 20:18:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
  
  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f921c91b510 :mov
(%rdi),%rax
   PC (0x7f921c91b510) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   cogl_object_unref () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in cogl_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_object_unref() from
  iter_remove_or_steal() from g_hash_table_iter_remove() from
  st_texture_cache_evict_icons() from on_icon_theme_changed()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/990288ee13e03a048791700aa0af1ccfaecd49bc
  https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a

  ---

  i don´t know

  ProblemType: Crash
  DistroRelease: 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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  8 20:18:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2018-03-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f921c91b510 :mov
(%rdi),%rax
   PC (0x7f921c91b510) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   cogl_object_unref () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in cogl_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760746] Re: /usr/bin/gnome-shell:11:cogl_object_unref:g_hash_table_remove_node:iter_remove_or_steal:g_hash_table_iter_remove:st_texture_cache_evict_icons

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1754445
   gnome-shell crashed with SIGSEGV in cogl_object_unref() from 
iter_remove_or_steal() from g_hash_table_iter_remove() from 
st_texture_cache_evict_icons() from on_icon_theme_changed()

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

Title:
  /usr/bin/gnome-
  
shell:11:cogl_object_unref:g_hash_table_remove_node:iter_remove_or_steal:g_hash_table_iter_remove:st_texture_cache_evict_icons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a 
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/1760746/+subscriptions

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

[Desktop-packages] [Bug 1760731] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from object_property_maybe_complete()

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
+ gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a() from g_object_ref() from 
object_property_maybe_complete()

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a() from g_object_ref() from
  object_property_maybe_complete()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Needed to logout and login again to get desktop working. After login,
  this crash report appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr  2 15:45:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-26 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6fdb853c0f 
:  mov(%rdx),%rdx
   PC (0x7f6fdb853c0f) ok
   source "(%rdx)" (0x1f0020) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760746] [NEW] /usr/bin/gnome-shell:11:cogl_object_unref:g_hash_table_remove_node:iter_remove_or_steal:g_hash_table_iter_remove:st_texture_cache_evict_icons

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a 
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-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic yakkety zesty

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

Title:
  /usr/bin/gnome-
  
shell:11:cogl_object_unref:g_hash_table_remove_node:iter_remove_or_steal:g_hash_table_iter_remove:st_texture_cache_evict_icons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/e4d313a6d362e991dc79947946d24a22a3a2f84a 
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/1760746/+subscriptions

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

[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

[Daniel van Vugt]

This bug is indeed meant to be wayland only. Which duplicates are from
Xorg?

Note that the login screen (gdm3) is using wayland by default. So your
system may report this crash even if you only use Xorg sessions.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760743] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760743/+attachment/5099348/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760743/+attachment/5099351/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760743/+attachment/5099352/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760743/+attachment/5099353/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760743/+attachment/5099354/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760743/+attachment/5099355/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  random crap in Thunderbird screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 08:41:51 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x555abff99311:mov0x90(%rbp),%rsi
   PC (0x555abff99311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  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-control-center/+bug/1760743/+subscriptions

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

[Desktop-packages] [Bug 1760073] Re: No network from suspend resume

[TJ]

Network issue is either kernel or Network Manager.

After the issue occurs we need to see the current 'dmesg' log (which
will show if devices resumed successfully) and /var/log/syslog (where
Network Manager is very verbose).

We also need to know which devices the system has:

lspci -nnk
lsusb

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

Title:
  No network from suspend resume

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following a resume from suspend - no network available on machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:53:22 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

[Jan Alexander]

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Needed to logout and login again to get desktop working. After login,
  this crash report appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr  2 15:45:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-26 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6fdb853c0f 
:  mov(%rdx),%rdx
   PC (0x7f6fdb853c0f) ok
   source "(%rdx)" (0x1f0020) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1756098] Re: Potential cache upgrade issue in 3.28 results in unable to install flatpakref due to remote already existing

[Andrew Hayzen]

Sure, when I get a moment I'll firstly try to reproduce the issue with
bionic by installing 3.27.92 and upgrading to 3.28 again. Then if I can
confirm that the issue really does happen, I'll try an upgrade from
artful (3.26.1). (I hope this was only an issue within the development
branch and therefore not affect "real" users, but we'll see).

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

Title:
  Potential cache upgrade issue in 3.28 results in unable to install
  flatpakref due to remote already existing

Status in gnome-software package in Ubuntu:
  New

Bug description:
  What happened
  1) Open your browser, navigate to flathub.org, find an app and click to 
install it
  2) Open the resulting flatpakref in gnome-software.
  3) Notice how the app info is correctly displayed
  4) Try to click install, notice how now you get "cannot install source from 
https://dl.flathub.org/repo/: flatpak source flathub already exists"

  Note that I have 3.27.92 installed first and then upgraded to 3.28.
  After removing all installed apps and remotes I have not been able to
  reproduce the issue. It has been suggested that it is an issue in
  cache cleanup between versions - probably within ~/.cache/gnome-
  software/flatpak/

  Furthermore note the actual issue was likely fixed in 3.28, so this is
  upgrades from lower than 3.28 to 3.28 which will be affected by cache
  upgrade issues.

  I have reported the bug upstream here https://gitlab.gnome.org/GNOME
  /gnome-software/issues/328

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

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

[Desktop-packages] [Bug 1587906] Guide et Comparatif des Balances Connectees

[Pascal Mons]

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

Guide et Comparatif des Balances Connectees
___

https://www.objetconnecte.net/comparatifs/comparatif-balance-connectee/

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

Title:
  GNOME Terminal 3.18.3 Xenial maximized windows does not return to its
  previous state when un-maximized

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  When a GNOME terminal is maximized then it is impossible to return to
  its initial size (UN-maximized), whatever the circumstances ...

  I have tried with tabs opened, without tabs, under different themes
  ...

  This is again very damaging to an Ubuntu LTS release, and this is the
  second GNOME 3.18.3 bug I report here in less than a week after
  installing Xenial 16.04. The previous one being gEdit.

  Will Ubuntu take care of these bugs ? As the typical answer from the
  GNOME team is that they have already moved to a newer release, so they
  won't provide any support on older versions ...

  The GNOME team appears to be highly unqualified to make stable
  releases of their software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 15:44:50 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-23 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  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/1587906/+subscriptions

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

[Desktop-packages] [Bug 1751147] Re: nvidia-304 kernel module failed to build with new bionic kernel [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?]

[victor00000]

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

my ubuntu 18.04 install nvidia-304 no work. :(

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

Title:
  nvidia-304 kernel module failed to build with new bionic kernel
  [error: implicit declaration of function ‘init_timer’; did you mean
  ‘init_timers’?]

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

Bug description:
  After updating to the 4.15.0-10-generic kernel today and rebooting,
  could log in but not do anything after that (got desktop image and
  conky, but no panel).  Returning to the prior kernel, everything was
  OK except apport popped up with this error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-304 304.137-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-10-generic
  Date: Thu Feb 22 15:30:32 2018
  DuplicateSignature: 
dkms:nvidia-304:304.137-0ubuntu2:/var/lib/dkms/nvidia-304/304.137/build/nv.c:3032:5:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2018-02-10 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  PackageVersion: 304.137-0ubuntu2
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.137-0ubuntu2: nvidia-304 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Michael Torres]

I was having this same issue after plugging in my screen. Oddly enough
this issue was resolved when I was trying to solve another issue about
screen locking up when opening a new application.

Here is the solution that fixed both issues.

https://support.displaylink.com/knowledgebase/articles/1843660-screen-
freezes-after-opening-an-application-only

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

[Mathieu St-Gelais]

I'm on Ubuntu 18.04, still beta, but fully updated, with dual screens on
two AMD R9 390, and it keeps happening after each login / screen unlock.

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in mutter package in Fedora:
  Fix Committed

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

  ---

  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/mutter/+bug/1731911/+subscriptions

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

[Desktop-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

[Gunnar Hjalmarsson]

@Pjotr12345: Thanks for the lesson on Dutch keyboards. :)

I can confirm that it's a regression compared to 16.04. On 16.04, if the
selected language matches the time zone location, a reasonable guess is
pre-set in the window for setting keyboard layout.

So if I select Nederlands and pretend to live in Haag, the installer
indeed suggests the us+intl layout.

This behavior was broken in 17.10, and I have a feeling that it's
related to the switch from unity-settings-daemon to gnome-settings-
daemon.

Compare:

http://bazaar.launchpad.net/~unity-settings-daemon-team/unity-settings-
daemon/trunk/view/head:/plugins/keyboard/gsd-keyboard-manager.c

with:

https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/blob/master/plugins/keyboard/gsd-keyboard-manager.c

The fix of bug #1719938 resulted in this patch:

https://bazaar.launchpad.net/~ubuntu-desktop/gnome-settings-
daemon/ubuntu/view/head:/debian/patches/ubuntu_ibus_configs.patch

which handles it for some locales which typically need input methods.
But for all other locales it simply defaults to the basic English (US)
layout.

As already mentioned, this may make the live session for many (most?)
languages disappointing. Typing is an essential part of the desktop
experience.

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Desktop-packages] [Bug 1760411] Re: I don know

[Simon Quigley]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug 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.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** 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/1760411

Title:
  I don know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i don know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr  1 16:29:14 2018
  DistUpgraded: 2018-03-31 14:06:35,805 DEBUG /openCache(), new cache size 86473
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80c1]
  InstallationDate: Installed on 2018-03-26 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-03-31 (1 days ago)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: HP
  dmi.board.version: 96.51
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd10/27/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Mar 31 13:56:55 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1759921] Re: Problem with Lexmark Optra E310: printing system doesn't work

[Carlos Rodriguez]

** Summary changed:

- printing system doesn't work
+ Problem with Lexmark Optra E310: printing system doesn't work

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

Title:
  Problem with Lexmark Optra E310: printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  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.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1760721] [NEW] Resolution is stuck at 640x480

[Diego Angel Osuna Carrasco]

Public bug reported:

This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 
resolution, this happened since the first boot. I researched and found in 
forums that xdiagnose provides a workaround by deactivating some graphics at 
boot, so I installed it and it worked, however, just as a workaround. I can 
change the resolution now, but the size of apps sometimes takes way more screen 
space than it should, and the screen flickers randomly. By selecting "inform 
errors" in xdiagnose I got a pop up message saying the computer is providing 3D 
by software instead of hardware, I don't know how to fix this, any guidance?
Let me know if you need more information.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic i686
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Apr  2 16:30:13 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA 
Display Adapter [1039:6330] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA 
Display Adapter [1025:0083]
InstallationDate: Installed on 2018-04-02 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release i386 (20180105)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer, inc. Aspire 3000
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a37feeb6-1e6a-47c6-b003-a161b5612912 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/06
dmi.bios.vendor: Acer
dmi.bios.version: 3A32
dmi.board.name: Lugano M
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvr3A32:bd02/20/06:svnAcer,inc.:pnAspire3000:pvrNotApplicable:rvnAcer,Inc.:rnLuganoM:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 3000
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Apr  2 16:18:06 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: apport-bug artful i386 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/1760721

Title:
  Resolution is stuck at 640x480

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 
resolution, this happened since the first boot. I researched and found in 
forums that xdiagnose provides a workaround by deactivating some graphics at 
boot, so I installed it and it worked, however, just as a workaround. I can 
change the resolution now, but the size of apps sometimes takes way more screen 
space than it should, and the screen flickers randomly. By selecting "inform 
errors" in xdiagnose I got a pop up message saying the computer is providing 3D 
by software instead of hardware, I don't know how to fix this, any guidance?
  Let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  CompizPlugins: No value set 

[Desktop-packages] [Bug 1730513] Re: [SRU artful] korganiser reminders do not trigger with 17.04.3

[Travis Odom]

Any chance for this to get into Artful? Reminders are extremely useful.

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

Title:
  [SRU artful] korganiser reminders do not trigger with 17.04.3

Status in Akonadi:
  Fix Released
Status in akonadi package in Ubuntu:
  Fix Released
Status in akonadi source package in Artful:
  In Progress
Status in akonadi source package in Bionic:
  Fix Released

Bug description:
  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic

  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.

  Seemingly upstream KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=384212

  With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

  
  *** SRU information ***

  [Impact]

   * An expected and relied on feature of KDE PIM (appointment and event
  reminders) shown on the desktop etc does not work.

   * Fix is a single non extensive commit that the upstream KDE
  developer considers is likely to be safe to backport.

  
  [Test Case]

   * Use korganiser to set a calendar item with a reminder

   * Make sure the organiser tray daemeon is running (koragc), and that
  reminders are enabled.

   * Test if a reminder is shown at the selected appropriate time
  relative to the event (can be a few mins delay in some cases)

   * In addition, generally test that adding, modifying, viewing event
  information works as before.

  * Test other KDE PIM applications as much as is practical

  [Regression Potential]

   * Single commit that upstream considers should not be problematic to
  backport.

   * As akonagi acts as the storage backend for PIM generally, it is
  unlikely but possible there could be unintended impacts. Testing of
  other parts of the PIM stack, as much as is practical is advisable.

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

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

[Desktop-packages] [Bug 1741119] Re: Software App crashed while in the background - was installing MATE Desktop via terminal

[Apport retracing service]

** Tags added: bugpattern-needed

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

Title:
  Software App crashed while in the background - was installing MATE
  Desktop via terminal

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Software App crashed while in the background - was installing MATE
  Desktop via terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 22:48:45 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171209)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_find_section_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1760711] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760711/+attachment/5099241/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760711/+attachment/5099244/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760711/+attachment/5099245/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760711/+attachment/5099246/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760711/+attachment/5099247/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760711/+attachment/5099248/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  happened after logging in to Ubuntu

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr  2 07:44:05 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760708] Re: Download Adobe Flash Player (apt-url). gnome-software crashed with signal 5 in g_main_context_new()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760708/+attachment/5099217/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760708/+attachment/5099220/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760708/+attachment/5099221/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760708/+attachment/5099222/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760708/+attachment/5099223/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760708/+attachment/5099224/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1741119
   Software App crashed while in the background - was installing MATE Desktop 
via terminal

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Download Adobe Flash Player (apt-url). gnome-software crashed with
  signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I download Adobe Flash Player from https://get.adobe.com/flashplayer/
  Linux 64-bit, English, Firefox with Apt for debian/ubuntu 
  When I click to download, I selected apt-url and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 22:54:12 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_find_section_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1760710] [NEW] package libreoffice-common (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете openoffice-debian-men

[voron]

Public bug reported:

in  system installed Apache OpenOffice 4.1.5. I`m install hyphen_Lt and
other packets for Russian and Lithuanian grammar from synaptic

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libreoffice-common (not installed)
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Mon Apr  2 22:11:23 2018
ErrorMessage: попытка перезаписать «/usr/bin/soffice», который уже имеется в 
пакете openoffice-debian-menus 4.1.5-9789
InstallationDate: Installed on 2018-03-28 (5 days ago)
InstallationMedia: Matuntu 18.04 - Release amd64
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: libreoffice
Title: package libreoffice-common (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете 
openoffice-debian-menus 4.1.5-9789
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете
  openoffice-debian-menus 4.1.5-9789

Status in libreoffice package in Ubuntu:
  New

Bug description:
  in  system installed Apache OpenOffice 4.1.5. I`m install hyphen_Lt
  and other packets for Russian and Lithuanian grammar from synaptic

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  2 22:11:23 2018
  ErrorMessage: попытка перезаписать «/usr/bin/soffice», который уже имеется в 
пакете openoffice-debian-menus 4.1.5-9789
  InstallationDate: Installed on 2018-03-28 (5 days ago)
  InstallationMedia: Matuntu 18.04 - Release amd64
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете 
openoffice-debian-menus 4.1.5-9789
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759833] Re: Update Greek translation for Firefox Desktop Action (firefox.desktop)

[Simos Xenitellis ]

** Tags added: l10n

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

Title:
  Update Greek translation for Firefox Desktop Action (firefox.desktop)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Please apply the attached patch that updates the Greek translation
  for the file "firefox/debian/firefox.desktop.in".

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

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

[Desktop-packages] [Bug 1730513] Re: [SRU artful] korganiser reminders do not trigger with 17.04.3

[Travis Odom]

Was this ever going to get pulled into Artful? "Reminders don't work at
all" seems like a big thing to just sit with an available fix for 5
months now

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

Title:
  [SRU artful] korganiser reminders do not trigger with 17.04.3

Status in Akonadi:
  Fix Released
Status in akonadi package in Ubuntu:
  Fix Released
Status in akonadi source package in Artful:
  In Progress
Status in akonadi source package in Bionic:
  Fix Released

Bug description:
  akonadi:  4:17.04.3-0ubuntu in artful and  4:17.04.3-0ubuntu1 and
  ubuntu2 in bionic

  When the korganizer tray daemon (koragc) is set to enable event
  reminders, these silently fail to appear.

  Seemingly upstream KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=384212

  With back-portable fix from the 17.08 branch:
  
https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08=d3c6ba904798768b0c83c2e182c27b1c624f78ca

  Test build for artful in:
  https://launchpad.net/~rikmills/+archive/ubuntu/akonadi-bug

  
  *** SRU information ***

  [Impact]

   * An expected and relied on feature of KDE PIM (appointment and event
  reminders) shown on the desktop etc does not work.

   * Fix is a single non extensive commit that the upstream KDE
  developer considers is likely to be safe to backport.

  
  [Test Case]

   * Use korganiser to set a calendar item with a reminder

   * Make sure the organiser tray daemeon is running (koragc), and that
  reminders are enabled.

   * Test if a reminder is shown at the selected appropriate time
  relative to the event (can be a few mins delay in some cases)

   * In addition, generally test that adding, modifying, viewing event
  information works as before.

  * Test other KDE PIM applications as much as is practical

  [Regression Potential]

   * Single commit that upstream considers should not be problematic to
  backport.

   * As akonagi acts as the storage backend for PIM generally, it is
  unlikely but possible there could be unintended impacts. Testing of
  other parts of the PIM stack, as much as is practical is advisable.

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

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

[Desktop-packages] [Bug 1759833] Re: Update Greek translation for Firefox Desktop Action (firefox.desktop)

[Launchpad Bug Tracker]

** Branch linked: lp:~simosx/firefox/l10n

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

Title:
  Update Greek translation for Firefox Desktop Action (firefox.desktop)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Please apply the attached patch that updates the Greek translation
  for the file "firefox/debian/firefox.desktop.in".

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

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

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

[chris pollock]

Gnome Shell crashed again just now while updating

Start-Date: 2018-04-02  15:38:42
Commandline: apt dist-upgrade
Requested-By: chris (1000)
Upgrade: openjdk-8-jre:amd64 (8u151-b12-0ubuntu0.16.04.2, 
8u162-b12-0ubuntu0.16.04.2), openjdk-8-jre-headless:amd64 
(8u151-b12-0ubuntu0.16.04.2, 8u162-b12-0ubuntu0.16.04.2)
End-Date: 2018-04-02  15:43:29

from the command line. This is getting to be an almost constant
occurrence, will this be fixed in 18.04?

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome Shell appeared to crash and then restart after doing software
  update.

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.18.5-0ubuntu0.2
Candidate: 3.18.5-0ubuntu0.2
Version table:
   *** 3.18.5-0ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 17:06:48 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (955 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   g_closure_invalidate () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invalidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756006] Re: FFe: Support suspend-to-hibernate

[Mario Limonciello]

The rename is done upstream, it's now suspend-then-hibernate.  I'm
uploading systemd with these patches.

As for G-S-D, I've adjusted it for the rename too but it's still waiting
to be merged.

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

** Summary changed:

- FFe: Support suspend-to-hibernate
+ FFe: Support suspend-then-hibernate

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

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

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

[Desktop-packages] [Bug 1759625] Re: Update gimp to 2.10

[Jeremy Bicha]

** Description changed:

+ Feature Freeze Justification
+ 
+ gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.
+ 
+ The Gimp development team is small enough that I do not expect there to
+ be much support at all for gimp 2.8 any more.
+ 
+ Future
+ ==
+ If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.
+ 
+ The Gimp developers have announced that they will add features to future
+ 2.10 releases so that users won't have to wait several years like this
+ again.
+ 
+ Gimp 3.0 will switch to gtk3 (or gtk4).
+ 
+ Changes
+ ===
+ This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS
+ 
+ Features are described in several blog posts documenting the 2.9
+ development releases at https://www.gimp.org/news/
+ 
+ Changes in the new Debian version
+ =
+ Uploaded to experimental on request of the Debian maintainer Ari Pollack.
+ 
+  gimp (2.10.0~RC1-1) experimental; urgency=medium
+  .
+* New upstream release candidate (LP: #1759625)
+  - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
+(LP: #1739684)
+* Bump dependencies per configure.ac
+* Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
+  libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
+  libwebp-dev, mypaint-brushes, python-cairo-dev
+* Depend on xdg-utils for email feature
+* Update debian/libgimp2.0.symbols
+* Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
+  with the new release

** Summary changed:

- Update gimp to 2.10
+ FFe: Sync gimp 2.10.0~RC1-1 (universe) from Debian experimental (main)

** Description changed:

  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.
  
  The Gimp development team is small enough that I do not expect there to
  be much support at all for gimp 2.8 any more.
  
  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.
  
  The Gimp developers have announced that they will add features to future
  2.10 releases so that users won't have to wait several years like this
  again.
  
  Gimp 3.0 will switch to gtk3 (or gtk4).
  
+ Affected Flavors
+ 
+ Ubuntu Studio is the only flavor to include gimp by default.
+ 
  Changes
  ===
  This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS
  
  Features are described in several blog posts documenting the 2.9
  development releases at https://www.gimp.org/news/
  
  Changes in the new Debian version
  =
  Uploaded to experimental on request of the Debian maintainer Ari Pollack.
  
-  gimp (2.10.0~RC1-1) experimental; urgency=medium
-  .
-* New upstream release candidate (LP: #1759625)
-  - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
-(LP: #1739684)
-* Bump dependencies per configure.ac
-* Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
-  libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
-  libwebp-dev, mypaint-brushes, python-cairo-dev
-* Depend on xdg-utils for email feature
-* Update debian/libgimp2.0.symbols
-* Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
-  with the new release
+  gimp (2.10.0~RC1-1) experimental; urgency=medium
+  .
+    * New upstream release candidate (LP: #1759625)
+  - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
+    (LP: #1739684)
+    * Bump dependencies per configure.ac
+    * Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
+  libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
+  libwebp-dev, mypaint-brushes, python-cairo-dev
+    * Depend on xdg-utils for email feature
+    * Update debian/libgimp2.0.symbols
+    * Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
+  with the new release

** Description changed:

  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.
  
- The Gimp development team is small enough that I do not expect there to
- be much support at all for gimp 2.8 any more.
+ The Gimp development team is so small that I do not expect there to be
+ much support at all for gimp 2.8 any more.
  
  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then 

[Desktop-packages] [Bug 491736] Re: nautilus takes a huge amount of memory when copy-pasting files

[Ads20000]

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

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

Title:
  nautilus takes a huge amount of memory when copy-pasting files

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus


  My system has 2GB of RAM and 4GB of swap. Nautilus is taking almost
  all of them. Top says 1781M virt and 1.2G res. This happens as I´m
  doing a backup of my external USB drive into another USB drive. Around
  1.000.000 files, with music, videos, text, and thousands and thousands
  of pictures. Copying from Ext3 to Ext4 partition, with a simple copy
  and paste.

  Copy speed decreased with time, starting around 16-17MB/sec now around
  11MB/sec.

  Serious bug. Copy & paste shouldn´t destroy a machine no matter how
  big the amount of files/total size. =(

  I posted this originally as a comment, but this is a different
  behaviour to the one described on the bug report that I posted on.

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

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

[Desktop-packages] [Bug 549629] Re: Feature request: Graphical method to mount selected drives within an encrypted LVM (made by altrnate installer)

[Ads20000]

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

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

Title:
  Feature request: Graphical method to mount selected drives within an
  encrypted LVM (made by altrnate installer)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  This bug is a request for a graphical method to mount selected drives
  within an encrypted LVM (made by alternate installer).

  What currently happens with LVM is that it is shown as two drives. One
  contains all the /boot file and is unprotected. The other (which is
  larger) contains my root drive (/) and my swap which are both
  encrypted.

  Nautilus presents it as:
  X.X GB Encrypted

  You can see this on the side pane or on the places menu, however, you
  cannot mount it from nautilus. This improvement should only affecting
  a LVM disk when booting from another disk (not when it is itself
  mounted and used as the system). More on that in Bug #441211 - Do not
  show LUKS devices of internal mounted disks.

  Currently what happens when clicking on the disk is the following
  error message shows up:

  Unable to mount X.X GB Encrypted
  Error starting job: Failed to execute child process "cryptsetup" (No such 
file or directory)

  
  What I expect, or would like to happen:
  When booting from a disk other then the one which is LVM setup (such as 
another partition, usb, Live CD), you would be presented with X.X GB Encrypted. 
Once you unlock the LVM, all the drives within it (with filesystems capable of 
being mounted) would be presented in the nautilus. The user can then select 
individual drives to mount them.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.29.92.1-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-17-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Sat Mar 27 11:03:05 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Desktop-packages] [Bug 1756098] Re: Potential cache upgrade issue in 3.28 results in unable to install flatpakref due to remote already existing

[Jeremy Bicha]

If you have time, could you try starting from Ubuntu 17.10, then upgrade
to 18.04 and see if you can reproduce the issue? You're welcome to use a
virtual machine to make testing easier.

** Tags added: bionic

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

Title:
  Potential cache upgrade issue in 3.28 results in unable to install
  flatpakref due to remote already existing

Status in gnome-software package in Ubuntu:
  New

Bug description:
  What happened
  1) Open your browser, navigate to flathub.org, find an app and click to 
install it
  2) Open the resulting flatpakref in gnome-software.
  3) Notice how the app info is correctly displayed
  4) Try to click install, notice how now you get "cannot install source from 
https://dl.flathub.org/repo/: flatpak source flathub already exists"

  Note that I have 3.27.92 installed first and then upgraded to 3.28.
  After removing all installed apps and remotes I have not been able to
  reproduce the issue. It has been suggested that it is an issue in
  cache cleanup between versions - probably within ~/.cache/gnome-
  software/flatpak/

  Furthermore note the actual issue was likely fixed in 3.28, so this is
  upgrades from lower than 3.28 to 3.28 which will be affected by cache
  upgrade issues.

  I have reported the bug upstream here https://gitlab.gnome.org/GNOME
  /gnome-software/issues/328

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

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

[Desktop-packages] [Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

[Jeremy Bicha]

Ok, I'll give you medium. Enjoy!

** Changed in: gnome-software (Ubuntu Artful)
   Importance: Low => Medium

** Changed in: gnome-software (Ubuntu)
   Importance: Low => Medium

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

Title:
  Unable to install flatpakref on Ubuntu artful

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  I saw a news article with a link to install a flatpak.

  http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4

  I clicked the link expecting to be able to install the flatpak, but
  the experience appears broken. I'm on an up to date Artful install

  What I did was:-

  Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4
  Click the flathub link:- 
https://flathub.org/repo/appstream/io.github.Pithos.flatpakref
  This downloaded the flatpakref file.
  I clicked the file in my browser, nothing happened

  I then tried finding the file in nautilus and double clicked it.
  GNOME Software launched and presented an error "Don't know how to handle 
'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot).

  If I search for pithos in GNOME Software I am able to find the older
  version from the deb repo, but not the newer version from flathub.

  Do we not support flatpak/flathub out of the box? Or is my system
  uniquely hosed?

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

-- 
Mailing list: https://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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Steve Langasek]

On Thu, Mar 29, 2018 at 06:27:18PM -, Alkis Georgopoulos wrote:

> For the maintainers of the affected packages to be able to help in this
> issue, addressing the main question already stated above would be most
> helpful:

> To support netplan, do we have to implement netlink events listeners 
> ourselves?
> I'm not sure all maintainers are willing to do that.

> Or is there another package that provides this functionality that we could
> rely on?  E.g.  NetworkManager does have a dispatcher.d directory that we
> can use, but does Ubuntu ship something similar (networkd-dispatcher?) in
> systems that don't use NetworkManager?

We are looking at integrating networkd-dispatcher for 18.04.

Many of these package tasks may become SRU material after 18.04 releases,
due to the timing.

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No 

[Desktop-packages] [Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

[Ads20000]

For those wondering: I should've realized this much earlier, the
importance being 'Low' is not some sort of anti-Flatpak conspiracy, it's
because the bug satisfies the criteria for Low importance as per:
https://wiki.ubuntu.com/Bugs/Importance

'Bugs that affect unusual end-user configurations or uncommon hardware
Bugs that affect a non-essential aspect and limited scope of the application
Non-ideal default configuration'

Though I think there's a case to make this higher importance:

'A bug that has a moderate impact on a core application' (Medium)
'Has a severe impact on a small portion of Ubuntu users (estimated)' (High)
'Renders essential features or functionality of the application or dependencies 
broken or ineffective' (High) - some would consider installing Flatpaks from 
their software center an 'essential feature', even if Flatpak and the plugin in 
question are in universe not main. (High)

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

Title:
  Unable to install flatpakref on Ubuntu artful

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  I saw a news article with a link to install a flatpak.

  http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4

  I clicked the link expecting to be able to install the flatpak, but
  the experience appears broken. I'm on an up to date Artful install

  What I did was:-

  Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4
  Click the flathub link:- 
https://flathub.org/repo/appstream/io.github.Pithos.flatpakref
  This downloaded the flatpakref file.
  I clicked the file in my browser, nothing happened

  I then tried finding the file in nautilus and double clicked it.
  GNOME Software launched and presented an error "Don't know how to handle 
'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot).

  If I search for pithos in GNOME Software I am able to find the older
  version from the deb repo, but not the newer version from flathub.

  Do we not support flatpak/flathub out of the box? Or is my system
  uniquely hosed?

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

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

[Desktop-packages] [Bug 1760670] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760670/+attachment/5099082/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760670/+attachment/5099086/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760670/+attachment/5099087/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760670/+attachment/5099088/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760670/+attachment/5099089/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760670/+attachment/5099090/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  *** This bug is a duplicate of bug 1754924 ***
  Used the control-center to install my Brother HL3140CW printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Mon Apr  2 20:12:05 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-01 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x55e545c23311:mov0x90(%rbp),%rsi
   PC (0x55e545c23311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  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-control-center/+bug/1760670/+subscriptions

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

[Desktop-packages] [Bug 1480143] Re: The organized files and folders are covered by Unity Launcher.

[Ads20000]

I can't reproduce this bug with Files 3.26 on Ubuntu 17.10 so I'm
assuming this is fixed, up to a Bug Control member to mark this as
affecting a particular series if it affects a supported release
(currently 14.04, 16.04, and 17.10)! :)

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

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

Title:
  The organized files and folders are covered by Unity Launcher.

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 14.04.2

  Reproducible Steps:

  1. Login Unity desktop environment.
  2. Change the scale factor to 2 in Displays of Settings.
  3. Create some files and folders on the desktop.
  4. Right click to select "Organize Desktop by Name".

  Expected Result:

  * The organized files and folders should be covered by Unity Launcher.

  Actual Result:

  * The organized files and folders are covered by Unity Launcher.

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

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

[Desktop-packages] [Bug 1406338] Re: nautilus misses "open with" for some types of files

[Ads20000]

Right-click > Open With is always a possibility for folders and .desktop
files for Files 3.26 on Ubuntu 17.10. Marking this as Fix Released, up
to a Bug Control member to mark this as affecting older (but supported)
releases of Ubuntu.

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

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

Title:
  nautilus misses "open with" for some types of files

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Hi guys.

  I am an ex "KDE fedora" user (for 5 years) and am trying "Unity
  Ubuntu" now.

  I think nautilus is interpreting so much the type of file and taking
  not the best decision.

  For example, when the "file" is a folder or a *.destop file, nautilus
  removes the "Open With" option.

  In my opinion, nautilus is a very nice pieace of code.

  IF the missing "Open With" is related to only these file type
  (direcotry and .desktop), it is ok to me.

  But i don't know if others file types are on the list.

  Please, guys. Turn the "Open With" switch to ALLWAYS ON.

  If not, please, can you list all the file types that you don't allow
  "Open With" ?

  (1) Ubuntu 14.04 LTS ( actually, Ubuntu 14.04.1, the amd64 version)
  (2) nautilus 3.10.1
  (3) I expected  "Open With" menu entry ALWAYS
  (4) What happened was that it was missing for some file types (I don't know 
all, but .desktop files is an example) 

  
  PS : Sorry by my poor english

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

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

[Desktop-packages] [Bug 1760371] Re: LightDM and GDM fail to start after systemd update in VirtualBox guest

[David Britton]

** Summary changed:

- LightDM and GDM fail to start after systemd update
+ LightDM and GDM fail to start after systemd update in VirtualBox guest

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

Title:
  LightDM and GDM fail to start after systemd update in VirtualBox guest

Status in lightdm package in Ubuntu:
  New

Bug description:
  1) Output of lsb_release -rd:
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04

  2) Output of apt-cache policy lightdm:
  lightdm:
Installed: 1.18.3-0ubuntu1.1
Candidate: 1.18.3-0ubuntu1.1
Version table:
   *** 1.18.3-0ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.18.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What I expected to happen:
  - Expected the display manager to take me to the lightdm user login screen.

  4) What happened instead:
  - lightdm made 5 attempts to start before failing. Failure messages were 
"failed to start Detect the available GPUs and deal with any system changes" 
and "Failed to start Light Display Manager".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 31 17:43:08 2018
  InstallationDate: Installed on 2015-11-23 (859 days ago)
  InstallationMedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (437 days ago)

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

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

[Desktop-packages] [Bug 1760664] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760664/+attachment/5099067/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760664/+attachment/5099070/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760664/+attachment/5099071/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760664/+attachment/5099072/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760664/+attachment/5099073/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760664/+attachment/5099074/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am not sure what else to report. This is an automated report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr  2 23:18:14 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-26 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760661] [NEW] Chromium and Chrome pausing

[Bret Ancowitz]

Public bug reported:

18.04 Budgie

Chrome and Chromium installed via debs and snaps are pausing for
variable seconds at a time, many times a minute.  Happens with or
without any extensions.  Firefox is fine.  CPU usage seems to go up with
the pauses.  Here is the snap run chromium output:

ATTENTION: default value of option force_s3tc_enable overridden by environment.
Gkr-Message: secret service operation failed: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.143" (uid=1000 pid=5932 
comm="/snap/chromium/266/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" 
member="Ping" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.secrets" (uid=1000 pid=1245 
comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")
Gkr-Message: secret service operation failed: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.143" (uid=1000 pid=5932 
comm="/snap/chromium/266/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") 
interface="org.freedesktop.Secret.Service" member="SearchItems" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" 
(uid=1000 pid=1245 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " 
label="unconfined")
[5932:6071:0402/134337.573104:ERROR:udev_watcher.cc(60)] Failed to begin udev 
enumeration.

Thank you.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Chromium and Chrome pausing

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  18.04 Budgie

  Chrome and Chromium installed via debs and snaps are pausing for
  variable seconds at a time, many times a minute.  Happens with or
  without any extensions.  Firefox is fine.  CPU usage seems to go up
  with the pauses.  Here is the snap run chromium output:

  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.143" (uid=1000 pid=5932 
comm="/snap/chromium/266/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" 
member="Ping" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.secrets" (uid=1000 pid=1245 
comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.143" (uid=1000 pid=5932 
comm="/snap/chromium/266/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") 
interface="org.freedesktop.Secret.Service" member="SearchItems" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" 
(uid=1000 pid=1245 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " 
label="unconfined")
  [5932:6071:0402/134337.573104:ERROR:udev_watcher.cc(60)] Failed to begin udev 
enumeration.

  Thank you.

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

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

[Desktop-packages] [Bug 1045553] Re: Nautilus unable to open certain URL links

[Bug Watch Updater]

** Changed in: nautilus
   Status: Unknown => Expired

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

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

Title:
  Nautilus unable to open certain URL links

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Noticed that Nautilus is unable to open certian URL links created from
  Firefox. Example of the error received when trying to open one of
  these links:

  Could not display
  "https://play.google.com/stor...5rb3VzaGlrZHV0dGEudGV0aGVyIl0;.

  The file is of an unknown type

  I am attaching one of these URL link files that fail to open.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep  3 17:40:39 2012
  EcryptfsInUse: Yes
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1607x865+0+186'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760645] Re: gnome-shell crashed with signal 5 in g_log_writer_default()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760645/+attachment/5099000/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760645/+attachment/5099005/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760645/+attachment/5099006/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760645/+attachment/5099007/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760645/+attachment/5099008/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760645/+attachment/5099009/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1755779
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from ... XSync() from 
meta_pre_paint_func() from _clutter_run_repaint_functions()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_writer_default()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Mon Apr  2 19:58:01 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-10-28 (156 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: Upgraded to bionic on 2018-03-10 (23 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo video

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

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

[Desktop-packages] [Bug 914572] Re: lbdb-fetchaddr truncates based on number of bytes, not characters

[Roland Rosenfeld]

The real name length limit was increased from 30 to 70 in lbdb 0.41.

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

Title:
  lbdb-fetchaddr truncates based on number of bytes, not characters

Status in lbdb package in Ubuntu:
  Confirmed

Bug description:
  When feeding lbdb-fetchaddr a header that is UTF-8 encoded and longer
  than 30 bytes or so, it truncates the name, but based on the number of
  bytes, not the number of characters. This can result in byte sequences
  that are not valid UTF-8 strings.

  For example:

  echo 'From: 우리들이 누리는 카이스트우리누리 선거운동 본부 ' | 
/usr/lib/lbdb/fetchaddr -c utf-8
  emaila...@gmail.com   우리들이 누리는 카�...  2012-01-11 11:34

  The charset argument is ignored when truncating. The result is
  m_inmail.list not being properly UTF-8 encoded.

  I am using lbdb 0.38 on Ubuntu 11.10.

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

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

[Desktop-packages] [Bug 1179890] Re: Folder icon is incorrectly thumbnailed if the source of the icon has been updated

[Alberto Salvia Novella]

** Changed in: hundredpapercuts
   Status: New => Confirmed

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

Title:
  Folder icon is incorrectly thumbnailed if the source of the icon has
  been updated

Status in One Hundred Papercuts:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  *
  STEPS TO REPRODUCE
  *
  1. Download an image into a folder.
  2. Change folder's icon to the downloaded image.
  3. Overwrite the image with a new one.
  4. Change folder's icon to the new image.

  *
  EXPECTED BEHAVIOUR
  *
  The icon to change to the new image.

  
  REAL BEHAVIOUR
  
  The icon doesn't update.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 14 12:27:29 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'220'
  InstallationDate: Installed on 2013-05-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760639] Re: gnome-shell crashed with signal 5 in g_log_writer_default()

[Apport retracing service]

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

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

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1760639/+attachment/5098973/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1760639/+attachment/5098976/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1760639/+attachment/5098977/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1760639/+attachment/5098978/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760639/+attachment/5098979/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760639/+attachment/5098980/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1755779
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from ... XSync() from 
meta_pre_paint_func() from _clutter_run_repaint_functions()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_writer_default()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with signal 5 in g_log_writer_default()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:31:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['brasero.desktop', 
'gnome-control-center.desktop', 'org.gnome.Software.desktop', 
'org.gnome.Nautilus.desktop', 'update-manager.desktop', 
'org.gnome.Screenshot.desktop', 'firefox.desktop', 'thunderbird.desktop', 
'spotify.desktop', 'audio-recorder.desktop', 'soundconverter.desktop', 
'qmmp.desktop', 'audacity.desktop', 'easytag.desktop', 'mypaint.desktop', 
'org.kde.kpat.desktop', 'org.gnome.Weather.Application.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-27 (126 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  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/1760639/+subscriptions

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

[Desktop-packages] [Bug 534477] Re: Closing "File Operations" into panel is redundant with minimizing

[Ads20000]

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

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

Title:
  Closing "File Operations" into panel is redundant with minimizing

Status in One Hundred Papercuts:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus 1:2.29.91-0ubuntu2, Ubuntu Lucid

  When moving or copying files that take a long time, a "File
  Operations" window opens. This window is both minimizable and
  closable. Closing it does not stop or cancel the operation; instead,
  it effectively minimizes the window into a status menu aka indicator
  (or, upstream, into a notification area item). While the window is
  open, the menu appears with a "Show copy dialogue" item, regardless of
  whether the progress window is currently focused or not.

  It is not sensible design to have two different destinations into
  which a window can be minimized. The usual argument here is that
  minimizing it into the standard window list takes up too much space;
  but if so, the answer shouldn't be to memorize a different way of
  minimizing it, it should be to find a way to make standard
  minimization take up less space. The extra width is not so onerous
  that we should delay fixing the inconsistency until after that
  happens.

  As I wrote in
  , "You do
  not need a custom status menu if: ... You just want the program to
  take up a small space in the panel when minimized." It would be
  misleading to ship Ubuntu 10.04 with a new design that we think other
  developers shouldn't imitate.

  I suggest that:
  * the "File Operations" window be made minimizable but not closable
  * Nautilus's libappindicator status menu be removed completely.

  Making this change would invalidate bug 507486.

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

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

[Desktop-packages] [Bug 979805] Re: nautilus greys out valid options

[Ads20000]

I used `sudo nautilus` to create a folder called roottest in ~. I gave
my user group ('adam') the 'Create and delete files' permission, and I'm
able to make new folders within the root-owned folder as expected.

I'm on Files 3.26 in Ubuntu 17.10.

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

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

Title:
  nautilus greys out valid options

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When you are in a group that has full rights to edit files, but you
  are not the owner, the "Create File/Folder" options are greyed out in
  Nautilus although they shouldn't be. Despite being greyed out,
  clicking them does still work though.

  Practical example: the /var/www sub-folders belong to www-data:www-
  data and file permissions are set to 775. I add the regular user to
  that group to be able to edit files without requiring root access. He
  can now edit files and create folders, but the Nautilus buttons do not
  indicate this.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 12 13:57:39 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '934x665+2104+146'
   org.gnome.nautilus.window-state sidebar-width 168
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1264344] Re: Filename conflict when copying files - unexpected behaviour when trying to rename the target file

[Ads20000]

This works fine in Files 3.26 on Ubuntu 17.10

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

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

Title:
  Filename conflict when copying files - unexpected behaviour when
  trying to rename the target file

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I use nautilus filemanger in my ubuntu box. When I copy and paste
  files between folders, sometimes a dialog box pops up saying that the
  target folder already contains a file with the same name asking me to
  choose among a set of options on how to proceed. One of the options
  available is to rename the target filename so that the file can be
  pasted to the target folder. When I rename the file through this
  dialog, it does not paste the file with the new name as expected.
  Instead it shows the name conflict dialog again for the same file with
  the old name. When I try to rename the file again with a different
  name, it accepts the command and pastes the file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-57-generic 3.2.0-57.87
  ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52
  Uname: Linux 3.2.0-57-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prasanna   2424 F pulseaudio
   /dev/snd/pcmC0D0p:   prasanna   2424 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc750 irq 56'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:111d7605,103c1656,00100105 
HDA:80862805,80860101,0010'
 Controls  : 26
 Simple ctrls  : 12
  Date: Thu Dec 26 12:09:03 2013
  HibernationDevice: RESUME=UUID=af25c2c3-daeb-4c20-ab5a-cd9142a49d7e
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic 
root=UUID=684493b8-0e0c-48e9-9c16-48bad55116c6 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-57-generic N/A
   linux-backports-modules-3.2.0-57-generic  N/A
   linux-firmware1.79.9
  SourcePackage: linux
  StagingDrivers: rts_pstor mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1656
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1656:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058C11244720001620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1229303] Re: Regional settings (date format) is ignored

[Ads20000]

Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

Also I can't test this on Ubuntu 17.10 because it uses GNOME Settings
rather than Unity Settings and doesn't seem to allow you to change the
date/time format in that, only to set the timezone.

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

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

Title:
  Regional settings (date format) is ignored

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  please see screenshot.
  Nautilus soes not use chosen date format.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 23 19:09:32 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1530x896+1920+155'"
  InstallationDate: Installed on 2013-04-02 (173 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago)

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

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

[Desktop-packages] [Bug 1252909] Re: Nautilus takes no notice of my selection in File --> Properties

[Ads20000]

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

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

Title:
  Nautilus takes no notice of my selection in File --> Properties

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  1. Select directory.
  2. Go to File --> Properties.
  3. Nautilus shows properties of the wrong thing.

  Nautilus doesn't appear to have any idea what it's doing.

  Cut and Copy are also not an option so I've had to revert to the
  command line!

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Nov 20 01:03:12 2013
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+437+144'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 235
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738664] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Bug Watch Updater]

** Changed in: sane-backends (Debian)
   Status: New => Fix Committed

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in dpkg package in Ubuntu:
  Invalid
Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Fix Committed

Bug description:
  ***
  to get a workaround, try:

  sudo apt-get -o Dpkg::Options::="--force-overwrite" install
  --reinstall libsane1:i386 (or your real package name)

  ***

  An error occured
  error:broken count>0

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 18 01:06:19 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-baiIM1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1179890] Re: Folder icon is incorrectly thumbnailed if the source of the icon has been updated

[Ads20000]

Confirmed on Files 3.26 on Ubuntu 17.10 and in the Files Nightly
Flatpak. Have filed here:
https://gitlab.gnome.org/GNOME/nautilus/issues/349

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

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

Title:
  Folder icon is incorrectly thumbnailed if the source of the icon has
  been updated

Status in One Hundred Papercuts:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  *
  STEPS TO REPRODUCE
  *
  1. Download an image into a folder.
  2. Change folder's icon to the downloaded image.
  3. Overwrite the image with a new one.
  4. Change folder's icon to the new image.

  *
  EXPECTED BEHAVIOUR
  *
  The icon to change to the new image.

  
  REAL BEHAVIOUR
  
  The icon doesn't update.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 14 12:27:29 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'220'
  InstallationDate: Installed on 2013-05-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1178225] Re: "Other Application" not shown in "Open With" menu, when more than one file is selected

[Rüdiger Kupper]

Confirming. Thanks, Ads2!

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

Title:
  "Other Application" not shown in "Open With" menu, when more than one
  file is selected

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Right clicking a file and selecting "Open With" from the context menu
  shows the applications registered for the respective MIME type. It
  also shows the entry "Other Application" for selecting another
  application to open the file with.

  When selecting more than one file (having the same MIME type,
  obviously), still shows the registered applications, but the "Other
  Application" entry is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  9 13:32:58 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'807x997+871+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'186'
  InstallationDate: Installed on 2012-12-20 (139 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-25 (13 days ago)

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

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

[Gunnar Hjalmarsson]

Thanks. Then the question is why it doesn't have any effect for you.

Another test: Can you please create an additional user, log in to that
user, and test it there? If it works for the other user, the problem is
somewhere in the $HOME of your first user.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1089449] Re: nautilus 3.6 desktop image thumbnail resize blurry

[Ads20000]

As of Files 3.26 on Ubuntu 17.10, desktop icons don't get more blurry as
you increase their size.

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

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

Title:
  nautilus 3.6 desktop image thumbnail resize blurry

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When I resize an image on the desktop larger, it becomes blurry
  because the thumbnail stretches. This was working properly not that
  long ago. Zooming in within a regular nautilus window works fine, but
  the desktop thumbnail resize does not. Icons (vector) resize fine,
  it's just images.

  I looked around and found the previous bugs about this, it seems like
  its supposed to be fixed by now. I think its a regression, unless
  there's some setting? I already tried removing the .thumbnails folder
  and restarting nautilus.

  Nautilus 3.6.3 on Ubuntu 12.10 x64 with gnome-shell 3.6.2

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

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

[Desktop-packages] [Bug 1179751] Re: Nautilus image folders cannot be used until thumbnailing is complete

[Ads20000]

Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Nautilus image folders cannot be used until thumbnailing is complete

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have lots of folders with images and of course, I use the file list
  with thumbnails. It would be great, but I cannot do any file operation
  because the file thumbnails have a different size and modify each
  line's height, so my files go down. See the attached movie for
  details.

  Each file should have a pre-determined max-height & max-width
  rectangle/square and the preview should always fit to that rectangle.
  Then, no matther the images are landscape or portrait, they will fit
  and this problem dissapears.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 14 04:37:53 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'808x550+49+24'"
  InstallationDate: Installed on 2013-04-25 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1223574] Re: Refuses to trash a directory "because" it's not empty

[Ads20000]

I can't reproduce this bug on Files 3.26 on Ubuntu 17.10 so I'm assuming
this bug is fixed.

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

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

Title:
  Refuses to trash a directory "because" it's not empty

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I selected two folders (which contained files) and hit the Delete key.
  I got the nonsense warning shown in the screenshot:

  "Unable to trash file: Directory not empty"

  Since when is that a reason for not being able to move a directory to trash???
  I have done the same hundreds of times before. Usually, when a folder is not 
empty, it used to be moved to trash with all its contents without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: i386
  Date: Tue Sep 10 23:50:37 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1322x738+202+144'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
  InstallationDate: Installed on 2010-06-23 (1175 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-08-10 (31 days ago)

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

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

[Desktop-packages] [Bug 1233855] Re: Trash doesn't work well

[Ads20000]

As of Files 3.26 on Ubuntu 17.10, it works to move files out of trash to
a different directory from the original.

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

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

Title:
  Trash doesn't work well

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  If I move to the Trash folder using the program "nautilus" and I righ-
  click on an item and then select "Copy to" or "Move to" instead of
  copying or moving where I tell it it just restores the item instead of
  the directory that I select. Even If I try to copy paste (CTRL+C
  CTRL+V) it will just restore in the original folder instead in the one
  I choose.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Tue Oct  1 23:02:25 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+65+189'"
  InstallationDate: Installed on 2013-09-23 (8 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1178225] Re: "Other Application" not shown in "Open With" menu, when more than one file is selected

[Ads20000]

I'm on Files 3.26 on Ubuntu 17.10 and can't reproduce this bug so I'm
assuming that it's been fixed :)

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

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

Title:
  "Other Application" not shown in "Open With" menu, when more than one
  file is selected

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Right clicking a file and selecting "Open With" from the context menu
  shows the applications registered for the respective MIME type. It
  also shows the entry "Other Application" for selecting another
  application to open the file with.

  When selecting more than one file (having the same MIME type,
  obviously), still shows the registered applications, but the "Other
  Application" entry is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  9 13:32:58 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'807x997+871+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'186'
  InstallationDate: Installed on 2012-12-20 (139 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-25 (13 days ago)

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

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

[Desktop-packages] [Bug 1121073] Re: Nautilus is not showing [encrypted] units after unmount

[Ads20000]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Nautilus is not showing [encrypted] units after unmount

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have an encrypted SD-card connected to my laptops card reader. After
  boot I start Nautilus and I can see the unit in the unit list, it is
  not mounted. I click on it to mount it and give the password with
  option Remind password for session, I then copy some files to it and
  the press the eject button to the right of it. Nautilus shuts down the
  active window. Later I want to copy some more files to it, so I start
  Nautilus again but the unit is not visible this time. I can see the
  SD-card in Disks but I cannot mount it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 10 12:19:34 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+118+75'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'193'
  InstallationDate: Installed on 2012-11-22 (79 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2012-11-22T15:57:26.024721

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

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

[Desktop-packages] [Bug 1705689] Re: When adding an app to favourites, two icons are created.

[frenchy82]

on a fresh install of ubuntu 18.04 in virtualbox i can experiment this
problem since this week updates

it's a bit different from this bug report as I have this bug when adding
terminal or totem or cheese with right click, not only by drag and drop

Don't know if it's the same bug or coming from a very recent update

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

Title:
  When adding an app to favourites, two icons are created.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10, I wanted to add gnome-terminal to the favorites.
  Usually in Gnome, the item gets added one times. Instead, there were
  two items of gnome-terminal in the favorites.

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

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

[Desktop-packages] [Bug 1045553] Re: Nautilus unable to open certain URL links

[Ads20000]

I clicked the link in the upstream bug and this now works fine! :)

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

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

Title:
  Nautilus unable to open certain URL links

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Noticed that Nautilus is unable to open certian URL links created from
  Firefox. Example of the error received when trying to open one of
  these links:

  Could not display
  "https://play.google.com/stor...5rb3VzaGlrZHV0dGEudGV0aGVyIl0;.

  The file is of an unknown type

  I am attaching one of these URL link files that fail to open.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep  3 17:40:39 2012
  EcryptfsInUse: Yes
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1607x865+0+186'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1045553] Re: Nautilus unable to open certain URL links

[Ads20000]

(Files 3.26 on Ubuntu 17.10)

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

Title:
  Nautilus unable to open certain URL links

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Noticed that Nautilus is unable to open certian URL links created from
  Firefox. Example of the error received when trying to open one of
  these links:

  Could not display
  "https://play.google.com/stor...5rb3VzaGlrZHV0dGEudGV0aGVyIl0;.

  The file is of an unknown type

  I am attaching one of these URL link files that fail to open.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep  3 17:40:39 2012
  EcryptfsInUse: Yes
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1607x865+0+186'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1084204] Re: Unmount message is not displayed

[Ads20000]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  Unmount message is not displayed

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When writing to external USB devices (e.g., USB sticks or USB HDD),
  the write progress bar is displayed correctly. After the write
  progress bar is full and the progress window stops displaying, the
  status light of the device signals, that still data is written to the
  device. Previously, when you pressed the unmount button in nautilus, a
  window apeared and displayed a warning not to remove the device. Since
  about two weeks, this warning message is not displayed any more. When
  removing the device before the write cache is empty, the filesystem of
  the device is corrupted on the next mount. This behaviour is
  reproducable and occurs every time. It also happens on other
  installation of 12.10 as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Wed Nov 28 20:03:37 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'917x683+65+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2012-11-13 (15 days ago)

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

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

[Desktop-packages] [Bug 883033] Re: mounted devices doesn't open from 1st attempt from desktop

[Ads20000]

(Assuming Fix Released because this bug was from Ubuntu 11.10-12.04.

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

Title:
  mounted devices doesn't open from 1st attempt from desktop

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  mounted devices doesn't open from 1st attempt from desktop. With
  gnome-tweak-tool I have enabled 'show mounted volumes on the desktop'

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

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

[Desktop-packages] [Bug 883033] Re: mounted devices doesn't open from 1st attempt from desktop

[Ads20000]

My USB stick mounts and opens on 1st time from the desktop in Ubuntu
17.10.

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

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

Title:
  mounted devices doesn't open from 1st attempt from desktop

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  mounted devices doesn't open from 1st attempt from desktop. With
  gnome-tweak-tool I have enabled 'show mounted volumes on the desktop'

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

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

[Desktop-packages] [Bug 1760437] Re: package xdiagnose 3.8.4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Leonidas S. Barbosa]

** Information type changed from Private Security to Public

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

Title:
  package xdiagnose 3.8.4.1 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in xdiagnose package in Ubuntu:
  New

Bug description:
  Bonjour

  La mise à jour qui met proposé est impossible a installer alors que
  faire.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xdiagnose 3.8.4.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   lshw: Install
   xdiagnose: Configure
   ubuntu-desktop: Configure
   lshw: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sun Apr  1 06:36:03 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-01  06:35:55
   Commandline: aptdaemon role='role-commit-packages' sender=':1.79'
   Upgrade: lshw:i386 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5)
  DuplicateSignature:
   package:xdiagnose:3.8.4.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package xdiagnose (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: xdiagnose
  Title: package xdiagnose 3.8.4.1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760437] Re: package xdiagnose 3.8.4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package xdiagnose 3.8.4.1 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in xdiagnose package in Ubuntu:
  New

Bug description:
  Bonjour

  La mise à jour qui met proposé est impossible a installer alors que
  faire.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xdiagnose 3.8.4.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   lshw: Install
   xdiagnose: Configure
   ubuntu-desktop: Configure
   lshw: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sun Apr  1 06:36:03 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-01  06:35:55
   Commandline: aptdaemon role='role-commit-packages' sender=':1.79'
   Upgrade: lshw:i386 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5)
  DuplicateSignature:
   package:xdiagnose:3.8.4.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package xdiagnose (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: xdiagnose
  Title: package xdiagnose 3.8.4.1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760614] Re: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured

[dino99]

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

** Package changed: cups (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade:
  package libcups2:i386 is already installed and configured

Status in dpkg package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcups2:i386 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: i386
  CupsErrorLog:
   
  Date: Mon Apr  2 14:42:56 2018
  DuplicateSignature:
   package:libcups2:i386:2.1.3-4ubuntu0.4
   Processing triggers for doc-base (0.10.7) ...
   1 hinzugefügte Doc-base-Datei wird verarbeitet...
   dpkg: error processing package udev (--configure):
package udev is already installed and configured
  ErrorMessage: package libcups2:i386 is already installed and configured
  InstallationDate: Installed on 2018-01-22 (69 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Precision M6500
  Papersize: a4
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: cups
  Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: 
package libcups2:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.

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

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