date:20180306

Great, thanks. But I can't access that bug so it must be private.
Unusual though, since as a member of ~ubuntu-bugcontrol I should be able
to see it...

Please wait until that bug has finished retracing, then remove any
sensitive personal information attachments from it, then change it from
Private to Public (top right of the page).

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

Title:
  Xorg crash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Each time I turn my screen off I get logged out of my session. I have
  to log in again and all my apps have been forcefully closed (Chrome
  mentions it didn't close cleanly and offers me to restore my tabs, for
  example).

  This happens after 5 minutes of inactivity (I have the setting for
  screen off at 5 minutes) and also when I turn off my screen by myself.

  Some more info:

  $ lsb_release -rd 
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy xorg 
  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:57:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  MachineType: MSI MS-7850
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/system-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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

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

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

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

*** 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/1753440/+attachment/5069772/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1753440/+attachment/5069781/+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/1753440

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm remove pulseaudo and install gnome-alsamixer. After run gnome-
  alsamixer appeared this error

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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: Mon Mar  5 13:15:22 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-11 (53 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.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
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () 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: 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/1753440/+subscriptions

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

[Desktop-packages] [Bug 1740150] Re: Allow GTK theming for Ubuntu Budgie

2018-03-06 Thread Simon Quigley

Since Tim said the patch looks good, sponsoring.

Thanks!

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

Title:
  Allow GTK theming for Ubuntu Budgie

Status in gnome-screensaver package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Budgie uses gnome-screensaver for its lock-screen.

  By default, gnome-screensaver does not provide a GTK+3 based style
  class - thus the lock screen is not themed by modern GTK+3 themes.

  UB already has a patch (33_budgie_support.patch) that fixes a couple
  of issues.

  I have updated this patch to allow GTK+3 theming via the style class
  "lock-dialog".  This allows gnome-screensaver to the themed in the
  same way as the gnome-screensaver fork mate-screensaver which uses the
  same named style-class.

  This has been tested using the GTK+3 theme adapta which has the MATE
  lock-screen style class "lock-dialog" .

  I will be separately updating arc-theme (the theme used by Ubuntu
  Budgie) to provide theming for both mate-screensaver and gnome-
  screensaver (for Ubuntu Budgie).

  Note - if its considered useful, I'm happy to rework this to move the
  style-class application to a separate patch to allow all desktops that
  use gnome-screensaver to be equally themed.  However I've only tested
  this patch on Ubuntu Budgie and hence have restricted the style-class
  application to UB.

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

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

[Desktop-packages] [Bug 1753658] Re: Xorg crash

2018-03-06 Thread dwilches

@vanvugt I followed your instructions and created the bug
https://bugs.launchpad.net/bugs/1753912 with the crash file

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

Title:
  Xorg crash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Each time I turn my screen off I get logged out of my session. I have
  to log in again and all my apps have been forcefully closed (Chrome
  mentions it didn't close cleanly and offers me to restore my tabs, for
  example).

  This happens after 5 minutes of inactivity (I have the setting for
  screen off at 5 minutes) and also when I turn off my screen by myself.

  Some more info:

  $ lsb_release -rd 
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy xorg 
  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:57:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  MachineType: MSI MS-7850
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/system-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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

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

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

[Desktop-packages] [Bug 1753658] Re: Xorg crash

2018-03-06 Thread dwilches

Found the issue when looking at `/var/log/apport.log`. This may be
useful for other people to whom you ask to do that workaround:

RROR: apport (pid 2496) Tue Mar  6 21:33:37 2018: apport: report
/var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen,
doing nothing to avoid disk usage DoS

So I removed the crashes I already had in /var/crash. Will reproduce the
crash now and report back in a moment.

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

Title:
  Xorg crash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Each time I turn my screen off I get logged out of my session. I have
  to log in again and all my apps have been forcefully closed (Chrome
  mentions it didn't close cleanly and offers me to restore my tabs, for
  example).

  This happens after 5 minutes of inactivity (I have the setting for
  screen off at 5 minutes) and also when I turn off my screen by myself.

  Some more info:

  $ lsb_release -rd 
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy xorg 
  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:57:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  MachineType: MSI MS-7850
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/system-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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

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

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

[Desktop-packages] [Bug 1753658] Re: Xorg crash

2018-03-06 Thread dwilches

Tried two workarounds mentioned in that bug, none worked (the crash did
not generate any files in /var/crash).

The first workaround I tried was:

comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.

I put an # at the beginning of line 20, not 23 because line 20 is the
one that mentions problem_types, but after a restart and reproducing the
crash I didn't get any new crash files in that folder.

Also tried adding `Crash` to the list of problem_types (as mentioned in
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/993450/comments/13
) but same thing, no new files after a restart and a crash.

Something else I can try to generate the crash file?

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

Title:
  Xorg crash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Each time I turn my screen off I get logged out of my session. I have
  to log in again and all my apps have been forcefully closed (Chrome
  mentions it didn't close cleanly and offers me to restore my tabs, for
  example).

  This happens after 5 minutes of inactivity (I have the setting for
  screen off at 5 minutes) and also when I turn off my screen by myself.

  Some more info:

  $ lsb_release -rd 
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy xorg 
  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:57:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  MachineType: MSI MS-7850
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/system-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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

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

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

[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2

2018-03-06 Thread matt r.

build reject for this patch in the driver

** Attachment added: "nv-linux.h.rej"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+attachment/5071271/+files/nv-linux.h.rej

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

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

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

[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2

2018-03-06 Thread matt r.

thank you google and duck duck gogo, i found the patch instructions here

https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/4/

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

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

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

[Desktop-packages] [Bug 1753796] Re: Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release)

2018-03-06 Thread Timo Aaltonen

** Package changed: mesa (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
 Assignee: (unassigned) => DAVIDE MILONE (milone)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
 Assignee: DAVIDE MILONE (milone) => Alberto Milone (albertomilone)

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

Title:
  Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-
  release)

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

Bug description:
  On Ubuntu 18.04 with the NVIDIA development repository PPA, installing
  cuda-drivers I get the following error during the installation of
  nvidia-390:

  dpkg: error processing archive 
/var/cache/apt/archives/nvidia-390_390.30-0ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which 
is also in package libglx-mesa0:amd64 18.0.0~rc4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglx-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: User Name 4.15.0-1002.2-azure 4.15.3
  Uname: Linux 4.15.0-1002-azure x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Tue Mar  6 17:38:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GK210GL [Tesla K80] [10de:106c]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1002-azure 
root=UUID=950907d2-f8b1-431a-8195-e06fbf9a814b ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 94AF2AB7-6288-E94C-9C01-1305DF401054
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2

2018-03-06 Thread matt r.

it is maintained by nvidia, i submitted a report to them .

how do I install the patch and where, driver kernel etc ?
i have compiled kernels, but not a patch as of yet

i have the hardware.

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

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

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

[Desktop-packages] [Bug 1753902] [NEW] Users administration tool - advanced settings window size problem

2018-03-06 Thread Brian

Public bug reported:

I am using MATE, so my steps will be as such

If I go to the menu: System -> Administration -> Users and Groups
When the window opens, I have only one user. Under that user, I click on button 
'Advanced Settings'. After I authenticate and the window opens, it appears on 
my screen very tall to the point where I cannot even see the bottom of the 
window where I assume there are some buttons like Cancel, Ok, Submit, or 
something to confirm or deny changes made. The window is somewhat narrow which 
looks fine, but there is a lor of wasted space vertically. I am unable to 
resize this window at all, not horizontally or vertically. The resizing icons 
appear, but the window itself will not resize.

I believe I have the current version, but there is no version/about or anything 
on this tool. The help is really of no use for this, and it does contain the 
following, but the link goes to an invalid URL.
"To report a bug or make a suggestion regarding the Users Administration Tool 
or this manual, follow the directions in the GNOME Feedback Page."
I am using MATE 17.10 with all updates valid as of today per Package Manager.

This may seem somewhat minor, but without a 'yes or no' button option,
these settings are all useless.

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

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

Title:
  Users administration tool - advanced settings window size problem

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  I am using MATE, so my steps will be as such

  If I go to the menu: System -> Administration -> Users and Groups
  When the window opens, I have only one user. Under that user, I click on 
button 'Advanced Settings'. After I authenticate and the window opens, it 
appears on my screen very tall to the point where I cannot even see the bottom 
of the window where I assume there are some buttons like Cancel, Ok, Submit, or 
something to confirm or deny changes made. The window is somewhat narrow which 
looks fine, but there is a lor of wasted space vertically. I am unable to 
resize this window at all, not horizontally or vertically. The resizing icons 
appear, but the window itself will not resize.

  I believe I have the current version, but there is no version/about or 
anything on this tool. The help is really of no use for this, and it does 
contain the following, but the link goes to an invalid URL.
  "To report a bug or make a suggestion regarding the Users Administration Tool 
or this manual, follow the directions in the GNOME Feedback Page."
  I am using MATE 17.10 with all updates valid as of today per Package Manager.

  This may seem somewhat minor, but without a 'yes or no' button option,
  these settings are all useless.

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

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

[Desktop-packages] [Bug 1753873] [NEW] The session title "Ubuntu on Wayland" is misleading

Public bug reported:

The session title "Ubuntu on Wayland" is misleading.

Gnome Shell is not running "on Wayland" at all. If you choose that
option then mutter is running on the "eglnative" backend instead of the
X11 backend.

I'm not suggesting we call the session "Ubuntu on eglnative", as that
would make it more confusing. But I wonder if we can find a session
title that avoids implying the impossible situation that the shell runs
"on Wayland". Because the current title makes many people think that's
what's happening.

Actually, Wayland doesn't come into the picture at all until you start
an app. Only then is "Wayland" used at all as the protocol between the
app and the shell, sometimes.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-session 3.27.91-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Wed Mar  7 09:59:25 2018
InstallationDate: Installed on 2017-12-12 (84 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-session (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071182/+files/JournalErrors.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071183/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071184/+files/ProcEnviron.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071181/+files/Dependencies.txt

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Low

** Description changed:

  The session title "Ubuntu on Wayland" is misleading.
  
  Gnome Shell is not running "on Wayland" at all. If you choose that
  option then mutter is running on the "eglnative" backend instead of the
  X11 backend.
  
  I'm not suggesting we call the session "Ubuntu on eglnative", as that
  would make it more confusing. But I wonder if we can find a session
  title that avoids implying the impossible situation that the shell runs
  "on Wayland". Because the current title makes many people think that's
  what's happening.
  
  Actually, Wayland doesn't come into the picture at all until you start
  an app. Only then is "Wayland" used at all as the protocol between the
- app and the shell.
+ app and the shell, sometimes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.27.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Mar  7 09:59:25 2018
  InstallationDate: Installed on 2017-12-12 (84 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  The session title "Ubuntu on Wayland" is misleading

Status in gnome-session package in Ubuntu:
  New

Bug description:
  The session title "Ubuntu on Wayland" is misleading.

  Gnome Shell is not running "on Wayland" at all. If you choose that
  option then mutter is running on the "eglnative" backend instead of
  the X11 backend.

  I'm not suggesting we call the session "Ubuntu on eglnative", as that
  would make it more confusing. But I wonder if we can find a session
  title that avoids implying the impossible situation that the shell
  runs "on Wayland". Because the current title makes many people think
  that's what's happening.

  Actually, Wayland doesn't come into the picture at all until you start
  an app. Only then is "Wayland" used at all as the protocol between the
  app and the shell, sometimes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.27.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Mar  7 09:59:25 2018
  InstallationDate: Installed on 2017-12-12 (84 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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-session/+bug/1753873/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

2018-03-06 Thread Miles

I'm also seeing this issue and I just purged Duplicity and then added it
back with the PPA and I am still seeing the issue. I am using 0.7.17
now. What information can I provide to help fix this?

Ubuntu Version: UbuntuMate 17.10

uname -a
Linux 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

ulimit -v
unlimited

ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 31429
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 31429
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

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

Title:
  error: can't start new thread

Status in Duplicity:
  Incomplete
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

So is there a bug here, for future reference? In nvidia-390 or mesa? Or
none?

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

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1753871] [NEW] Track info is lost or corrupted after "Extract"

2018-03-06 Thread Michael Poole

Public bug reported:

When I insert a CD, Rhythmbox typically tells me that it matches
multiple albums, usually with identical names.  Whichever album I pick,
it shows correct-looking title, artist, and album names on the "Devices"
page for the CD.  However, if I go to the "Recently Added" page after
the import completes, most -- and often all -- of the tracks show
unknown artist and album name, and the track name is of the form "01 -
Track Name.flac".

The most frequent case is that all tracks lose this information.
Sometimes one, and rarely two, end up with the correct metadata.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: rhythmbox 3.4.1-2ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  6 20:40:15 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-29 (615 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to artful on 2017-10-21 (136 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Track info is lost or corrupted after "Extract"

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  When I insert a CD, Rhythmbox typically tells me that it matches
  multiple albums, usually with identical names.  Whichever album I
  pick, it shows correct-looking title, artist, and album names on the
  "Devices" page for the CD.  However, if I go to the "Recently Added"
  page after the import completes, most -- and often all -- of the
  tracks show unknown artist and album name, and the track name is of
  the form "01 - Track Name.flac".

  The most frequent case is that all tracks lose this information.
  Sometimes one, and rarely two, end up with the correct metadata.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: rhythmbox 3.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 20:40:15 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-29 (615 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to artful on 2017-10-21 (136 days ago)

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

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

[Desktop-packages] [Bug 1753576] Re: GDM freeze

Wayland is not a program, so "Wayland" can't crash. Wayland is only a
protocol for talking to apps that is supported by the Gnome Shell
'eglnative' backend inside the 'mutter' project. This issue is further
confused by the incorrect wording "Ubuntu on Wayland" on the login
screen. Actually it's not running "on Wayland" at all...

That all said, yes the eglnative backend in mutter, which provides
Wayland app support, can crash for its own reasons.

The greeter will default to eglnative ("Wayland") mode, so if you find
disabling that works around the bug (switching to Xorg instead) then
great. However this bug will stay incomplete until we have some sort of
stack trace of a crash, ideally a .crash file.

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

Title:
  GDM freeze

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

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  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+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

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

nvidia-90 support may/should be fixed now that Mesa 18.0 is in bionic.
Please update and retest.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
 Assignee: Alberto Milone (albertomilone) => (unassigned)

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

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

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

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

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

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

[Desktop-packages] [Bug 1752431] Re: Gnome Shell Wayland session crashes on startup - artful

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

** Description changed:

+ https://gitlab.gnome.org/GNOME/mutter/issues/56
+ 
+ ---
+ 
  When I select "gnome" on login, the session fails to start. If I select
  gnome/xorg all is well.
  
  Description:  Ubuntu 17.10
  Release:  17.10
  
- 
  wayland-protocols:
-   Installed: 1.10-1
-   Candidate: 1.10-1
-   Version table:
-  *** 1.10-1 500
- 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
- 500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
- 100 /var/lib/dpkg/status
- --- 
+   Installed: 1.10-1
+   Candidate: 1.10-1
+   Version table:
+  *** 1.10-1 500
+ 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
+ 500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
+ 100 /var/lib/dpkg/status
+ ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
-  org.gnome.shell favorite-apps ['firefox.desktop', 
'chromium-browser.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'shotwell.desktop', 'org.gnome.Totem.desktop', 
'vlc.desktop', 'update-manager.desktop', 'audacity.desktop', 
'org.gnome.Terminal.desktop']
-  org.gnome.desktop.interface cursor-theme 'redglass'
-  org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
-  org.gnome.desktop.interface gtk-theme 'Adwaita-dark'
-  org.gnome.desktop.interface clock-show-date true
+  org.gnome.shell favorite-apps ['firefox.desktop', 
'chromium-browser.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'shotwell.desktop', 'org.gnome.Totem.desktop', 
'vlc.desktop', 'update-manager.desktop', 'audacity.desktop', 
'org.gnome.Terminal.desktop']
+  org.gnome.desktop.interface cursor-theme 'redglass'
+  org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
+  org.gnome.desktop.interface gtk-theme 'Adwaita-dark'
+  org.gnome.desktop.interface clock-show-date true
  InstallationDate: Installed on 2013-03-16 (1811 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-21 (131 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  Gnome Shell Wayland session crashes on startup - artful

Status in gnome-shell package in Ubuntu:
  New

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

  ---

  When I select "gnome" on login, the session fails to start. If I
  select gnome/xorg all is well.

  Description:  Ubuntu 17.10
  Release:  17.10

  wayland-protocols:
    Installed: 1.10-1
    Candidate: 1.10-1
    Version table:
   *** 1.10-1 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell favorite-apps ['firefox.desktop', 
'chromium-browser.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'shotwell.desktop', 'org.gnome.Totem.desktop', 
'vlc.desktop', 'update-manager.desktop', 'audacity.desktop', 
'org.gnome.Terminal.desktop']
   org.gnome.desktop.interface cursor-theme 'redglass'
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
   org.gnome.desktop.interface gtk-theme 'Adwaita-dark'
   org.gnome.desktop.interface clock-show-date true
  InstallationDate: Installed on 2013-03-16 (1811 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-21 (131 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1753884] [NEW] session logout after suspend

2018-03-06 Thread Simon

Public bug reported:

This is a new bug report for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362075

I am running Ubuntu 16.04.4 LTS 64-bit + gnome, the standard
installation as downloaded from the Ubuntu website, on a Lenovo ThinkPad
T440s.

When I close the lid of my laptop, my session gets logged out, where I
would expect the lock screen simply to come up.

The workaround suggested in the original bug report (which was for
kubuntu 9.04) suggests to disable the lock screen on resume option, but
I can't find this option on 16.04.

It's also not a super desirable work-around. I want to still have to log
in if I close the lid of my laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Mar  6 18:07:50 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2018-02-15 (19 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
MachineType: LENOVO 20AQ009HUS
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET78WW (2.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQ009HUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20AQ009HUS
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
   session logout after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a new bug report for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362075

  I am running Ubuntu 16.04.4 LTS 64-bit + gnome, the standard
  installation as downloaded from the Ubuntu website, on a Lenovo
  ThinkPad T440s.

  When I close the lid of my laptop, my session gets logged out, where I
  would expect the lock screen simply to come up.

  The workaround suggested in the original bug report (which was for
  kubuntu 9.04) suggests to disable the lock screen on resume option,
  but I can't find this option on 16.04.

  It's also not a super desirable work-around. I want to still have to
  log in if I close the lid of my laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

** Changed in: libglvnd (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1753831] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'aut

2018-03-06 Thread dino99

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: tentative de remplacement de «
  /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances
  du paquet libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I don't know why this error appear, nothing special happened

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar  6 13:37:27 2018
  ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
  InstallationDate: Installed on 2018-01-31 (34 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  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: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1539591] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from st_bin_dispose() [st/st-bin.c:186:st_bin_dispose: assertion failed:

Fix released (zero crashes reported after 17.10)

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

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr() from st_bin_dispose() [st/st-
  bin.c:186:st_bin_dispose: assertion failed: (priv->child == NULL)]

Status in gnome-shell package in Ubuntu:
  Fix Released

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

  ---

  Such crash has already happened several times after validating the greeter's 
password to open a gnome-shell session.
  This does not happen each time, but always, after the password validation, it 
looks like the system have some difficulties to load X : that takes too much 
time, the background goes grey, and 5 or 10 seconds later, the session is 
opened, or i get such a crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 29 14:08:52 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libgnome-shell.so
   g_object_run_dispose () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   clutter_actor_destroy () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionLog:
   openConnection: connect: No such file or directory
   cannot connect to brltty at :0
   Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer: 
Failed to connect to socket /tmp/dbus-M92EaZdecj: Connection refused
   upstart: upstart-event-bridge main process (1801) terminated with status 1
   upstart: upstart-event-bridge main process ended, respawning

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

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

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

2018-03-06 Thread Timo Aaltonen

I think you first got the updates when nvidia had migrated and
mesa/libglvnd had no

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1693113] Re: GNOME sessions need renaming (too many people are choosing the X11 one over Wayland)

The prefix, and the default session, have both changed now. No bug.

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

Title:
  GNOME sessions need renaming (too many people are choosing the X11 one
  over Wayland)

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  GNOME sessions need renaming (too many people are choosing the X11 one
  over Wayland).

  This would be because:

  X11 is named "GNOME"
  Wayland is named "GNOME on Wayland"

  A consequence of many people choosing the former is a high rate of X11
  crashes: bug 1556601 and bug 1505409

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Wed May 24 14:55:48 2017
  InstallationDate: Installed on 2017-05-03 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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-session/+bug/1693113/+subscriptions

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

[Desktop-packages] [Bug 1753776] Re: After login the screen pixelates for few seconds on GNOME on X

Yeah I had this yesterday with 3.27.91, but today the bug is gone
(bionic updated to gnome-shell/mutter 3.27.92).

** Summary changed:

- After login the screen pixelates for few seconds on GNOME on X
+ Graphics corruption in login animation to Xorg sessions

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

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

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

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

Title:
  Graphics corruption in login animation to Xorg sessions

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   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.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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:

[Desktop-packages] [Bug 1752123] Re: Force 8bit RGB config

That's fine. I knew I was aiming for Wayland sessions on 10-bit support,
not Xorg. It might also take some additional mutter work.

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

Title:
  Force 8bit RGB config

Status in clutter package in Ubuntu:
  New
Status in cogl package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  New mesa supports 10bit RGB configs, and this causes issues with
  cogl/mutter which get a random EGLConfig that breaks some
  autopkgtests. To fix this this merge request is needed for mutter

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

  and a similar one for cogl.

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

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

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

2018-03-06 Thread Sam Wilson

I'm not sure which update did it, but without me doing anything my Epson
V33 is working again now on Ubunbu 17.10.

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

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

Status in sane-backends package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"

2018-03-06 Thread John

Downloaded ubuntu-font-family-0.83 from design.ubuntu.com/font.

This bug also affects me on Debian 9.

If I remove Ubuntu Medium, Ubuntu Light renders properly in LibreOffice.

Also, Microsoft Windows displays Ubuntu Medium's font name as "Ubuntu
Light."

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

Title:
  "Ubuntu Light" font has heavier weight than "Ubuntu"

Status in One Hundred Papercuts:
  In Progress
Status in Ubuntu Font Family:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in ubuntu-font-family-sources package in Ubuntu:
  In Progress
Status in ubuntu-font-family-sources source package in Wily:
  Triaged

Bug description:
  After upgrading from Vivid to Wily, pages using the "Ubuntu light" font 
actually renders with a weight heavier than the regular one in web pages.
  This happens with Chrome/Chromium and also the Ubuntu browser.

  After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in
  place of 0.83-0ubuntu1), the issue is fixed.

  See the attached screenshot showing the result seen browing
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  1 17:55:19 2015
  Dependencies:

  InstallationDate: Installed on 2014-10-14 (382 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)

  IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users
  which impacts the usability and visual design.

  The new version of font package (0.831) corrects the relationship
  between Light and Medium weight to follow the commonly used naming
  standards:

  Ubuntu Light  Light   Light Italic
  UbuntuRegular Italic  BoldBold Italic
  Ubuntu Medium Medium  Medium Italic   
  Ubuntu Condensed  Regular 
  Ubuntu Mono   Regular Italic  BoldBold Italic

  TEST CASE: in 15.10, go to
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  If the Light weight renders heavier than Normal weight, the bug is in
  place

  REGRESSION POTENTIAL

  0.831 was tested by manually running in 15.10 and no regression was
  noticed, while the bug was fixed. The potential for regression is
  small.

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

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

[Desktop-packages] [Bug 1753178] Re: deja-dup-monitor crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1753052
   deja-dup-monitor crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup-monitor is segfaulting upon login to the desktop session.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Mar  3 21:55:56 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-01-23 (39 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180123)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/fish
  SegvAnalysis:
   Segfault happened at: 0x7fb82ba93588:movl   $0x0,(%rax)
   PC (0x7fb82ba93588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fb82bcfb02c, 
init_routine=0x7fb822b76490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753178/+subscriptions

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

[Desktop-packages] [Bug 1752950] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

** This bug is no longer a duplicate of bug 1753052
   deja-dup-monitor crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 in virtualbox 5.2.8 on Windows 10

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  2 18:37:38 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-08-09 (204 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f2800e61588:movl   $0x0,(%rax)
   PC (0x7f2800e61588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f28010c902c, 
init_routine=0x7f27f7f64490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2017-11-25 (96 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1752950/+subscriptions

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

[Desktop-packages] [Bug 1753052] Re: deja-dup-monitor crashed with SIGSEGV

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

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

  $ apt-cache policy deja-dup
  deja-dup:
Instal·lat: 37.1-1fakesync1
Candidat:   37.1-1fakesync1
Taula de versió:
   *** 37.1-1fakesync1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Mar  3 08:56:22 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2014-08-20 (1290 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7fac7224d588:movl   $0x0,(%rax)
   PC (0x7fac7224d588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fac724b502c, 
init_routine=0x7fac69330490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-01-02 (59 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev pulse pulse-access 
sambashare sudo video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1753052/+subscriptions

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

[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace the "Activities" label with the Ubuntu icon/logo/glyph

** Description changed:

  I suggest replacing the "Activities" label with the Ubuntu icon/logo.
  
  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.
- 
- Perhaps even a single glyph:  or 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [enhancement] Replace the "Activities" label with the Ubuntu
  icon/logo/glyph

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

Bug description:
  I suggest replacing the "Activities" label with the Ubuntu icon/logo.

  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753246] Re: deja-dup-monito: segfault

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

** This bug is no longer a duplicate of bug 1753052
   deja-dup-monitor crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup-monito: segfault

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  deja-dup-monito[4838]: segfault at bbadbeef ip 7f00ac4cb588 sp
  7ffde62fc3d0 error 6 in
  libjavascriptcoregtk-4.0.so.18.7.6[7f00ab713000+fc4000]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar  4 13:44:43 2018
  InstallationDate: Installed on 2018-01-01 (61 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753246/+subscriptions

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

[Desktop-packages] [Bug 1753279] Re: deja-dup-monitor crashed with SIGSEGV

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

** This bug is no longer a duplicate of bug 1753052
   deja-dup-monitor crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  ubuntu bionic beaver .
  I get this error but don't know why because I don't use deja-dup.
  I've got this a multiple times after logging in to my system

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  Uname: Linux 4.15.7-041507-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar  4 22:58:40 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7fcdf71eb588:movl   $0x0,(%rax)
   PC (0x7fcdf71eb588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fcdf745302c, 
init_routine=0x7fcdee2a8490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753279/+subscriptions

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

[Desktop-packages] [Bug 1753861] [NEW] Renaming file in password protected archive results in file being deleted from the archive

2018-03-06 Thread John Keenan

Public bug reported:

I have encountered a problem when using Archive Manager (file-roller) version
3.16.5 on Ubuntu 16.04 LTS (currently updated).
$ lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04
$ apt-cache policy file-roller
file-roller:
Installed: 3.16.5-0ubuntu1.2
Candidate: 3.16.5-0ubuntu1.2
Version table:
*** 3.16.5-0ubuntu1.2 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
3.16.4-1ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To demonstrate this problem:

1) Download the attached file "Archive rename problem.zip". This archive
contains the two files "Hello there.txt" and "Hello there.log". The archive
password is "Hello there" (without the quotes).
2) Inspection of the contents of the two files indicates the files were
mistakenly named. The .txt file should be .log and the .log file should be .txt.
3) Close and re-open the archive. This step is required so the password is
required in the next step.
4) Rename file "Hello there.txt" to "Hello there2.log". When you click the
"Rename" button, you will be immediately prompted for the archive password.
Enter the password and click the "OK" button. At this point the file "Hello
there.txt" has been deleted from the archive and only file "Hello there.log"
remains in the archive. Menu item File > Test Integrity shows no problems with
the archive.

My expectation is that the rename of a file in an archive should never result
in the deletion of that file from the archive. The rename operation should
either rename the file or fail to rename the file preserving the original file
name.

I believe this problem is important because files that are put into a
password protected archive are put there for a reason (for example,
financial information). The unexpected deletion of these files is most
likely important to the file owner.

Please note:

1) This problem does not occur if the identical files are placed into an
archive which is not password protected.
2) This problem does not occur if the archive password is entered previous to
the rename operation. For example, if the files are first opened to inspect
their contents.
3) This problem does not occur if the two files have different names
excluding the file name extensions .txt and .log.

** Affects: file-roller (Ubuntu)
Importance: Undecided
Status: New

** Tags: file-roller

** Attachment added: "Archive rename problem.zip"

https://bugs.launchpad.net/bugs/1753861/+attachment/5071147/+files/Archive%20rename%20problem.zip

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

Title:
Renaming file in password protected archive results in file being
deleted from the archive

Status in file-roller package in Ubuntu:
New

Bug description:
I have encountered a problem when using Archive Manager (file-roller) version
3.16.5 on Ubuntu 16.04 LTS (currently updated).
$ lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04
$ apt-cache policy file-roller
file-roller:
Installed: 3.16.5-0ubuntu1.2
Candidate: 3.16.5-0ubuntu1.2
Version table:
*** 3.16.5-0ubuntu1.2 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
3.16.4-1ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To demonstrate this problem:

I believe this problem is important because files

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10

2018-03-06 Thread genti

It is actually fixed now. If you build 1.0.27 from Git it'll be ok.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10 I see a black band on
  scanned image. The scanner is Canon CanoScan LIDE100. Libsane version
  is 1.0.27-1~experimental2ubuntu1

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

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

[Desktop-packages] [Bug 245716] Re: file-roller puts temporary files in the home dir instead of /tmp

2018-03-06 Thread igor

i'm on Ubuntu 14 lts (16 didnt even boot up on this device, so i didnt
bother to update, its an LTS after all)

not only this bug is still present but i found another one:
if you open an image protected by password in an zip file, then close the file 
roller, the image disapear, i guess that is the expected, but there is another 
issue.
even if you close the image, if you put the computer to hibernate, then return 
from it (the hibernate status)
the image will open again...

i'm not sure what is happening here, but here is what i guess:
i was seeing some password protected files, something crash on the background 
so i had to kill some processes including firefox, i'm not sure if i killed the 
file roller too and the pp files (password protected) or they close 
automatically and the system was trying to recover from crash, i constantly 
closed an openend pp files sometimes, and set the computer to hibernate, when i 
wake up the computer, the files where openend many times, as if i never had 
closed then.

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

Title:
  file-roller puts temporary files in the home dir instead of /tmp

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged
Status in file-roller package in Arch Linux:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy file-roller
  file-roller:
Installed: 3.12.2-0ubuntu1
Candidate: 3.12.2-0ubuntu1
Version table:
   *** 3.12.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens a tarball with file-
  roller, and without extracting the file, open it (ex. open PDF file
  with evince) the file-roller utilizes /tmp for this.

  4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , 
where * is a changing folder name. If one logs out, or kills the file-roller 
process via:
  kill PID

  the temp files are left behind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions

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

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

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

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

Title:
  jackd crashed with SIGABRT

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  Probably happened in connection with shotcut crashing while being
  connected to Jackd.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 11:12:22 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2333 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

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

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

** Changed in: jackd2 (Ubuntu)
   Status: New => Invalid

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

Title:
  jackd crashed with SIGABRT

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  Probably happened in connection with shotcut crashing while being
  connected to Jackd.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 11:12:22 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2333 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

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

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

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

Title:
  jackd crashed with SIGABRT

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  Probably happened in connection with shotcut crashing while being
  connected to Jackd.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 11:12:22 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2333 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Desktop-packages] [Bug 1753433] Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libmagic-mgc
no debug symbol package found for qjackctl
no debug symbol package found for gir1.2-glib-2.0
no debug symbol package found for perl-base
no debug symbol package found for libcomerr2
no debug symbol package found for libavahi-common-data
no debug symbol package found for perl-base
no debug symbol package found for perl-base


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

** Tags removed: need-amd64-retrace

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

Title:
  jackd crashed with SIGABRT

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  Probably happened in connection with shotcut crashing while being
  connected to Jackd.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 11:12:22 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2333 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Desktop-packages] [Bug 1753433] jackd crashed with SIGABRT

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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

Title:
  jackd crashed with SIGABRT

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  Probably happened in connection with shotcut crashing while being
  connected to Jackd.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 11:12:22 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2333 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10

2018-03-06 Thread genti

This is also reported on the SANE project bug report website, which
includes the solution to fix this issue:
https://alioth.debian.org/tracker/index.php?func=detail=315752_id=30186=410366

The root cause is a patch, that causes the issue in the first place

** Bug watch added: alioth.debian.org/ #315752
   http://alioth.debian.org/support/tracker.php?aid=315752

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10 I see a black band on
  scanned image. The scanner is Canon CanoScan LIDE100. Libsane version
  is 1.0.27-1~experimental2ubuntu1

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

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

[Desktop-packages] [Bug 1734032] Re: X11 application cannot get nabi XIM server's state

2018-03-06 Thread Frank Heimes

** Changed in: nabi (Ubuntu)
   Status: New => Invalid

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

Title:
  X11 application cannot get nabi XIM server's state

Status in nabi package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  X11 application cannot get nabi XIM server's state.

  ---uname output---
  4.10.0-30-generic #34~16.04.1-Ubuntu SMP Wed Aug 2 02:13:56 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
   
  Machine Type = x64 machine 

  ---Steps to Reproduce---
   This testing requires X11 desktop environment , nabi XIM server (nabi 
package) and Korean locale.
  1. Login to X11 environmnet
  2. Download attached xim_root.zip file
  3. Compile it with "-lX11" option, like
  $ cc -o xim_root xim_root.c -lX11
  4. Change current local ko_KR.utf8, like
  $ export LANG=ko_KR.utf8
  5. Start nabi, like
  $ nabi &
  (XIM's state may display somewhere...)
  6. Start xim_root with XMODIFIERS environment variable, like
  $ XMODIFIERS=@im=nabi ./xim_root
  7. Press "A" key, then xim_root prints "XmbLookupString:a"
  8. Press Ctrl+Muddle Mouse button on xim_root, then print "State: IM On", 
even if IM is not turned ON <== ISSUE
  9. Press Shift+Space key to turn on, then type "gks", Korean character is 
displayed on xim_root, then press Return key, this Korean character is committed
  10. Press Ctrl+Left Mouse button to turn off XIM server, then type "gks", but 
still XIM is turned on <== ISSUE
  11. Press Ctrl+Middle Mouse button, print "State: IM Off".

  So X11 application cannot get XIM state properly.

  $ ps -ef | grep nabi
  jdktest   4377  3409  0 21:21 pts/10   00:00:00 nabi
  jdktest   7427  1760  0 21:40 pts/100:00:00 grep --color=auto nabi
  $ apport-cli 4377 --save=bug.apport

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

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

[Desktop-packages] [Bug 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"

2018-03-06 Thread Kenneth Long

one more note.  the kern.log message below is triggered when I select
source.

Insert -> Media -> Scan -> Select Source

Mar  6 17:45:21 know kernel: [ 3171.678785] audit: type=1400 
audit(1520376321.492:41): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=3747 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
Mar  6 17:45:21 know kernel: [ 3171.678789] audit: type=1400 
audit(1520376321.492:42): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=3747 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0

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

Title:
  apparmor="DENIED" operation="open" profile="libreoffice-soffice"
  name="/etc/sane.d/dll.d/hplip"

Status in apparmor package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  currently able to scan with xsane utility. libreoffice is not able to
  scan because it cannot find the scanner.

  log shows

  
  Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 
audit(1519613074.593:93): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 
audit(1519613074.593:94): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 
audit(1519613074.593:95): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001

  
  this stopped working after latest "do-release-upgrade"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashReports:
   664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 
21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload
   600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 
21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded
   640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 
21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash
   640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 
20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash
  CurrentDesktop: XFCE
  Date: Sun Feb 25 22:00:01 2018
  InstallationDate: Installed on 2017-04-19 (312 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago)

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

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

[Desktop-packages] [Bug 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"

2018-03-06 Thread Kenneth Long

sorry about the improper naming... " apparmor, not apport "
The machine I was using when this bug was originally found had a failed hard 
drive.  
new hard and new install of xubuntu. its using all the default repositories the 
comes with xubuntu. 
it also has a google ppa for chrome install. 

uname -a
Linux know 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

this problem still exists and the install version of libreoffice is

Version: 5.4.5.1
Build ID: 1:5.4.5-0ubuntu0.17.10.4
CPU threads: 16; OS: unknown; UI render: default; VCL: gtk2; 
Locale: en-US (en_US.UTF-8); Calc: group

and kern.log shows the error -

Mar  6 17:27:13 know kernel: [ 2083.820190] audit: type=1400
audit(1520375233.628:35): apparmor="DENIED" operation="open" profile
="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=3747
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0


should these repositories below have this updated libreoffice ?
what else can I look for? 

root@know:/etc/apt# cat sources.list | grep -v \#

deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted
deb http://us.archive.ubuntu.com/ubuntu/ artful-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu/ artful universe
deb http://us.archive.ubuntu.com/ubuntu/ artful-updates universe
deb http://us.archive.ubuntu.com/ubuntu/ artful multiverse
deb http://us.archive.ubuntu.com/ubuntu/ artful-updates multiverse
deb http://us.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse
deb http://security.ubuntu.com/ubuntu artful-security main restricted
deb http://security.ubuntu.com/ubuntu artful-security universe
deb http://security.ubuntu.com/ubuntu artful-security multiverse

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

Title:
  apparmor="DENIED" operation="open" profile="libreoffice-soffice"
  name="/etc/sane.d/dll.d/hplip"

Status in apparmor package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  currently able to scan with xsane utility. libreoffice is not able to
  scan because it cannot find the scanner.

  log shows

  
  Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 
audit(1519613074.593:93): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 
audit(1519613074.593:94): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 
audit(1519613074.593:95): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001

  
  this stopped working after latest "do-release-upgrade"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashReports:
   664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 
21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload
   600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 
21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded
   640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 
21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash
   640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 
20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash
  CurrentDesktop: XFCE
  Date: Sun Feb 25 22:00:01 2018
  InstallationDate: Installed on 2017-04-19 (312 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago)

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

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

[Desktop-packages] [Bug 1724773] Re: Some packages of LO 5.4.2 conflict with each other

2018-03-06 Thread Bobby de Vos

Last month I upgraded to 5.4.5 and did not notice any problems, so I
would say no, it is no longer valid.

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

Title:
  Some packages of LO 5.4.2 conflict with each other

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  1)
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  2)
  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:5.4.2~rc2-0ubuntu0.16.04.1~lo1
Candidate: 1:5.4.2~rc2-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:5.4.2~rc2-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0
Candidate: 1:5.4.2~rc2-0ubuntu0.16.04.1~lo1
Version table:
   1:5.4.2~rc2-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu 
xenial/main amd64 Packages
   *** 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 100
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3)
  I expected a clean upgrade from LO 5.4.1~rc2 to 5.4.2~rc2

  4)
  The packages
  * libreoffice-calc
  * libreoffice-common
  both provide
  /usr/lib/libreoffice/program/pagein-calc
  which causes problems for the upgrade.
  Similar issues happen with the packages
  * libreoffice-impress
  * libreoffice-draw

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

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

[Desktop-packages] [Bug 1753429] Re: shares-admin crashed with SIGSEGV in g_type_check_instance_cast()

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

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 #1731256, 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/1753429/+attachment/5069742/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1731256

** 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-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1753429

Title:
  shares-admin crashed with SIGSEGV in g_type_check_instance_cast()

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  It crashes when clicking the properties box, user...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-tools 3.0.0-6ubuntu1
  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
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 10:58:15 2018
  ExecutablePath: /usr/bin/shares-admin
  InstallationDate: Installed on 2018-01-30 (33 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: shares-admin
  SegvAnalysis:
   Segfault happened at: 0x7f31b033aed0 :   
movzbl 0x14(%r8),%ecx
   PC (0x7f31b033aed0) ok
   source "0x14(%r8)" (0x6dd37174) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-system-tools
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   share_settings_dialog_run_for_iter ()
   on_edit_share_clicked ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: shares-admin crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-01 (3 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-system-tools/+bug/1753429/+subscriptions

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

[Desktop-packages] [Bug 1753052] Re: deja-dup-monitor crashed with SIGSEGV

2018-03-06 Thread Bug Watch Updater

** Changed in: webkit-open-source
   Status: Unknown => Confirmed

** Changed in: webkit-open-source
   Importance: Unknown => Medium

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

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

  $ apt-cache policy deja-dup
  deja-dup:
Instal·lat: 37.1-1fakesync1
Candidat:   37.1-1fakesync1
Taula de versió:
   *** 37.1-1fakesync1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Mar  3 08:56:22 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2014-08-20 (1290 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7fac7224d588:movl   $0x0,(%rax)
   PC (0x7fac7224d588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fac724b502c, 
init_routine=0x7fac69330490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-01-02 (59 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev pulse pulse-access 
sambashare sudo video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1753052/+subscriptions

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

[Desktop-packages] [Bug 1753052] Re: deja-dup-monitor crashed with SIGSEGV

2018-03-06 Thread Danilo Piazzalunga

I believe this is a duplicate of LP: #1751460.

** Bug watch added: bugs.webkit.org/ #183329
   https://bugs.webkit.org/show_bug.cgi?id=183329

** Also affects: webkit-open-source via
   https://bugs.webkit.org/show_bug.cgi?id=183329
   Importance: Unknown
   Status: Unknown

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in Déjà Dup:
  New
Status in WebKit:
  Unknown
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

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

  $ apt-cache policy deja-dup
  deja-dup:
Instal·lat: 37.1-1fakesync1
Candidat:   37.1-1fakesync1
Taula de versió:
   *** 37.1-1fakesync1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Mar  3 08:56:22 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2014-08-20 (1290 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7fac7224d588:movl   $0x0,(%rax)
   PC (0x7fac7224d588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fac724b502c, 
init_routine=0x7fac69330490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-01-02 (59 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev pulse pulse-access 
sambashare sudo video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1753052/+subscriptions

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

[Desktop-packages] [Bug 1752899] Re: deja-dup crashed with SIGSEGV in __pthread_once_slow()

2018-03-06 Thread Danilo Piazzalunga

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Running in Virtualbox. Latest updates were being installed no
  applications running.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  2 14:51:40 2018
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2018-01-27 (34 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  JournalErrors:
   -- Logs begin at Sat 2018-01-27 12:04:01 GMT, end at Fri 2018-03-02 14:56:00 
GMT. --
   Mar 02 14:47:05 username-VirtualBox NetworkManager[567]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   Mar 02 14:47:12 username-VirtualBox gnome-session-binary[800]: CRITICAL: 
Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
   Mar 02 14:47:45 username-VirtualBox pulseaudio[1141]: [pulseaudio] 
bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  ProcCmdline: deja-dup --prompt
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fbc4a73f588:movl   $0x0,(%rax)
   PC (0x7fbc4a73f588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fbc4a9a702c, 
init_routine=0x7fbc42acc490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1752899/+subscriptions

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

[Desktop-packages] [Bug 1753478] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

2018-03-06 Thread Danilo Piazzalunga

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

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

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  this is an automated bug report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 19:56:52 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2015-08-05 (942 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f086a843588:movl   $0x0,(%rax)
   PC (0x7f086a843588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f086aaab02c, 
init_routine=0x7f0861900490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirt lpadmin plugdev sambashare sudo 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753478/+subscriptions

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

[Desktop-packages] [Bug 1753417] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753417/+attachment/5069697/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753417

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Happened after reboot and first login after upgrade to 18.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 11:05:41 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-10-06 (149 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f845f74d588:movl   $0x0,(%rax)
   PC (0x7f845f74d588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f845f9b502c, 
init_routine=0x7f845680a490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753417/+subscriptions

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

[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

2018-03-06 Thread Arna Ghosh

Hello everyone,
Thanks to your answers and this discussion. I ran into this problem yesterday. 
Although I tried the instructions by @cjjefcoat on #57, it didn't give me back 
my display as expected. Unity got screwed up and although I could see the 
display, the rendering was not proper. The windows didn't have the title bar 
and most keyboard functionality won't work. I didn't even have the task bar. 
I went back to -112 version of the kernel but only found the same result. So I 
reinstalled all NVIDIA drviers and uninstalled CUDA with no luck at all. 
Finally I tried restarting Unity by following #14 here - 
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1569357/comments/14

and it worked for me :D 
Now I tried running everything on 116 kernel and it works. So in case unity 
screws up for any of you after you reinstall the 116 kernel, try restarting 
Unity and hope it works :D

Cheers

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile:

[Desktop-packages] [Bug 1753422] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753422/+attachment/5069708/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753422

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  happens immediately after logging in

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 08:57:33 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f170867f588:movl   $0x0,(%rax)
   PC (0x7f170867f588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f17088e702c, 
init_routine=0x7f16ff73c490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip disk kvm libvirt lpadmin plugdev sambashare 
sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753422/+subscriptions

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

[Desktop-packages] [Bug 1193205] Re: dhcp IPv6 sets accept_ra to 0 and doesn't get IPv6 route

2018-03-06 Thread Alexander Kirsch

I ran into the same problem with 17.10 and I solved it without any fixed
or workarounds. But this is not an ubuntu bug! It's a false
configuration. There are 2 Options for automatic IPv6 configuration in
network manager. "Automatic" and "Automatic (DHCP only)". IPv6 router
advertisment is not part of dhcpv6 by spec! So I switch my config to
"Automatic" which uses dhcpv6 and router advertisment. The kernel option
/proc/sys/net/ipv6/conf/ethX/accept_ra is set to 1 (active) then!
Problem solved!

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

Title:
  dhcp IPv6 sets accept_ra to 0 and doesn't get IPv6 route

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Configure IPv6 network so that the IP address is obtained through
  DHCPv6 and setup NetworkManager IPv6 to use the "Automatic (DHCP
  only)" method.   accept_ra is then set to 0 and NetworkManager fails
  to obtain the IPv6 route.

  Attached is a script /etc/NetworkManager/dispatcher.d/02allowIPv6route
  which works around the issue to set accept_ra to 1.

  I am running Kubuntu 13.04, but I believe the bug is not limited to
  this release.

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

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

[Desktop-packages] [Bug 894496] Re: Add support for Google Play Music

2018-03-06 Thread Fred

** Summary changed:

- Add support for Google Music
+ Add support for Google Play Music

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

Title:
  Add support for Google Play Music

Status in Amarok:
  Fix Released
Status in Banshee:
  New
Status in Exaile:
  Won't Fix
Status in Unity:
  Confirmed
Status in audacious package in Ubuntu:
  New
Status in banshee package in Ubuntu:
  Triaged
Status in clementine package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Add support for Google Music to Unity as a scope.
  https://music.google.com/

  And to media players as a music store and music cloud storage.

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

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

[Desktop-packages] [Bug 1753831] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'a

2018-03-06 Thread Mickaël ANCELLE

Public bug reported:

I don't know why this error appear, nothing special happened

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Mar  6 13:37:27 2018
ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
InstallationDate: Installed on 2018-01-31 (34 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
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: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: tentative de remplacement de «
  /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances
  du paquet libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I don't know why this error appear, nothing special happened

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar  6 13:37:27 2018
  ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
  InstallationDate: Installed on 2018-01-31 (34 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  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: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753396] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753396/+attachment/5069651/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753396

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Appeared after upgrade from Artful to Bionic

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 09:17:02 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2016-11-01 (489 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f25a8fa4588:movl   $0x0,(%rax)
   PC (0x7f25a8fa4588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f25a920c02c, 
init_routine=0x7f25a0061490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (0 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753396/+subscriptions

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

[Desktop-packages] [Bug 1753719] Re: gnome-calculator won't launch

2018-03-06 Thread Hans Joachim Desserud

** Tags added: artful

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

Title:
  gnome-calculator won't launch

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  package: gnome-calculator
  release: 17.10
  package version: gnome-calculator:
Installed: 1:3.25.92-0ubuntu1
Candidate: 1:3.25.92-0ubuntu1
Version table:
   *** 1:3.25.92-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  I expected the calculator to open

  instead it crashed:
  ../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= 
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
  Aborted (core dumped)

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

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

[Desktop-packages] [Bug 1753241] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1753241/+attachment/5068912/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753241

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  something due upgrading the system...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar  4 13:05:57 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f69d0370588:movl   $0x0,(%rax)
   PC (0x7f69d0370588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f69d05d802c, 
init_routine=0x7f69c742d490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753241/+subscriptions

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

[Desktop-packages] [Bug 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"

2018-03-06 Thread Led Shark

Hi,

 I can confirm the last batch of libreoffice (1:5.4.5-0ubuntu0.17.10.4)
fixes concerning apparmor  fixed the many warnings mentioned in my logs.

Merci/Thks

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

Title:
  apparmor="DENIED" operation="open" profile="libreoffice-soffice"
  name="/etc/sane.d/dll.d/hplip"

Status in apparmor package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  currently able to scan with xsane utility. libreoffice is not able to
  scan because it cannot find the scanner.

  log shows

  
  Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 
audit(1519613074.593:93): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 
audit(1519613074.593:94): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 
audit(1519613074.593:95): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001

  
  this stopped working after latest "do-release-upgrade"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashReports:
   664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 
21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload
   600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 
21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded
   640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 
21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash
   640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 
20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash
  CurrentDesktop: XFCE
  Date: Sun Feb 25 22:00:01 2018
  InstallationDate: Installed on 2017-04-19 (312 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago)

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

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

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

*** 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/1753239/+attachment/5068884/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1753239/+attachment/5068893/+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/1753239

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after boot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar  4 19:08:39 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"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop', 
'org.gnome.Terminal.desktop', 'bdgui.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-02-21 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.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: Upgraded to bionic on 2018-02-23 (9 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1753236] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753236/+attachment/5068855/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753236

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Running on Xubuntu Bionic. After running updates and rebooting, deja-
  dup-monitor crashes at startup. Happy to provide any additional info
  needed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Sun Mar  4 06:48:27 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-02-11 (20 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180211)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdee70ec588:movl   $0x0,(%rax)
   PC (0x7fdee70ec588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fdee735402c, 
init_routine=0x7fdede1a9490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  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/deja-dup/+bug/1753236/+subscriptions

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

[Desktop-packages] [Bug 1753238] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753238/+attachment/5068874/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753238

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup-monitor crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 12:47:20 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-09-28 (157 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4fb1601588:movl   $0x0,(%rax)
   PC (0x7f4fb1601588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f4fb186902c, 
init_routine=0x7f4fa86e4490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  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/deja-dup/+bug/1753238/+subscriptions

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

[Desktop-packages] [Bug 1753235] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753235/+attachment/5068844/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753235

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  just dist-upgrading

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Mar  4 12:46:34 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2012-02-27 (2196 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0a07a65588:movl   $0x0,(%rax)
   PC (0x7f0a07a65588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f0a07ccd02c, 
init_routine=0x7f09feb48490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2017-12-11 (83 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare 
vboxusers video wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753235/+subscriptions

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

[Desktop-packages] [Bug 1752431] Re: Gnome Shell Wayland session crashes on startup - artful

2018-03-06 Thread Sam Freed

https://gitlab.gnome.org/GNOME/mutter/issues/56

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

Title:
  Gnome Shell Wayland session crashes on startup - artful

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I select "gnome" on login, the session fails to start. If I
  select gnome/xorg all is well.

  Description:  Ubuntu 17.10
  Release:  17.10

  
  wayland-protocols:
Installed: 1.10-1
Candidate: 1.10-1
Version table:
   *** 1.10-1 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell favorite-apps ['firefox.desktop', 
'chromium-browser.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'shotwell.desktop', 'org.gnome.Totem.desktop', 
'vlc.desktop', 'update-manager.desktop', 'audacity.desktop', 
'org.gnome.Terminal.desktop']
   org.gnome.desktop.interface cursor-theme 'redglass'
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
   org.gnome.desktop.interface gtk-theme 'Adwaita-dark'
   org.gnome.desktop.interface clock-show-date true
  InstallationDate: Installed on 2013-03-16 (1811 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-21 (131 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1753744] Re: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

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

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 #1664613, 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/1753744/+attachment/5070680/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1664613

** 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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1753744

Title:
  gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I know nothing more than an error occurred, asked me to send it here.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.27.90-1ubuntu1
  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: Unity:Unity7:ubuntu
  Date: Tue Mar  6 12:42:49 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2018-03-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  SegvAnalysis:
   Segfault happened at: 0x7f25c3ef3818:mov0x90(%r14),%rsi
   PC (0x7f25c3ef3818) ok
   source "0x90(%r14)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()
  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-terminal/+bug/1753744/+subscriptions

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

[Desktop-packages] [Bug 1752702] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1752702/+attachment/5066400/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1752702

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Ciao

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  1 20:46:45 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-02-24 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180223)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8ed790b588:movl   $0x0,(%rax)
   PC (0x7f8ed790b588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f8ed7b7302c, 
init_routine=0x7f8ece9ee490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1752702/+subscriptions

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

[Desktop-packages] [Bug 1753213] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753213/+attachment/5068750/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753213

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  The system was subsequently upgraded by apt-get dist-upgrade during two or 
three month from Ubuntu 17.04LTS to the last available Bionic Beaver 
development branch. Had to upgrade due to some package I was unable to run 
under LTS and it was OK under newer distributives.
  At a beginning of February 2018 I've started to get different crashes. 
Meanwhile, another operational system on the same laptop is OK, none crashes. 
The current report is about new type of a crash I've never seen before.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 11:09:32 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f38036c6588:movl   $0x0,(%rax)
   PC (0x7f38036c6588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f380392e02c, 
init_routine=0x7f37fa783490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin microchip plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753213/+subscriptions

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

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

2018-03-06 Thread Michael

And it worked :-) Thanks for the hint!

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

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

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

*** 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/1752698/+attachment/5066378/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1752698/+attachment/5066387/+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/1752698

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar  1 20:29:39 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-05-13 (292 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170511)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.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/1752698/+subscriptions

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

[Desktop-packages] [Bug 1753212] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1753212/+attachment/5068741/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753212

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 09:30:05 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-01-12 (50 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  JournalErrors:
   -- Logs begin at Tue 2018-01-23 09:13:25 CET, end at Sun 2018-03-04 09:34:05 
CET. --
   mar 04 09:27:49 username-850PRO gnome-session-binary[1051]: CRITICAL: Unable 
to create a DBus proxy for GnomeScreensaver: Errore nel chiamare 
StartServiceByName per org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
   mar 04 09:28:02 username-850PRO kernel: nouveau :01:00.0: gr: intr 
0040
   mar 04 09:28:15 username-850PRO pulseaudio[2056]: [pulseaudio] 
bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: 
Failed to activate service 'org.bluez': timed out 
(service_start_timeout=25000ms)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f47cb229588:movl   $0x0,(%rax)
   PC (0x7f47cb229588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f47cb49102c, 
init_routine=0x7f47c22e6490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1753212/+subscriptions

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

[Desktop-packages] [Bug 1753776] Re: After login the screen pixelates for few seconds on GNOME on X

2018-03-06 Thread corrado venturini

problem does NOT occur with Gnome 3.27.92 and a different Intel graphics:
mao@mao-p6-bb:~$ inxi -Fx
System:Host: mao-p6-bb Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0
   Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3)
   Distro: Ubuntu Bionic Beaver (development branch)
Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x serial: N/A
   UEFI: American Megatrends v: F3 date: 04/24/2013
CPU:   Dual core Intel Core i3-4130 (-MT-MCP-) arch: Haswell rev.3 cache: 
3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13569
   clock speeds: max: 3400 MHz 1: 915 MHz 2: 1260 MHz 3: 1224 MHz 4: 
1259 MHz
Graphics:  Card: Intel 4th Generation Core Integrated Graphics Controller 
bus-ID: 00:02.0
   Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1680x1050@59.88hz
   OpenGL: renderer: Mesa DRI Intel Haswell
   version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Def. Audio Controller
   driver: snd_hda_intel bus-ID: 00:1b.0
   Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
   driver: snd_hda_intel bus-ID: 00:03.0
   Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
   driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
   IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 
94:de:80:7e:90:a7
Drives:HDD Total Size: 1000.2GB (1.2% used)
   ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 4.0G (14%) fs: ext4 dev: /dev/sda6
   ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
   Fan Speeds (in rpm): cpu: N/A
Info:  Processes: 237 Uptime: 7 min Memory: 1431.8/7856.5MB
   Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) 
inxi: 2.3.56
mao@mao-p6-bb:~$

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

Title:
  After login the screen pixelates for few seconds on GNOME on X

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

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature:

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

*** 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/1753207/+attachment/5068713/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1753207/+attachment/5068722/+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/1753207

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happened a few seconds after boot and startup of LibreOffice
  Calc.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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: Sun Mar  4 01:57:35 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:
   () 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: 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/1753207/+subscriptions

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

[Desktop-packages] [Bug 1753208] Re: gnome-software crashed with SIGSEGV in g_main_loop_is_running()

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

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 #1716508, 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/1753208/+attachment/5068723/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1716508
   gnome-software crashed with SIGSEGV in g_main_loop_is_running()

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

Title:
  gnome-software crashed with SIGSEGV in g_main_loop_is_running()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.27.90-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar  4 08:44:36 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.27.90-1ubuntu2
   gnome-software-plugin-limba   3.27.90-1ubuntu2
   gnome-software-plugin-snap3.27.90-1ubuntu2
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f397060f779 : mov
0xc(%rdi),%eax
   PC (0x7f397060f779) ok
   source "0xc(%rdi)" (0x3fe232323232323e) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   g_main_loop_is_running () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/liblimba.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in g_main_loop_is_running()
  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/1753208/+subscriptions

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

[Desktop-packages] [Bug 1753206] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1753206/+attachment/5068703/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753206

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  it just reported crash in backup which i hadn't run.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 02:04:01 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd69dffa588:movl   $0x0,(%rax)
   PC (0x7fd69dffa588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fd69e26202c, 
init_routine=0x7fd6950dd490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1753206/+subscriptions

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

[Desktop-packages] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

2018-03-06 Thread Michael

$  apt install libegl-mesa0 libmirclient9 libcapnp-0.6.1 libmircommon7
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
  libboost-filesystem1.65.1:i386 libboost-system1.65.1:i386 libmircore1:i386
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
  libmircore1
Die folgenden Pakete werden ENTFERNT:
  libcapnp-0.6.1:i386 libegl-mesa0:i386 libegl1:i386 libegl1-mesa:i386 
libgtk-3-0:i386 libmikmod3:i386 libmirclient9:i386 libmircommon7:i386 
libsdl-mixer1.2:i386 libsdl2-2.0-0:i386 libwayland-egl1-mesa:i386
Die folgenden NEUEN Pakete werden installiert:
  libcapnp-0.6.1 libegl-mesa0 libmirclient9 libmircommon7 libmircore1
0 aktualisiert, 5 neu installiert, 11 zu entfernen und 0 nicht aktualisiert.
Es müssen 1.045 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 12,1 MB Plattenplatz freigegeben.

I had to add some packages to get apt on the right way.
I'll tell after a restart what happened, I just wanted to write down what apt 
did ;-)

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

Title:
  [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe

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

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core:

[Desktop-packages] [Bug 1753199] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753199/+attachment/5068652/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753199

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I just booted an got app report message.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 08:27:05 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-11-08 (115 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f852c6fb588:movl   $0x0,(%rax)
   PC (0x7f852c6fb588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f852c96302c, 
init_routine=0x7f85237de490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753199/+subscriptions

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

[Desktop-packages] [Bug 1753200] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1753200/+attachment/5068662/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753200

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 08:06:54 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-02-03 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180203)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6e8ffc9588:movl   $0x0,(%rax)
   PC (0x7f6e8ffc9588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f6e9023102c, 
init_routine=0x7f6e870ac490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1753200/+subscriptions

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

[Desktop-packages] [Bug 1753202] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753202/+attachment/5068673/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753202

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Backup software crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 11:34:23 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-01-22 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180122)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f66e740c588:movl   $0x0,(%rax)
   PC (0x7f66e740c588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f66e767402c, 
init_routine=0x7f66de4ef490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  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/deja-dup/+bug/1753202/+subscriptions

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

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

*** 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/1753194/+attachment/5068618/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1753194/+attachment/5068627/+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/1753194

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Fault notice appeared after upgrade download, reboot, followed by
  running autoremove and autoclean; along with the fault notice "The
  application Backups has closed unexpectedly."

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Mar  3 18:52:52 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-11 (113 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171110)
  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/1753194/+subscriptions

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

[Desktop-packages] [Bug 1753197] Re: deja-dup-monitor crashed with SIGSEGV

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

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 #1751460, 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/1753197/+attachment/5068633/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753197

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When i initialize the Ubuntu 18.04, automatically appears the prompt
  asking to report this error

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  4 01:16:08 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7f06522f0588:movl   $0x0,(%rax)
   PC (0x7f06522f0588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f065255802c, 
init_routine=0x7f06493ad490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  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/deja-dup/+bug/1753197/+subscriptions

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

[Desktop-packages] [Bug 1753450] Re: [MIR] mpg123

2018-03-06 Thread Adam Conrad

mpg123 1.25.8-1 in bionic: universe/sound -> main
libmpg123-0 1.25.8-1 in bionic amd64: universe/libs/optional/100% -> main
libmpg123-0 1.25.8-1 in bionic arm64: universe/libs/optional/100% -> main
libmpg123-0 1.25.8-1 in bionic armhf: universe/libs/optional/100% -> main
libmpg123-0 1.25.8-1 in bionic i386: universe/libs/optional/100% -> main
libmpg123-0 1.25.8-1 in bionic ppc64el: universe/libs/optional/100% -> main
libmpg123-0 1.25.8-1 in bionic s390x: universe/libs/optional/100% -> main
libmpg123-dev 1.25.8-1 in bionic amd64: universe/libdevel/optional/100% -> main
libmpg123-dev 1.25.8-1 in bionic arm64: universe/libdevel/optional/100% -> main
libmpg123-dev 1.25.8-1 in bionic armhf: universe/libdevel/optional/100% -> main
libmpg123-dev 1.25.8-1 in bionic i386: universe/libdevel/optional/100% -> main
libmpg123-dev 1.25.8-1 in bionic ppc64el: universe/libdevel/optional/100% -> 
main
libmpg123-dev 1.25.8-1 in bionic s390x: universe/libdevel/optional/100% -> main
libout123-0 1.25.8-1 in bionic amd64: universe/libs/optional/100% -> main
libout123-0 1.25.8-1 in bionic arm64: universe/libs/optional/100% -> main
libout123-0 1.25.8-1 in bionic armhf: universe/libs/optional/100% -> main
libout123-0 1.25.8-1 in bionic i386: universe/libs/optional/100% -> main
libout123-0 1.25.8-1 in bionic ppc64el: universe/libs/optional/100% -> main
libout123-0 1.25.8-1 in bionic s390x: universe/libs/optional/100% -> main
mpg123 1.25.8-1 in bionic amd64: universe/sound/optional/100% -> main
mpg123 1.25.8-1 in bionic arm64: universe/sound/optional/100% -> main
mpg123 1.25.8-1 in bionic armhf: universe/sound/optional/100% -> main
mpg123 1.25.8-1 in bionic i386: universe/sound/optional/100% -> main
mpg123 1.25.8-1 in bionic ppc64el: universe/sound/optional/100% -> main
mpg123 1.25.8-1 in bionic s390x: universe/sound/optional/100% -> main
Override [y|N]? y
25 publications overridden.


** Changed in: mpg123 (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

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

Title:
  [MIR] mpg123

Status in mpg123 package in Ubuntu:
  Fix Released

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

  For that, it uses some libraries and we'll need to put them in main.

  Security
  
  There are some CVEs in the history of the project.

  https://security-tracker.debian.org/tracker/source-package/mpg123
  https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html

  The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in
  1.25.8-1.

  Quality assurance
  =
  Desktop team is subscribed.

  Bugs
  

  https://bugs.launchpad.net/ubuntu/+source/mpg123
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=mpg123

  Dependencies
  
  We need libmpg123-0 in main, and this depends on libc6 only.

  Standards compliance
  
  4.1.2. debian/rules is slightly complicated because it generates some wrapper 
scripts for some old binary names. Those binaries don't go in a package that we 
need in main.

  Maintenance
  ===
  Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

[Desktop-packages] [Bug 1753441] Re: [MIR] lame

2018-03-06 Thread Adam Conrad

lame 3.100-2 in bionic: universe/sound -> main
lame 3.100-2 in bionic amd64: universe/sound/optional/100% -> main
lame 3.100-2 in bionic arm64: universe/sound/optional/100% -> main
lame 3.100-2 in bionic armhf: universe/sound/optional/100% -> main
lame 3.100-2 in bionic i386: universe/sound/optional/100% -> main
lame 3.100-2 in bionic ppc64el: universe/sound/optional/100% -> main
lame 3.100-2 in bionic s390x: universe/sound/optional/100% -> main
lame-doc 3.100-2 in bionic amd64: universe/doc/optional/100% -> main
lame-doc 3.100-2 in bionic arm64: universe/doc/optional/100% -> main
lame-doc 3.100-2 in bionic armhf: universe/doc/optional/100% -> main
lame-doc 3.100-2 in bionic i386: universe/doc/optional/100% -> main
lame-doc 3.100-2 in bionic ppc64el: universe/doc/optional/100% -> main
lame-doc 3.100-2 in bionic s390x: universe/doc/optional/100% -> main
libmp3lame-dev 3.100-2 in bionic amd64: universe/libdevel/optional/100% -> main
libmp3lame-dev 3.100-2 in bionic arm64: universe/libdevel/optional/100% -> main
libmp3lame-dev 3.100-2 in bionic armhf: universe/libdevel/optional/100% -> main
libmp3lame-dev 3.100-2 in bionic i386: universe/libdevel/optional/100% -> main
libmp3lame-dev 3.100-2 in bionic ppc64el: universe/libdevel/optional/100% -> 
main
libmp3lame-dev 3.100-2 in bionic s390x: universe/libdevel/optional/100% -> main
libmp3lame0 3.100-2 in bionic amd64: universe/libs/optional/100% -> main
libmp3lame0 3.100-2 in bionic arm64: universe/libs/optional/100% -> main
libmp3lame0 3.100-2 in bionic armhf: universe/libs/optional/100% -> main
libmp3lame0 3.100-2 in bionic i386: universe/libs/optional/100% -> main
libmp3lame0 3.100-2 in bionic ppc64el: universe/libs/optional/100% -> main
libmp3lame0 3.100-2 in bionic s390x: universe/libs/optional/100% -> main
Override [y|N]? y
25 publications overridden.


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

** Changed in: lame (Ubuntu)
 Assignee: Iain Lane (laney) => Adam Conrad (adconrad)

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

Title:
  [MIR] lame

Status in lame package in Ubuntu:
  Fix Released

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

  For that, it uses some libraries and we'll need to put them in main.

  Security
  
  There are some CVEs in the history of the project.

  https://security-tracker.debian.org/tracker/source-package/lame
  https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html

  The Ubuntu CVE page lists some 'needed' ones but from looking at those
  ones in Debian they are duplicates and should be fixed already.

  Quality assurance
  =
  Desktop team is subscribed.

  Bugs
  

  https://bugs.launchpad.net/ubuntu/+source/lame
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=lame

  I think they are reasonably calm given that this is a well known
  project.

  Dependencies
  

  We need libmp3lame0 in main, and this depends on libc6 only.

  Standards compliance
  

  4.1.1 and dh minimal style rules.

  Maintenance
  ===
  Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

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

*** 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/1753190/+attachment/5068563/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1753190/+attachment/5068572/+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/1753190

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  updated from 16.04 and found this error

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  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: Sat Mar  3 07:18:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-22 (9 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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: Upgraded to bionic on 2018-03-02 (1 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1752681] Re: wireless disconnect

2018-03-06 Thread Marco Giannini

In my case it works also by setting the IPV6 to "Automatic, address only".
Try like this. Turn off the connection, set it to Automatich, address only or 
"Ignore" and then re-enable the connection. In my case this procedure works 
(see attachment)

** Attachment added: "Istantanea_2018-03-06_19-03-28.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752681/+attachment/5070976/+files/Istantanea_2018-03-06_19-03-28.png

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

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

[Desktop-packages] [Bug 1753458] Re: [MIR] twolame

2018-03-06 Thread Adam Conrad

twolame 0.3.13-3 in bionic: universe/sound -> main
libtwolame-dev 0.3.13-3 in bionic amd64: universe/libdevel/optional/100% -> main
libtwolame-dev 0.3.13-3 in bionic arm64: universe/libdevel/optional/100% -> main
libtwolame-dev 0.3.13-3 in bionic armhf: universe/libdevel/optional/100% -> main
libtwolame-dev 0.3.13-3 in bionic i386: universe/libdevel/optional/100% -> main
libtwolame-dev 0.3.13-3 in bionic ppc64el: universe/libdevel/optional/100% -> 
main
libtwolame-dev 0.3.13-3 in bionic s390x: universe/libdevel/optional/100% -> main
libtwolame0 0.3.13-3 in bionic amd64: universe/libs/optional/100% -> main
libtwolame0 0.3.13-3 in bionic arm64: universe/libs/optional/100% -> main
libtwolame0 0.3.13-3 in bionic armhf: universe/libs/optional/100% -> main
libtwolame0 0.3.13-3 in bionic i386: universe/libs/optional/100% -> main
libtwolame0 0.3.13-3 in bionic ppc64el: universe/libs/optional/100% -> main
libtwolame0 0.3.13-3 in bionic s390x: universe/libs/optional/100% -> main
twolame 0.3.13-3 in bionic amd64: universe/sound/optional/100% -> main
twolame 0.3.13-3 in bionic arm64: universe/sound/optional/100% -> main
twolame 0.3.13-3 in bionic armhf: universe/sound/optional/100% -> main
twolame 0.3.13-3 in bionic i386: universe/sound/optional/100% -> main
twolame 0.3.13-3 in bionic ppc64el: universe/sound/optional/100% -> main
twolame 0.3.13-3 in bionic s390x: universe/sound/optional/100% -> main
Override [y|N]? y
19 publications overridden.


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

** Changed in: twolame (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  [MIR] twolame

Status in twolame package in Ubuntu:
  Fix Released

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

  For that, it uses some libraries and we'll need to put them in main.

  Security
  
  None reported so far.

  https://security-tracker.debian.org/tracker/source-package/twolame
  https://people.canonical.com/~ubuntu-security/cve/pkg/twolame.html

  Quality assurance
  =
  Desktop team is subscribed.

  Bugs
  
  https://bugs.launchpad.net/ubuntu/+source/twolame
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=twolame

  Dependencies
  
  We need libtwolame0 in main, and this depends on libc6 only.

  Standards compliance
  
  4.1.0. Minimal rules. Tests are disabled. When I enable them the test wrapper 
hangs indefinitely. We should look at that.

  Maintenance
  ===
  Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

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

*** 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/1753184/+attachment/5068544/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1753184/+attachment/5068554/+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/1753184

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  no idea

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  Uname: Linux 4.15.7-041507-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Mar  3 23:55:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-15 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  ProcCmdline: /usr/bin/gnome-shell
  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: 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/1753184/+subscriptions

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

[Desktop-packages] [Bug 1748321] Re: Sort order is bizarre, and can not be changed

2018-03-06 Thread Bug Watch Updater

** Changed in: glib
   Status: Incomplete => Confirmed

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

Title:
  Sort order is bizarre, and can not be changed

Status in GLib:
  Confirmed
Status in glib package in Ubuntu:
  Triaged
Status in gnome-desktop3 package in Ubuntu:
  Invalid

Bug description:
  Create some test files as follows:

  $ touch 0110-0.jpg 0110-A.jpg 01A00010-0.jpg
  03BBF000-0.jpg 3bA1A000-0.jpg 3BD22000-0.jpg
  A4AC3000-0.jpg 00011 00011.jpg 00021

  View them at the command line and in Nautilus:

  $ ls -1
  0110-0.jpg
  0110-A.jpg
  01A00010-0.jpg
  03BBF000-0.jpg
  3bA1A000-0.jpg
  3BD22000-0.jpg
  A4AC3000-0.jpg
  00011
  00011.jpg
  00021
  $ nautilus .

  ls sorts files as one might expect. It is not case sensitive (unless
  you use a case sensitive locale, e.g. LANG=C), but sorts
  alphabetically.

  Nautilus sorts the files in a bizarre order, regardless of which locale is 
used. Weird behaviours include:
  * Longer but otherwise equal filenames sort before shorter ones
  * Sometimes ignores runs of zeros, but not punctuation
  * Seems to detect runs of digits and sort them at the end

  The actual behaviour is very complex and difficult to predict, though
  it must follow some internal logic. The end result is that files don't
  sort in any reasonable order. This also impacts some other
  applications, such as Eye of Gnome. Others, like Transmission, respect
  locale.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-desktop3-data 3.26.2-0ubuntu0.1
  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
  CurrentDesktop: GNOME
  Date: Fri Feb  9 10:39:25 2018
  Dependencies:
   
  InstallationDate: Installed on 2016-12-02 (432 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: gnome-desktop3
  UpgradeStatus: Upgraded to artful on 2017-10-12 (119 days ago)

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

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

[Desktop-packages] [Bug 1753699] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

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

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 #1751460, 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/1753699/+attachment/5070531/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1751460
   deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753699

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I don't know the reason, the crash report started behind another
  window

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  6 10:23:40 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f40fad7c588:movl   $0x0,(%rax)
   PC (0x7f40fad7c588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f40fafe402c, 
init_routine=0x7f40f1e39490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1753699/+subscriptions

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

[Desktop-packages] [Bug 1753814] [NEW] package nvidia-340 (not installed) failed to install/upgrade: Versuch, »/usr/lib/i386-linux-gnu/libGL.so.1« zu überschreiben, welches auch in Paket libgl1:i386 1

2018-03-06 Thread bssmusic

Public bug reported:

Tried to install nvidia 340 on Quadro 1600

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
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
Date: Tue Mar  6 19:47:50 2018
ErrorMessage: Versuch, »/usr/lib/i386-linux-gnu/libGL.so.1« zu überschreiben, 
welches auch in Paket libgl1:i386 1.0.0-2ubuntu2 ist
InstallationDate: Installed on 2018-03-02 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
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~beta1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: Versuch, 
»/usr/lib/i386-linux-gnu/libGL.so.1« zu überschreiben, welches auch in Paket 
libgl1:i386 1.0.0-2ubuntu2 ist
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: Versuch,
  »/usr/lib/i386-linux-gnu/libGL.so.1« zu überschreiben, welches auch in
  Paket libgl1:i386 1.0.0-2ubuntu2 ist

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

Bug description:
  Tried to install nvidia 340 on Quadro 1600

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  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
  Date: Tue Mar  6 19:47:50 2018
  ErrorMessage: Versuch, »/usr/lib/i386-linux-gnu/libGL.so.1« zu überschreiben, 
welches auch in Paket libgl1:i386 1.0.0-2ubuntu2 ist
  InstallationDate: Installed on 2018-03-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  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~beta1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: Versuch, 
»/usr/lib/i386-linux-gnu/libGL.so.1« zu überschreiben, welches auch in Paket 
libgl1:i386 1.0.0-2ubuntu2 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753167] Re: deja-dup-monitor crashed with SIGSEGV